[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AH0XBAXG6FV5PRC98P2T8M":3,"skill-same:01M7AH0XBAXG6FV5PRC98P2T8M":53},{"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},"01M7AH0XBAXG6FV5PRC98P2T8M","kiro-validate-gap",null,"Analyze implementation gap between requirements and existing codebase","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\u002Fcodex-skills\u002Fskills\u002Fkiro-validate-gap\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: kiro-validate-gap\ndescription: Analyze implementation gap between requirements and existing codebase\nmetadata:\n  shared-rules: \"gap-analysis.md\"\n---\n\n\n# Implementation Gap Validation\n\n\u003Cbackground_information>\n- **Mission**: Analyze the gap between requirements and existing codebase to inform implementation strategy\n- **Success Criteria**:\n  - Comprehensive understanding of existing codebase patterns and components\n  - Clear identification of missing capabilities and integration challenges\n  - Multiple viable implementation approaches evaluated\n  - Technical research needs identified for design phase\n\u003C\u002Fbackground_information>\n\n\u003Cinstructions>\n## Core Task\nAnalyze implementation gap for feature **$1** based on approved requirements and existing codebase.\n\n## Execution Steps\n\n1. **Load Context**:\n   - Read `{{KIRO_DIR}}\u002Fspecs\u002F$1\u002Fspec.json` for language and metadata\n   - Read `{{KIRO_DIR}}\u002Fspecs\u002F$1\u002Frequirements.md` for requirements\n   - Core steering context: `product.md`, `tech.md`, `structure.md`\n   - Additional steering files only when directly relevant to the feature's domain rules, integrations, runtime prerequisites, compliance\u002Fsecurity constraints, or existing product boundaries\n   - Relevant local agent skills or playbooks only when they clearly match the feature's host environment or use case and provide analysis-relevant context\n\n2. **Read Analysis Guidelines**:\n   - Read `rules\u002Fgap-analysis.md` from this skill's directory for comprehensive analysis framework\n\n#### Parallel Research\n\nThe following research areas are independent and can be executed in parallel:\n1. **Codebase analysis**: Existing implementations, architecture patterns, integration points, extension possibilities\n2. **External dependency research**: Dependency compatibility, version constraints, known integration challenges (when needed)\n3. **Context loading**: Requirements, core steering, task-relevant extra steering, relevant local agent skills\u002Fplaybooks, and gap-analysis rules\n\nIf multi-agent is enabled, spawn sub-agents for each area above. Otherwise execute sequentially.\n\nAfter all parallel research completes, synthesize findings for gap analysis.\n\n3. **Execute Gap Analysis**:\n   - Follow gap-analysis.md framework for thorough investigation\n   - Analyze existing codebase using Grep and Read tools\n   - Use WebSearch\u002FWebFetch for external dependency research if needed\n   - Evaluate multiple implementation approaches (extend\u002Fnew\u002Fhybrid)\n   - Use language specified in spec.json for output\n\n4. **Generate Analysis Document**:\n   - Create comprehensive gap analysis following the output guidelines in gap-analysis.md\n   - Present multiple viable options with trade-offs\n   - Flag areas requiring further research\n\n5. **Write Gap Analysis to Disk**:\n\n   **Write the gap analysis to disk so it survives session boundaries and can be referenced during design phase.**\n\n   - Save the gap analysis to `{{KIRO_DIR}}\u002Fspecs\u002F$1\u002Fresearch.md`\n   - If the file already exists, append the new analysis (separated by a horizontal rule `---`) rather than overwriting previous research\n   - Verify the file was written by reading it back\n\n## Important Constraints\n- **Information over Decisions**: Provide analysis and options, not final implementation choices\n- **Multiple Options**: Present viable alternatives when applicable\n- **Thorough Investigation**: Use tools to deeply understand existing codebase\n- **Explicit Gaps**: Clearly flag areas needing research or investigation\n- **Context Discipline**: Start with core steering and expand only with analysis-relevant steering or use-case-aligned local agent skills\u002Fplaybooks\n\u003C\u002Finstructions>\n\n## Tool Guidance\n- **Read first**: Load spec, core steering, relevant local playbooks\u002Fagent skills, and rules before analysis\n- **Grep extensively**: Search codebase for patterns, conventions, and integration points\n- **WebSearch\u002FWebFetch**: Research external dependencies and best practices when needed\n- **Write last**: Generate analysis only after complete investigation\n\n## Output Description\nProvide output in the language specified in spec.json with:\n\n1. **Analysis Summary**: Brief overview (3-5 bullets) of scope, challenges, and recommendations\n2. **Document Status**: Confirm analysis approach used\n3. **Next Steps**: Guide user on proceeding to design phase\n\n**Format Requirements**:\n- Use Markdown headings for clarity\n- Keep summary concise (under 300 words)\n- Detailed analysis follows gap-analysis.md output guidelines\n\n## Safety & Fallback\n\n### Error Scenarios\n- **Missing Requirements**: If requirements.md doesn't exist, stop with message: \"Run `$kiro-spec-requirements $1` first to generate requirements\"\n- **Requirements Not Approved**: If requirements not approved, warn user but proceed (gap analysis can inform requirement revisions)\n- **Empty Steering Directory**: Warn user that project context is missing and may affect analysis quality\n- **Complex Integration Unclear**: Flag for comprehensive research in design phase rather than blocking\n- **Language Undefined**: Default to English (`en`) if spec.json doesn't specify language\n\n### Next Phase: Design Generation\n\n**If Gap Analysis Complete**:\n- Review gap analysis insights\n- Run `$kiro-spec-design $1` to create technical design document\n- Or `$kiro-spec-design $1 -y` to auto-approve requirements and proceed directly\n\n**Note**: Gap analysis is optional but recommended for brownfield projects to inform design decisions.\n","# Implementation Gap Validation\n\n\u003Cbackground_information>\n- **Mission**: Analyze the gap between requirements and existing codebase to inform implementation strategy\n- **Success Criteria**:\n  - Comprehensive understanding of existing codebase patterns and components\n  - Clear identification of missing capabilities and integration challenges\n  - Multiple viable implementation approaches evaluated\n  - Technical research needs identified for design phase\n\u003C\u002Fbackground_information>\n\n\u003Cinstructions>\n## Core Task\nAnalyze implementation gap for feature **$1** based on approved requirements and existing codebase.\n\n## Execution Steps\n\n1. **Load Context**:\n   - Read `{{KIRO_DIR}}\u002Fspecs\u002F$1\u002Fspec.json` for language and metadata\n   - Read `{{KIRO_DIR}}\u002Fspecs\u002F$1\u002Frequirements.md` for requirements\n   - Core steering context: `product.md`, `tech.md`, `structure.md`\n   - Additional steering files only when directly relevant to the feature's domain rules, integrations, runtime prerequisites, compliance\u002Fsecurity constraints, or existing product boundaries\n   - Relevant local agent skills or playbooks only when they clearly match the feature's host environment or use case and provide analysis-relevant context\n\n2. **Read Analysis Guidelines**:\n   - Read `rules\u002Fgap-analysis.md` from this skill's directory for comprehensive analysis framework\n\n#### Parallel Research\n\nThe following research areas are independent and can be executed in parallel:\n1. **Codebase analysis**: Existing implementations, architecture patterns, integration points, extension possibilities\n2. **External dependency research**: Dependency compatibility, version constraints, known integration challenges (when needed)\n3. **Context loading**: Requirements, core steering, task-relevant extra steering, relevant local agent skills\u002Fplaybooks, and gap-analysis rules\n\nIf multi-agent is enabled, spawn sub-agents for each area above. Otherwise execute sequentially.\n\nAfter all parallel research completes, synthesize findings for gap analysis.\n\n3. **Execute Gap Analysis**:\n   - Follow gap-analysis.md framework for thorough investigation\n   - Analyze existing codebase using Grep and Read tools\n   - Use WebSearch\u002FWebFetch for external dependency research if needed\n   - Evaluate multiple implementation approaches (extend\u002Fnew\u002Fhybrid)\n   - Use language specified in spec.json for output\n\n4. **Generate Analysis Document**:\n   - Create comprehensive gap analysis following the output guidelines in gap-analysis.md\n   - Present multiple viable options with trade-offs\n   - Flag areas requiring further research\n\n5. **Write Gap Analysis to Disk**:\n\n   **Write the gap analysis to disk so it survives session boundaries and can be referenced during design phase.**\n\n   - Save the gap analysis to `{{KIRO_DIR}}\u002Fspecs\u002F$1\u002Fresearch.md`\n   - If the file already exists, append the new analysis (separated by a horizontal rule `---`) rather than overwriting previous research\n   - Verify the file was written by reading it back\n\n## Important Constraints\n- **Information over Decisions**: Provide analysis and options, not final implementation choices\n- **Multiple Options**: Present viable alternatives when applicable\n- **Thorough Investigation**: Use tools to deeply understand existing codebase\n- **Explicit Gaps**: Clearly flag areas needing research or investigation\n- **Context Discipline**: Start with core steering and expand only with analysis-relevant steering or use-case-aligned local agent skills\u002Fplaybooks\n\u003C\u002Finstructions>\n\n## Tool Guidance\n- **Read first**: Load spec, core steering, relevant local playbooks\u002Fagent skills, and rules before analysis\n- **Grep extensively**: Search codebase for patterns, conventions, and integration points\n- **WebSearch\u002FWebFetch**: Research external dependencies and best practices when needed\n- **Write last**: Generate analysis only after complete investigation\n\n## Output Description\nProvide output in the language specified in spec.json with:\n\n1. **Analysis Summary**: Brief overview (3-5 bullets) of scope, challenges, and recommendations\n2. **Document Status**: Confirm analysis approach used\n3. **Next Steps**: Guide user on proceeding to design phase\n\n**Format Requirements**:\n- Use Markdown headings for clarity\n- Keep summary concise (under 300 words)\n- Detailed analysis follows gap-analysis.md output guidelines\n\n## Safety & Fallback\n\n### Error Scenarios\n- **Missing Requirements**: If requirements.md doesn't exist, stop with message: \"Run `$kiro-spec-requirements $1` first to generate requirements\"\n- **Requirements Not Approved**: If requirements not approved, warn user but proceed (gap analysis can inform requirement revisions)\n- **Empty Steering Directory**: Warn user that project context is missing and may affect analysis quality\n- **Complex Integration Unclear**: Flag for comprehensive research in design phase rather than blocking\n- **Language Undefined**: Default to English (`en`) if spec.json doesn't specify language\n\n### Next Phase: Design Generation\n\n**If Gap Analysis Complete**:\n- Review gap analysis insights\n- Run `$kiro-spec-design $1` to create technical design document\n- Or `$kiro-spec-design $1 -y` to auto-approve requirements and proceed directly\n\n**Note**: Gap analysis is optional but recommended for brownfield projects to inform design decisions.\n",{"name":5,"metadata":24,"description":7},{"shared-rules":25},"gap-analysis.md","main","2259916910e45633c21f5760d7fe329addc415a7","tools\u002Fcc-sdd\u002Ftemplates\u002Fagents\u002Fcodex-skills\u002Fskills\u002Fkiro-validate-gap",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-validate-gap",{"tool":39,"command":40},"bunx","bunx skills add Huruikagi\u002Fspecbind --skill kiro-validate-gap",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Huruikagi\u002Fspecbind --skill kiro-validate-gap","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fcc-sdd\u002Ftemplates\u002Fagents\u002Fcodex-skills\u002Fskills\u002Fkiro-validate-gap\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",179,"https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fcc-sdd\u002Ftemplates\u002Fagents\u002Fcodex-skills\u002Fskills\u002Fkiro-validate-gap\u002Fagents\u002Fopenai.yaml",[54,60,65,72,79,86],{"skillNo":55,"name":56,"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":57,"categories":58,"keywords":59,"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":61,"name":56,"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":62,"categories":63,"keywords":64,"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":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},"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":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},"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":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},"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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",[],[]]