kiro-spec-init
Initialize a new specification with detailed project description
- License 许可
- MIT
- 最近更新
- 2026-11-04
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- kiro-spec-init
- description
- Initialize a new specification with detailed project description
- allowed-tools
- Bash, Read, Write, Glob, AskUserQuestion
- argument-hint
- <project-description>
03 SKILL.md 正文
Spec Initialization
<instructions>
Core Task
Generate a unique feature name from the project description ($ARGUMENTS) and initialize the specification structure.
Execution Steps
- Check for Brief: If
{{KIRO_DIR}}/specs/{feature-name}/brief.mdexists (created by/kiro-discovery), read it. The brief contains problem, approach, scope, and constraints from the discovery session. Use this to pre-fill the project description and skip clarification questions that the brief already answers. - Clarify Intent: The Project Description in requirements.md must contain three elements: (a) who has the problem, (b) current situation, (c) what should change. If a brief.md exists and covers these, skip to step 3. Otherwise, ask the user to clarify before proceeding. Ask as many questions as needed; do not fill in gaps with your own assumptions.
- Check Uniqueness: Verify
{{KIRO_DIR}}/specs/for naming conflicts. If the directory already exists with onlybrief.md(nospec.json), use that directory (discovery created it). - Create Directory:
{{KIRO_DIR}}/specs/[feature-name]/(skip if already exists from discovery) - Initialize Files Using Templates:
- Read
{{KIRO_DIR}}/settings/templates/specs/init.json - Read
{{KIRO_DIR}}/settings/templates/specs/requirements-init.md - Replace placeholders:
{{FEATURE_NAME}}→ generated feature name{{TIMESTAMP}}→ current ISO 8601 timestamp{{PROJECT_DESCRIPTION}}→ from brief.md if available, otherwise $ARGUMENTS{{LANG_CODE}}→ language code (detect from user's input language, default toen)
- Write
spec.jsonandrequirements.mdto spec directory
- Read
Important Constraints
- Do NOT generate requirements, design, or tasks. This skill only creates spec.json and requirements.md. </instructions>
Output Description
Provide output in the language specified in spec.json with the following structure:
- Generated Feature Name:
feature-nameformat with 1-2 sentence rationale - Project Summary: Brief summary (1 sentence)
- Created Files: Bullet list with full paths
- Next Step: Command block showing
/kiro-spec-requirements <feature-name>
Format Requirements:
- Use Markdown headings (##, ###)
- Wrap commands in code blocks
- Keep total output concise (under 250 words)
- Use clear, professional language per
spec.json.language
Safety & Fallback
- Ambiguous Feature Name: If feature name generation is unclear, propose 2-3 options and ask user to select
- Template Missing: If template files don't exist in
{{KIRO_DIR}}/settings/templates/specs/, report error with specific missing file path and suggest checking repository setup - Directory Conflict: If feature name already exists, append numeric suffix (e.g.,
feature-name-2) and notify user of automatic conflict resolution - Write Failure: Report error with specific path and suggest checking permissions or disk space
04 同仓库更多 Skills
kiro-spec-init
暂无简介
kiro-spec-init
暂无简介
sb-verify-completion
Consequence-free check of an explicit completion or success claim against fresh evidence. Changes nothing; do not use to advance a named Spec whose implementation may be accepted.
sb-validate-implementation
Validate completed Tasks against active Requirement IDs and record completion on GO under an explicit lifecycle-validation request or ordinary Drive authority. Also owns completion withdrawal under an evidenced Drive replan recovery handoff. For a consequence-free claim check, use sb-verify-completion.
sb-validate-design
Independently judge whether a Spec's design is ready to be built on — requirement coverage, boundary, buildability, self-containment, and architectural fit.
sb-steering
Maintain durable project guidance — bootstrap it, synchronize it after code changes, or document a long-lived project convention such as testing, API, security, or deployment.