[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CZQX02WR3NWDZ76VB7YZWB":3,"skill-same:01M6CZQX02WR3NWDZ76VB7YZWB":96},{"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":28,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6CZQX02WR3NWDZ76VB7YZWB","kiro-validate-design",null,"Interactive technical design quality review and validation","j5ik2o\u002Fai-tools","j5ik2o","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F461711?v=4","01M6CR6HZJM242J0HDRJT5GY6J","Junichi Kato","01M6CZP6PXKYDDNX5A7PZ3P4DY",28,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fj5ik2o\u002Fai-tools\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkiro-validate-design\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39],"design","validate","kiro","kiro validate design","review","validation","quality","technical","interactive","quality review","technical design","2026-11-10 10:12:30",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\u002Fspecs\u002F$1\u002Fspec.json` for language and metadata\n   - Read `.kiro\u002Fspecs\u002F$1\u002Frequirements.md` for requirements\n   - Read `.kiro\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\u002Fspecs\u002F$1\u002Fspec.json` for language and metadata\n   - Read `.kiro\u002Fspecs\u002F$1\u002Frequirements.md` for requirements\n   - Read `.kiro\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":45,"description":7},{"shared-rules":46},"design-review.md","main","3e6b722545091ed1bb6b81fe15f38189099154c1",".agents\u002Fskills\u002Fkiro-validate-design",0,"https:\u002F\u002Fgithub.com\u002Fj5ik2o\u002Fai-tools","https:\u002F\u002Fgithub.com\u002Fj5ik2o","https:\u002F\u002Flapras.com\u002Fpublic\u002FNHXS5RH","I'm a tech-lead in the IDEO;PLUS Inc, is lover to Scala\u002FRust, Akka, DDD\u002FCQRS+Event Sourcing.","2026-11-12 10:31:08",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add j5ik2o\u002Fai-tools --skill kiro-validate-design",{"tool":62,"command":63},"bunx","bunx skills add j5ik2o\u002Fai-tools --skill kiro-validate-design",{"tool":65,"command":66},"pnpm","pnpm dlx skills add j5ik2o\u002Fai-tools --skill kiro-validate-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fj5ik2o\u002Fai-tools\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkiro-validate-design\u002FSKILL.md",true,[70,76,80,84,88,92],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"agents\u002Fopenai.yaml","REFERENCE","参考文档",171,"https:\u002F\u002Fgithub.com\u002Fj5ik2o\u002Fai-tools\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkiro-validate-design\u002Fagents\u002Fopenai.yaml",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fcwv-thresholds.md",5159,"https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fseo\u002Freferences\u002Fcwv-thresholds.md",{"path":81,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Feeat-framework.md",7452,"https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fseo\u002Freferences\u002Feeat-framework.md",{"path":85,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fquality-gates.md",5210,"https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fseo\u002Freferences\u002Fquality-gates.md",{"path":89,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fschema-types.md",6276,"https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fseo\u002Freferences\u002Fschema-types.md",{"path":93,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":94,"sourceHtmlUrl":95},"rules\u002Fdesign-review.md",4369,"https:\u002F\u002Fgithub.com\u002Fj5ik2o\u002Fai-tools\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkiro-validate-design\u002Frules\u002Fdesign-review.md",[97,110,117,138,149,161],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":106,"publishedAt":40},"01M6D03X604YGMM6YFEG4M6767","takt","TAKT ワークフローエンジン。Agent Team を使ったマルチエージェントオーケストレーション。ワークフロー YAML（steps \u002F initial_step）に従ってマルチエージェントを実行する。","https:\u002F\u002Fgithub.com\u002Fj5ik2o\u002Fai-tools\u002Fblob\u002Fmain\u002Fplugins\u002Ftakt\u002Fskills\u002Fj5ik2o-takt-workflow-builder\u002Freferences\u002Ftakt\u002Fbuiltins\u002Fskill\u002FSKILL.md",[103],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[99,107,108,109],"agent team","team","yaml",{"skillNo":111,"name":99,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":40},"01M6D03TAJ6WKRV6XACZHZ70NS","TAKT ワークフローエンジン。codex exec でサブエージェントを起動し、ワークフロー YAML（steps \u002F initial_step）に従って マルチエージェントオーケストレーションを実行する。","https:\u002F\u002Fgithub.com\u002Fj5ik2o\u002Fai-tools\u002Fblob\u002Fmain\u002Fplugins\u002Ftakt\u002Fskills\u002Fj5ik2o-takt-workflow-builder\u002Freferences\u002Ftakt\u002Fbuiltins\u002Fskill-codex\u002FSKILL.md",[],[99,109,116],"codex",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":127,"publishedAt":40},"01M6D02V9SQ13TEDYDGN67K3WA","j5ik2o-takt-workflow-builder","TAKTワークフロー（ワークフローYAML）の作成・カスタマイズスキル。Faceted Prompting （Persona\u002FPolicy\u002FInstruction\u002FKnowledge\u002FOutput Contract）に基づくファセット群の 生成を含む。references\u002Ftaktにあるtaktのソースコード・ドキュメント・ビルトインワークフロー群を 参照資料として活用する。ユーザーの要件をヒアリングし、step構成、ルール設計、 ファセットファイル生成を一括で行う。 トリガー：「ワークフローを作りたい」「ワークフローを定義」「taktのワークフローを作成」 「新しいtaktワークフローを作って」「takt workflow」「ワークフローYAML」","https:\u002F\u002Fgithub.com\u002Fj5ik2o\u002Fai-tools\u002Fblob\u002Fmain\u002Fplugins\u002Ftakt\u002Fskills\u002Fj5ik2o-takt-workflow-builder\u002FSKILL.md",[123,124],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":125,"categoryName":126,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[128,99,129,130,131,132,133,134,135,136,137],"j5ik2o takt workflow builder","builder","workflow builder","workflow","生成","contract","references","knowledge","persona","policy",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":40},"01M6D02P0Y4DEJ19J6V4S5VZ2S","j5ik2o-takt-task-builder","TAKTのtasks.yaml（タスクメタデータ）とタスクディレクトリ（.takt\u002Ftasks\u002F{slug}\u002Forder.md）の 作成・編集を支援するスキル。TaskRecordスキーマに準拠したYAMLエントリの生成、 order.mdタスク仕様書の作成、ステータス遷移ルールの検証を行う。 references\u002Ftaktにあるtaskスキーマ定義・ドキュメントを参照資料として活用する。 トリガー：「タスクを追加」「tasks.yamlを編集」「taktタスクを作成」 「タスク仕様書を書く」「order.mdを作成」「takt task」「タスクを定義」 「pendingタスクを追加」「GitHub Issueからタスク作成」","https:\u002F\u002Fgithub.com\u002Fj5ik2o\u002Fai-tools\u002Fblob\u002Fmain\u002Fplugins\u002Ftakt\u002Fskills\u002Fj5ik2o-takt-task-builder\u002FSKILL.md",[],[99,145,146,129,134,132,109,147,148],"j5ik2o takt task builder","task","tasks","github",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":40},"01M6D022WYSR825B6KB2CSNNY0","j5ik2o-takt-skill-updater","nrslib\u002Ftakt の新バージョンリリース時に、takt-*スキル群（j5ik2o-takt-task-builder, j5ik2o-takt-workflow-builder, j5ik2o-takt-facet-builder, j5ik2o-takt-analyzer, j5ik2o-takt-optimizer）を最新のtaktバージョンに追従させるスキル。 TypeScriptスキーマ（taskRecordSchemas.ts \u002F taskExecutionSchemas.ts）、ワークフローYAML、ファセットMarkdownの差分を検出し、 SKILL.md・参照ドキュメント（task-schema.md等）を体系的に更新する。 トリガー：「taktスキルを更新」「takt-*スキルの鮮度チェック」「taktバージョンアップ対応」 「スキルが古くないか確認」「takt skill updater」","https:\u002F\u002Fgithub.com\u002Fj5ik2o\u002Fai-tools\u002Fblob\u002Fmain\u002Fplugins\u002Ftakt\u002Fskills\u002Fj5ik2o-takt-skill-updater\u002FSKILL.md",[155],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},[99,157,158,131,159,129,146,160],"skill updater","j5ik2o takt skill updater","schema","optimizer",{"skillNo":162,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":166,"publishedAt":40},"01M6D01Z6WJEXJTXRKEK6N2NBM","https:\u002F\u002Fgithub.com\u002Fj5ik2o\u002Fai-tools\u002Fblob\u002Fmain\u002Fplugins\u002Ftakt\u002Fskills\u002Fj5ik2o-takt-optimizer\u002Freferences\u002Ftakt\u002Fbuiltins\u002Fskill\u002FSKILL.md",[165],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},[99,108,107,109]]