[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AH0TY3B2RE6ZKT3T05ZCFY":3,"skill-same:01M7AH0TY3B2RE6ZKT3T05ZCFY":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},"01M7AH0TY3B2RE6ZKT3T05ZCFY","kiro-validate-design",null,"Interactive technical design quality review and validation","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-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: kiro-validate-design\ndescription: Interactive technical design quality review and validation\nmetadata:\n  shared-rules: \"design-review.md\"\n---\n\n\n# Technical Design Validation\n\n\u003Cbackground_information>\n- **Mission**: Conduct interactive quality review of technical design to ensure readiness for implementation\n- **Success Criteria**:\n  - Critical issues identified (maximum 3 most important concerns)\n  - Balanced assessment with strengths recognized\n  - Clear GO\u002FNO-GO decision with rationale\n  - Actionable feedback for improvements if needed\n\u003C\u002Fbackground_information>\n\n\u003Cinstructions>\n## Core Task\nInteractive design quality review for feature **$1** based on approved requirements and design document.\n\n## Execution Steps\n\n1. **Gather 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   - Read `{{KIRO_DIR}}\u002Fspecs\u002F$1\u002Fdesign.md` for design document\n   - Core steering context: `product.md`, `tech.md`, `structure.md`\n   - Additional steering files only when directly relevant to architecture boundaries, integrations, runtime prerequisites, domain rules, security\u002Fperformance constraints, or team conventions that affect implementation readiness\n   - Relevant local agent skills or playbooks only when they clearly match the feature's host environment or use case and provide review-relevant context\n\n#### Parallel Research\n\nThe following research areas are independent and can be executed in parallel:\n1. **Context & rules loading**: Spec documents, core steering, task-relevant extra steering, relevant local agent skills\u002Fplaybooks, and `rules\u002Fdesign-review.md` from this skill's directory for review criteria\n2. **Codebase pattern survey**: Gather existing architecture patterns, naming conventions, and component structure from the codebase to use as reference during review\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 review.\n\n2. **Execute Design Review**:\n   - Reference conversation history when available: leverage prior requirements discussion and user's stated design intent\n   - Follow design-review.md process: Analysis → Critical Issues → Strengths → GO\u002FNO-GO\n   - Limit to 3 most important concerns\n   - Engage interactively with user — ask clarifying questions, propose alternatives\n   - Use language specified in spec.json for output\n\n3. **Decision and Next Steps**:\n   - Clear GO\u002FNO-GO decision with rationale\n   - Provide specific actionable next steps (see Next Phase below)\n\n## Important Constraints\n- **Quality assurance, not perfection seeking**: Accept acceptable risk\n- **Critical focus only**: Maximum 3 issues, only those significantly impacting success\n- **Conversation-aware**: Leverage discussion history for requirements context and user intent when available\n- **Interactive approach**: Engage in dialogue, ask clarifying questions, propose alternatives\n- **Balanced assessment**: Recognize both strengths and weaknesses\n- **Actionable feedback**: All suggestions must be implementable\n- **Context Discipline**: Start with core steering and expand only with review-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 review\n- **Grep if needed**: Search codebase for pattern validation or integration checks\n- **Interactive**: Engage with user throughout the review process\n\n## Output Description\nProvide output in the language specified in spec.json with:\n\n1. **Review Summary**: Brief overview (2-3 sentences) of design quality and readiness\n2. **Critical Issues**: Maximum 3, following design-review.md format\n3. **Design Strengths**: 1-2 positive aspects\n4. **Final Assessment**: GO\u002FNO-GO decision with rationale and next steps\n\n**Format Requirements**:\n- Use Markdown headings for clarity\n- Follow design-review.md output format\n- Keep summary concise\n\n## Safety & Fallback\n\n### Error Scenarios\n- **Missing Design**: If design.md doesn't exist, stop with message: \"Run `$kiro-spec-design $1` first to generate design document\"\n- **Design Not Generated**: If design phase not marked as generated in spec.json, warn but proceed with review\n- **Empty Steering Directory**: Warn user that project context is missing and may affect review quality\n- **Language Undefined**: Default to English (`en`) if spec.json doesn't specify language\n\n### Next Phase: Task Generation\n\n**If Design Passes Validation (GO Decision)**:\n- Review feedback and apply changes if needed\n- Run `$kiro-spec-tasks $1` to generate implementation tasks\n- Or `$kiro-spec-tasks $1 -y` to auto-approve and proceed directly\n\n**If Design Needs Revision (NO-GO Decision)**:\n- Address critical issues identified\n- Re-run `$kiro-spec-design $1` with improvements\n- Re-validate with `$kiro-validate-design $1`\n\n**Note**: Design validation is recommended but optional. Quality review helps catch issues early.\n","# Technical Design Validation\n\n\u003Cbackground_information>\n- **Mission**: Conduct interactive quality review of technical design to ensure readiness for implementation\n- **Success Criteria**:\n  - Critical issues identified (maximum 3 most important concerns)\n  - Balanced assessment with strengths recognized\n  - Clear GO\u002FNO-GO decision with rationale\n  - Actionable feedback for improvements if needed\n\u003C\u002Fbackground_information>\n\n\u003Cinstructions>\n## Core Task\nInteractive design quality review for feature **$1** based on approved requirements and design document.\n\n## Execution Steps\n\n1. **Gather 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   - Read `{{KIRO_DIR}}\u002Fspecs\u002F$1\u002Fdesign.md` for design document\n   - Core steering context: `product.md`, `tech.md`, `structure.md`\n   - Additional steering files only when directly relevant to architecture boundaries, integrations, runtime prerequisites, domain rules, security\u002Fperformance constraints, or team conventions that affect implementation readiness\n   - Relevant local agent skills or playbooks only when they clearly match the feature's host environment or use case and provide review-relevant context\n\n#### Parallel Research\n\nThe following research areas are independent and can be executed in parallel:\n1. **Context & rules loading**: Spec documents, core steering, task-relevant extra steering, relevant local agent skills\u002Fplaybooks, and `rules\u002Fdesign-review.md` from this skill's directory for review criteria\n2. **Codebase pattern survey**: Gather existing architecture patterns, naming conventions, and component structure from the codebase to use as reference during review\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 review.\n\n2. **Execute Design Review**:\n   - Reference conversation history when available: leverage prior requirements discussion and user's stated design intent\n   - Follow design-review.md process: Analysis → Critical Issues → Strengths → GO\u002FNO-GO\n   - Limit to 3 most important concerns\n   - Engage interactively with user — ask clarifying questions, propose alternatives\n   - Use language specified in spec.json for output\n\n3. **Decision and Next Steps**:\n   - Clear GO\u002FNO-GO decision with rationale\n   - Provide specific actionable next steps (see Next Phase below)\n\n## Important Constraints\n- **Quality assurance, not perfection seeking**: Accept acceptable risk\n- **Critical focus only**: Maximum 3 issues, only those significantly impacting success\n- **Conversation-aware**: Leverage discussion history for requirements context and user intent when available\n- **Interactive approach**: Engage in dialogue, ask clarifying questions, propose alternatives\n- **Balanced assessment**: Recognize both strengths and weaknesses\n- **Actionable feedback**: All suggestions must be implementable\n- **Context Discipline**: Start with core steering and expand only with review-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 review\n- **Grep if needed**: Search codebase for pattern validation or integration checks\n- **Interactive**: Engage with user throughout the review process\n\n## Output Description\nProvide output in the language specified in spec.json with:\n\n1. **Review Summary**: Brief overview (2-3 sentences) of design quality and readiness\n2. **Critical Issues**: Maximum 3, following design-review.md format\n3. **Design Strengths**: 1-2 positive aspects\n4. **Final Assessment**: GO\u002FNO-GO decision with rationale and next steps\n\n**Format Requirements**:\n- Use Markdown headings for clarity\n- Follow design-review.md output format\n- Keep summary concise\n\n## Safety & Fallback\n\n### Error Scenarios\n- **Missing Design**: If design.md doesn't exist, stop with message: \"Run `$kiro-spec-design $1` first to generate design document\"\n- **Design Not Generated**: If design phase not marked as generated in spec.json, warn but proceed with review\n- **Empty Steering Directory**: Warn user that project context is missing and may affect review quality\n- **Language Undefined**: Default to English (`en`) if spec.json doesn't specify language\n\n### Next Phase: Task Generation\n\n**If Design Passes Validation (GO Decision)**:\n- Review feedback and apply changes if needed\n- Run `$kiro-spec-tasks $1` to generate implementation tasks\n- Or `$kiro-spec-tasks $1 -y` to auto-approve and proceed directly\n\n**If Design Needs Revision (NO-GO Decision)**:\n- Address critical issues identified\n- Re-run `$kiro-spec-design $1` with improvements\n- Re-validate with `$kiro-validate-design $1`\n\n**Note**: Design validation is recommended but optional. Quality review helps catch issues early.\n",{"name":5,"metadata":24,"description":7},{"shared-rules":25},"design-review.md","main","2259916910e45633c21f5760d7fe329addc415a7","tools\u002Fcc-sdd\u002Ftemplates\u002Fagents\u002Fcodex-skills\u002Fskills\u002Fkiro-validate-design",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-design",{"tool":39,"command":40},"bunx","bunx skills add Huruikagi\u002Fspecbind --skill kiro-validate-design",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Huruikagi\u002Fspecbind --skill kiro-validate-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fcc-sdd\u002Ftemplates\u002Fagents\u002Fcodex-skills\u002Fskills\u002Fkiro-validate-design\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",171,"https:\u002F\u002Fgithub.com\u002FHuruikagi\u002Fspecbind\u002Fblob\u002Fmain\u002Ftools\u002Fcc-sdd\u002Ftemplates\u002Fagents\u002Fcodex-skills\u002Fskills\u002Fkiro-validate-design\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",[],[]]