[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CZSDWKBATB1FQMXCZRKTKN":3,"skill-same:01M6CZSDWKBATB1FQMXCZRKTKN":58},{"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":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M6CZSDWKBATB1FQMXCZRKTKN","kiro-spec-status",null,"Show specification status and progress","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.claude\u002Fskills\u002Fkiro-spec-status\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27],"spec","status","kiro","kiro spec status","grep","read","specification","show","feature","2026-11-10 10:12:30",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\u002Fspecs\u002F$ARGUMENTS\u002Fspec.json` for metadata and phase status\n- Read `.kiro\u002Fspecs\u002F$ARGUMENTS\u002Fbrief.md` if it exists\n- Read existing files: `requirements.md`, `design.md`, `tasks.md` (if they exist)\n- Check `.kiro\u002Fspecs\u002F$ARGUMENTS\u002F` directory for available files\n- Read `.kiro\u002Fsteering\u002Froadmap.md` if it exists and this spec appears in it\n- Read `.kiro\u002Fsettings\u002Ftemplates\u002Fspecs\u002Flocalized-spec-terminology.md` and select section names from `spec.json.language`; stop if the language is missing or unsupported\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 terms using the selected localized terminology for this spec\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\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\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\u002Fspecs\u002F$ARGUMENTS\u002Fspec.json` for metadata and phase status\n- Read `.kiro\u002Fspecs\u002F$ARGUMENTS\u002Fbrief.md` if it exists\n- Read existing files: `requirements.md`, `design.md`, `tasks.md` (if they exist)\n- Check `.kiro\u002Fspecs\u002F$ARGUMENTS\u002F` directory for available files\n- Read `.kiro\u002Fsteering\u002Froadmap.md` if it exists and this spec appears in it\n- Read `.kiro\u002Fsettings\u002Ftemplates\u002Fspecs\u002Flocalized-spec-terminology.md` and select section names from `spec.json.language`; stop if the language is missing or unsupported\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 terms using the selected localized terminology for this spec\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\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\u002Fspecs\u002F` with their status\n",{"name":5,"description":7,"allowed-tools":33,"argument-hint":34},"Read, Glob, Grep","\u003Cfeature-name>","main","3e6b722545091ed1bb6b81fe15f38189099154c1",".claude\u002Fskills\u002Fkiro-spec-status",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":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add j5ik2o\u002Fai-tools --skill kiro-spec-status",{"tool":50,"command":51},"bunx","bunx skills add j5ik2o\u002Fai-tools --skill kiro-spec-status",{"tool":53,"command":54},"pnpm","pnpm dlx skills add j5ik2o\u002Fai-tools --skill kiro-spec-status","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fj5ik2o\u002Fai-tools\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fkiro-spec-status\u002FSKILL.md",true,[],[59,74,81,104,115,127],{"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":70,"publishedAt":28},"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",[65],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[61,71,72,73],"agent team","team","yaml",{"skillNo":75,"name":61,"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":28},"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",[],[61,73,80],"codex",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":93,"publishedAt":28},"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",[87,88],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[94,61,95,96,97,98,99,100,101,102,103],"j5ik2o takt workflow builder","builder","workflow builder","workflow","生成","contract","references","knowledge","persona","policy",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":28},"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",[],[61,111,112,95,100,98,73,113,114],"j5ik2o takt task builder","task","tasks","github",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":122,"publishedAt":28},"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",[121],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},[61,123,124,97,125,95,112,126],"skill updater","j5ik2o takt skill updater","schema","optimizer",{"skillNo":128,"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":129,"categories":130,"keywords":132,"publishedAt":28},"01M6D01Z6WJEXJTXRKEK6N2NBM","https:\u002F\u002Fgithub.com\u002Fj5ik2o\u002Fai-tools\u002Fblob\u002Fmain\u002Fplugins\u002Ftakt\u002Fskills\u002Fj5ik2o-takt-optimizer\u002Freferences\u002Ftakt\u002Fbuiltins\u002Fskill\u002FSKILL.md",[131],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},[61,72,71,73]]