[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AGYK7CSBDF5D7T8W8CAJ9C":3,"skill-same:01M7AGYK7CSBDF5D7T8W8CAJ9C":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},"01M7AGYK7CSBDF5D7T8W8CAJ9C","kiro-spec-status",null,"Show specification status and progress","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-status\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: kiro-spec-status\ndescription: Show specification status and progress\nallowed-tools: Read, Glob, Grep\nargument-hint: \u003Cfeature-name>\n---\n\n# kiro-spec-status Skill\n\n## Core Mission\n- **Success Criteria**:\n  - Show current phase and completion status\n  - Identify next actions and blockers\n  - Provide clear visibility into progress\n  - Surface boundary readiness, upstream\u002Fdownstream context, and likely revalidation needs when available\n\n## Execution Steps\n\n### Step 1: Load Spec Context\n- Read `{{KIRO_DIR}}\u002Fspecs\u002F$ARGUMENTS\u002Fspec.json` for metadata and phase status\n- Read `{{KIRO_DIR}}\u002Fspecs\u002F$ARGUMENTS\u002Fbrief.md` if it exists\n- Read existing files: `requirements.md`, `design.md`, `tasks.md` (if they exist)\n- Check `{{KIRO_DIR}}\u002Fspecs\u002F$ARGUMENTS\u002F` directory for available files\n- Read `{{KIRO_DIR}}\u002Fsteering\u002Froadmap.md` if it exists and this spec appears in it\n\n### Step 2: Analyze Status\n\n**Parse each phase**:\n- **Requirements**: Count requirements and acceptance criteria\n- **Design**: Check for architecture, components, diagrams, and whether boundary sections are present\n- **Tasks**: Count completed vs total tasks (parse `- [x]` vs `- [ ]`)\n- **Approvals**: Check approval status in spec.json\n- **Boundary context**:\n  - From brief.md: note `Boundary Candidates`, `Upstream \u002F Downstream`, and `Existing Spec Touchpoints` if present\n  - From design.md: note `Boundary Commitments`, `Out of Boundary`, `Allowed Dependencies`, and `Revalidation Triggers` if present\n  - From roadmap.md: note upstream dependencies and whether this spec is adjacent to `Existing Spec Updates`\n- **Revalidation watchlist**:\n  - Identify downstream specs, neighboring existing-spec updates, or rollout-sensitive design notes that may need revalidation if this spec changes\n  - Call out when the current spec shape looks too broad and may want roadmap\u002Fdesign splitting instead of more local repair\n\n### Step 3: Generate Report\n\nCreate report in the language specified in spec.json covering:\n1. **Current Phase & Progress**: Where the spec is in the workflow\n2. **Completion Status**: Percentage complete for each phase\n3. **Task Breakdown**: If tasks exist, show completed\u002Fremaining counts\n4. **Boundary Context**: Upstream\u002Fdownstream, out-of-boundary, and allowed dependency notes when available\n5. **Revalidation Watchlist**: Downstream or adjacent work likely affected by changes to this spec\n6. **Next Actions**: What needs to be done next\n7. **Blockers**: Any issues preventing progress\n\n**Format**: Clear, scannable format with emojis for status\n\n## Safety & Fallback\n\n### Error Scenarios\n\n**Spec Not Found**:\n- **Message**: \"No spec found for `$ARGUMENTS`. Check available specs in `{{KIRO_DIR}}\u002Fspecs\u002F`\"\n- **Action**: List available spec directories\n\n**Incomplete Spec**:\n- **Warning**: Identify which files are missing\n- **Suggested Action**: Point to next phase command\n\n### List All Specs\n\nTo see all available specs:\n- Run with no argument or use wildcard\n- Shows all specs in `{{KIRO_DIR}}\u002Fspecs\u002F` with their status\n","# kiro-spec-status Skill\n\n## Core Mission\n- **Success Criteria**:\n  - Show current phase and completion status\n  - Identify next actions and blockers\n  - Provide clear visibility into progress\n  - Surface boundary readiness, upstream\u002Fdownstream context, and likely revalidation needs when available\n\n## Execution Steps\n\n### Step 1: Load Spec Context\n- Read `{{KIRO_DIR}}\u002Fspecs\u002F$ARGUMENTS\u002Fspec.json` for metadata and phase status\n- Read `{{KIRO_DIR}}\u002Fspecs\u002F$ARGUMENTS\u002Fbrief.md` if it exists\n- Read existing files: `requirements.md`, `design.md`, `tasks.md` (if they exist)\n- Check `{{KIRO_DIR}}\u002Fspecs\u002F$ARGUMENTS\u002F` directory for available files\n- Read `{{KIRO_DIR}}\u002Fsteering\u002Froadmap.md` if it exists and this spec appears in it\n\n### Step 2: Analyze Status\n\n**Parse each phase**:\n- **Requirements**: Count requirements and acceptance criteria\n- **Design**: Check for architecture, components, diagrams, and whether boundary sections are present\n- **Tasks**: Count completed vs total tasks (parse `- [x]` vs `- [ ]`)\n- **Approvals**: Check approval status in spec.json\n- **Boundary context**:\n  - From brief.md: note `Boundary Candidates`, `Upstream \u002F Downstream`, and `Existing Spec Touchpoints` if present\n  - From design.md: note `Boundary Commitments`, `Out of Boundary`, `Allowed Dependencies`, and `Revalidation Triggers` if present\n  - From roadmap.md: note upstream dependencies and whether this spec is adjacent to `Existing Spec Updates`\n- **Revalidation watchlist**:\n  - Identify downstream specs, neighboring existing-spec updates, or rollout-sensitive design notes that may need revalidation if this spec changes\n  - Call out when the current spec shape looks too broad and may want roadmap\u002Fdesign splitting instead of more local repair\n\n### Step 3: Generate Report\n\nCreate report in the language specified in spec.json covering:\n1. **Current Phase & Progress**: Where the spec is in the workflow\n2. **Completion Status**: Percentage complete for each phase\n3. **Task Breakdown**: If tasks exist, show completed\u002Fremaining counts\n4. **Boundary Context**: Upstream\u002Fdownstream, out-of-boundary, and allowed dependency notes when available\n5. **Revalidation Watchlist**: Downstream or adjacent work likely affected by changes to this spec\n6. **Next Actions**: What needs to be done next\n7. **Blockers**: Any issues preventing progress\n\n**Format**: Clear, scannable format with emojis for status\n\n## Safety & Fallback\n\n### Error Scenarios\n\n**Spec Not Found**:\n- **Message**: \"No spec found for `$ARGUMENTS`. Check available specs in `{{KIRO_DIR}}\u002Fspecs\u002F`\"\n- **Action**: List available spec directories\n\n**Incomplete Spec**:\n- **Warning**: Identify which files are missing\n- **Suggested Action**: Point to next phase command\n\n### List All Specs\n\nTo see all available specs:\n- Run with no argument or use wildcard\n- Shows all specs in `{{KIRO_DIR}}\u002Fspecs\u002F` with their status\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25},"Read, Glob, Grep","\u003Cfeature-name>","main","2259916910e45633c21f5760d7fe329addc415a7","tools\u002Fcc-sdd\u002Ftemplates\u002Fagents\u002Fclaude-code-skills\u002Fskills\u002Fkiro-spec-status",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-status",{"tool":39,"command":40},"bunx","bunx skills add Huruikagi\u002Fspecbind --skill kiro-spec-status",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Huruikagi\u002Fspecbind --skill kiro-spec-status","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fcc-sdd\u002Ftemplates\u002Fagents\u002Fclaude-code-skills\u002Fskills\u002Fkiro-spec-status\u002FSKILL.md",true,[],[48,54,59,66,73,80],{"skillNo":49,"name":50,"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":51,"categories":52,"keywords":53,"publishedAt":19},"01M7AH3VQ2VR2X159H99G73TGE","kiro-spec-init","https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fspecbind\u002Ftests\u002Ffixtures\u002Fmigration\u002Fminimal\u002F.agents\u002Fskills\u002Fkiro-spec-init\u002FSKILL.md",[],[],{"skillNo":55,"name":50,"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":56,"categories":57,"keywords":58,"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":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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",[],[]]