[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AGY9EYQ5VRMSSTWDY6NEKK":3,"skill-same:01M7AGY9EYQ5VRMSSTWDY6NEKK":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7AGY9EYQ5VRMSSTWDY6NEKK","kiro-spec-init",null,"Initialize a new specification with detailed project description","Huruikagi\u002Fspecbind","Huruikagi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10933612?v=4","01M7AGWP8QKD1EXMV26YA1ESXF","ふるいかぎ","01M7AGWP9WBJ1EEJNQKWB77GN3",2,"MIT","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fcc-sdd\u002Ftemplates\u002Fagents\u002Fclaude-code-skills\u002Fskills\u002Fkiro-spec-init\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: kiro-spec-init\ndescription: Initialize a new specification with detailed project description\nallowed-tools: Bash, Read, Write, Glob, AskUserQuestion\nargument-hint: \u003Cproject-description>\n---\n\n# Spec Initialization\n\n\u003Cinstructions>\n## Core Task\nGenerate a unique feature name from the project description ($ARGUMENTS) and initialize the specification structure.\n\n## Execution Steps\n1. **Check for Brief**: If `{{KIRO_DIR}}\u002Fspecs\u002F{feature-name}\u002Fbrief.md` exists (created by `\u002Fkiro-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.\n2. **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.\n3. **Check Uniqueness**: Verify `{{KIRO_DIR}}\u002Fspecs\u002F` for naming conflicts. If the directory already exists with only `brief.md` (no `spec.json`), use that directory (discovery created it).\n4. **Create Directory**: `{{KIRO_DIR}}\u002Fspecs\u002F[feature-name]\u002F` (skip if already exists from discovery)\n5. **Initialize Files Using Templates**:\n   - Read `{{KIRO_DIR}}\u002Fsettings\u002Ftemplates\u002Fspecs\u002Finit.json`\n   - Read `{{KIRO_DIR}}\u002Fsettings\u002Ftemplates\u002Fspecs\u002Frequirements-init.md`\n   - Replace placeholders:\n     - `{{FEATURE_NAME}}` → generated feature name\n     - `{{TIMESTAMP}}` → current ISO 8601 timestamp\n     - `{{PROJECT_DESCRIPTION}}` → from brief.md if available, otherwise $ARGUMENTS\n     - `{{LANG_CODE}}` → language code (detect from user's input language, default to `en`)\n   - Write `spec.json` and `requirements.md` to spec directory\n\n## Important Constraints\n- Do NOT generate requirements, design, or tasks. This skill only creates spec.json and requirements.md.\n\u003C\u002Finstructions>\n\n## Output Description\nProvide output in the language specified in `spec.json` with the following structure:\n\n1. **Generated Feature Name**: `feature-name` format with 1-2 sentence rationale\n2. **Project Summary**: Brief summary (1 sentence)\n3. **Created Files**: Bullet list with full paths\n4. **Next Step**: Command block showing `\u002Fkiro-spec-requirements \u003Cfeature-name>`\n\n**Format Requirements**:\n- Use Markdown headings (##, ###)\n- Wrap commands in code blocks\n- Keep total output concise (under 250 words)\n- Use clear, professional language per `spec.json.language`\n\n## Safety & Fallback\n- **Ambiguous Feature Name**: If feature name generation is unclear, propose 2-3 options and ask user to select\n- **Template Missing**: If template files don't exist in `{{KIRO_DIR}}\u002Fsettings\u002Ftemplates\u002Fspecs\u002F`, report error with specific missing file path and suggest checking repository setup\n- **Directory Conflict**: If feature name already exists, append numeric suffix (e.g., `feature-name-2`) and notify user of automatic conflict resolution\n- **Write Failure**: Report error with specific path and suggest checking permissions or disk space\n","# Spec Initialization\n\n\u003Cinstructions>\n## Core Task\nGenerate a unique feature name from the project description ($ARGUMENTS) and initialize the specification structure.\n\n## Execution Steps\n1. **Check for Brief**: If `{{KIRO_DIR}}\u002Fspecs\u002F{feature-name}\u002Fbrief.md` exists (created by `\u002Fkiro-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.\n2. **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.\n3. **Check Uniqueness**: Verify `{{KIRO_DIR}}\u002Fspecs\u002F` for naming conflicts. If the directory already exists with only `brief.md` (no `spec.json`), use that directory (discovery created it).\n4. **Create Directory**: `{{KIRO_DIR}}\u002Fspecs\u002F[feature-name]\u002F` (skip if already exists from discovery)\n5. **Initialize Files Using Templates**:\n   - Read `{{KIRO_DIR}}\u002Fsettings\u002Ftemplates\u002Fspecs\u002Finit.json`\n   - Read `{{KIRO_DIR}}\u002Fsettings\u002Ftemplates\u002Fspecs\u002Frequirements-init.md`\n   - Replace placeholders:\n     - `{{FEATURE_NAME}}` → generated feature name\n     - `{{TIMESTAMP}}` → current ISO 8601 timestamp\n     - `{{PROJECT_DESCRIPTION}}` → from brief.md if available, otherwise $ARGUMENTS\n     - `{{LANG_CODE}}` → language code (detect from user's input language, default to `en`)\n   - Write `spec.json` and `requirements.md` to spec directory\n\n## Important Constraints\n- Do NOT generate requirements, design, or tasks. This skill only creates spec.json and requirements.md.\n\u003C\u002Finstructions>\n\n## Output Description\nProvide output in the language specified in `spec.json` with the following structure:\n\n1. **Generated Feature Name**: `feature-name` format with 1-2 sentence rationale\n2. **Project Summary**: Brief summary (1 sentence)\n3. **Created Files**: Bullet list with full paths\n4. **Next Step**: Command block showing `\u002Fkiro-spec-requirements \u003Cfeature-name>`\n\n**Format Requirements**:\n- Use Markdown headings (##, ###)\n- Wrap commands in code blocks\n- Keep total output concise (under 250 words)\n- Use clear, professional language per `spec.json.language`\n\n## Safety & Fallback\n- **Ambiguous Feature Name**: If feature name generation is unclear, propose 2-3 options and ask user to select\n- **Template Missing**: If template files don't exist in `{{KIRO_DIR}}\u002Fsettings\u002Ftemplates\u002Fspecs\u002F`, report error with specific missing file path and suggest checking repository setup\n- **Directory Conflict**: If feature name already exists, append numeric suffix (e.g., `feature-name-2`) and notify user of automatic conflict resolution\n- **Write Failure**: Report error with specific path and suggest checking permissions or disk space\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25},"Bash, Read, Write, Glob, AskUserQuestion","\u003Cproject-description>","main","2259916910e45633c21f5760d7fe329addc415a7","tools\u002Fcc-sdd\u002Ftemplates\u002Fagents\u002Fclaude-code-skills\u002Fskills\u002Fkiro-spec-init",0,"https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind","https:\u002F\u002Fgithub.com\u002FHuruikagi","2026-11-04 13:59:47",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Huruikagi\u002Fspecbind --skill kiro-spec-init",{"tool":39,"command":40},"bunx","bunx skills add Huruikagi\u002Fspecbind --skill kiro-spec-init",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Huruikagi\u002Fspecbind --skill kiro-spec-init","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fcc-sdd\u002Ftemplates\u002Fagents\u002Fclaude-code-skills\u002Fskills\u002Fkiro-spec-init\u002FSKILL.md",true,[],[48,53,58,65,72,79],{"skillNo":49,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7AH3VQ2VR2X159H99G73TGE","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Ftests\u002Ffixtures\u002Fmigration\u002Fminimal\u002F.agents\u002Fskills\u002Fkiro-spec-init\u002FSKILL.md",[],[],{"skillNo":54,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7AH3RXXAHA50BR132P0M955","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Ftests\u002Ffixtures\u002Fmigration\u002Fguided\u002F.claude\u002Fskills\u002Fkiro-spec-init\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7AH3KZBF4YBG4Q8628WD50S","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.","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-verify-completion\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7AH3EFD7KC9RGPZFZE0YNA6","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.","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-validate-implementation\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7AH38XP0RT7N8G5M74N7FD5","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.","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-validate-design\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7AH344YTCDM8E8FTSJHC8WF","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.","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Fassets\u002Fskills\u002Fsb-steering\u002FSKILL.md",[],[]]