[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KSTKJFNXNBVSJTM20Z1J2D":3,"skill-same:01M6KSTKJFNXNBVSJTM20Z1J2D":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":67},"01M6KSTKJFNXNBVSJTM20Z1J2D","speckit-implement",null,"Execute the implementation plan by processing and executing all tasks defined in tasks.md","ghbvf\u002Fgocell","ghbvf","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104540935?v=4","01M6KSS2CVFY1XK013726EE7ZP","01M6KSS2GJ30TNAVPNFATW578Q",4,"MIT","https:\u002F\u002Fgithub.com\u002Fghbvf\u002Fgocell\u002Fblob\u002Fdevelop\u002F.claude\u002Fskills\u002Fspeckit-implement\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"implement","speckit","speckit implement","structure","implementation plan","true","kit","with","spec-kit","processing","commands","project","directory","plan","templates","specify","tasks","project structure","github","spec","2026-11-10 10:12:30",false,"---\nname: speckit-implement\ndescription: Execute the implementation plan by processing and executing all tasks\n  defined in tasks.md\ncompatibility: Requires spec-kit project structure with .specify\u002F directory\nmetadata:\n  author: github-spec-kit\n  source: templates\u002Fcommands\u002Fimplement.md\ndisable-model-invocation: true\n---\n\n## User Input\n\n```text\n$ARGUMENTS\n```\n\nYou **MUST** consider the user input before proceeding (if not empty).\n\n## Pre-Execution Checks\n\n**Check for extension hooks (before implementation)**:\n- Check if `.specify\u002Fextensions.yml` exists in the project root.\n- If it exists, read it and look for entries under the `hooks.before_implement` key\n- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally\n- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.\n- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:\n  - If the hook has no `condition` field, or it is null\u002Fempty, treat the hook as executable\n  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation\n- For each executable hook, output the following based on its `optional` flag:\n  - **Optional hook** (`optional: true`):\n    ```\n    ## Extension Hooks\n\n    **Optional Pre-Hook**: {extension}\n    Command: `\u002F{command}`\n    Description: {description}\n\n    Prompt: {prompt}\n    To execute: `\u002F{command}`\n    ```\n  - **Mandatory hook** (`optional: false`):\n    ```\n    ## Extension Hooks\n\n    **Automatic Pre-Hook**: {extension}\n    Executing: `\u002F{command}`\n    EXECUTE_COMMAND: {command}\n    \n    Wait for the result of the hook command before proceeding to the Outline.\n    ```\n- If no hooks are registered or `.specify\u002Fextensions.yml` does not exist, skip silently\n\n## Outline\n\n1. Run `.specify\u002Fscripts\u002Fbash\u002Fcheck-prerequisites.sh --json --require-tasks --include-tasks` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like \"I'm Groot\", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: \"I'm Groot\").\n\n2. **Check checklists status** (if FEATURE_DIR\u002Fchecklists\u002F exists):\n   - Scan all checklist files in the checklists\u002F directory\n   - For each checklist, count:\n     - Total items: All lines matching `- [ ]` or `- [X]` or `- [x]`\n     - Completed items: Lines matching `- [X]` or `- [x]`\n     - Incomplete items: Lines matching `- [ ]`\n   - Create a status table:\n\n     ```text\n     | Checklist | Total | Completed | Incomplete | Status |\n     |-----------|-------|-----------|------------|--------|\n     | ux.md     | 12    | 12        | 0          | ✓ PASS |\n     | test.md   | 8     | 5         | 3          | ✗ FAIL |\n     | security.md | 6   | 6         | 0          | ✓ PASS |\n     ```\n\n   - Calculate overall status:\n     - **PASS**: All checklists have 0 incomplete items\n     - **FAIL**: One or more checklists have incomplete items\n\n   - **If any checklist is incomplete**:\n     - Display the table with incomplete item counts\n     - **STOP** and ask: \"Some checklists are incomplete. Do you want to proceed with implementation anyway? (yes\u002Fno)\"\n     - Wait for user response before continuing\n     - If user says \"no\" or \"wait\" or \"stop\", halt execution\n     - If user says \"yes\" or \"proceed\" or \"continue\", proceed to step 3\n\n   - **If all checklists are complete**:\n     - Display the table showing all checklists passed\n     - Automatically proceed to step 3\n\n3. Load and analyze the implementation context:\n   - **REQUIRED**: Read tasks.md for the complete task list and execution plan\n   - **REQUIRED**: Read plan.md for tech stack, architecture, and file structure\n   - **IF EXISTS**: Read data-model.md for entities and relationships\n   - **IF EXISTS**: Read contracts\u002F for API specifications and test requirements\n   - **IF EXISTS**: Read research.md for technical decisions and constraints\n   - **IF EXISTS**: Read quickstart.md for integration scenarios\n\n4. **Project Setup Verification**:\n   - **REQUIRED**: Create\u002Fverify ignore files based on actual project setup:\n\n   **Detection & Creation Logic**:\n   - Check if the following command succeeds to determine if the repository is a git repo (create\u002Fverify .gitignore if so):\n\n     ```sh\n     git rev-parse --git-dir 2>\u002Fdev\u002Fnull\n     ```\n\n   - Check if Dockerfile* exists or Docker in plan.md → create\u002Fverify .dockerignore\n   - Check if .eslintrc* exists → create\u002Fverify .eslintignore\n   - Check if eslint.config.* exists → ensure the config's `ignores` entries cover required patterns\n   - Check if .prettierrc* exists → create\u002Fverify .prettierignore\n   - Check if .npmrc or package.json exists → create\u002Fverify .npmignore (if publishing)\n   - Check if terraform files (*.tf) exist → create\u002Fverify .terraformignore\n   - Check if .helmignore needed (helm charts present) → create\u002Fverify .helmignore\n\n   **If ignore file already exists**: Verify it contains essential patterns, append missing critical patterns only\n   **If ignore file missing**: Create with full pattern set for detected technology\n\n   **Common Patterns by Technology** (from plan.md tech stack):\n   - **Node.js\u002FJavaScript\u002FTypeScript**: `node_modules\u002F`, `dist\u002F`, `build\u002F`, `*.log`, `.env*`\n   - **Python**: `__pycache__\u002F`, `*.pyc`, `.venv\u002F`, `venv\u002F`, `dist\u002F`, `*.egg-info\u002F`\n   - **Java**: `target\u002F`, `*.class`, `*.jar`, `.gradle\u002F`, `build\u002F`\n   - **C#\u002F.NET**: `bin\u002F`, `obj\u002F`, `*.user`, `*.suo`, `packages\u002F`\n   - **Go**: `*.exe`, `*.test`, `vendor\u002F`, `*.out`\n   - **Ruby**: `.bundle\u002F`, `log\u002F`, `tmp\u002F`, `*.gem`, `vendor\u002Fbundle\u002F`\n   - **PHP**: `vendor\u002F`, `*.log`, `*.cache`, `*.env`\n   - **Rust**: `target\u002F`, `debug\u002F`, `release\u002F`, `*.rs.bk`, `*.rlib`, `*.prof*`, `.idea\u002F`, `*.log`, `.env*`\n   - **Kotlin**: `build\u002F`, `out\u002F`, `.gradle\u002F`, `.idea\u002F`, `*.class`, `*.jar`, `*.iml`, `*.log`, `.env*`\n   - **C++**: `build\u002F`, `bin\u002F`, `obj\u002F`, `out\u002F`, `*.o`, `*.so`, `*.a`, `*.exe`, `*.dll`, `.idea\u002F`, `*.log`, `.env*`\n   - **C**: `build\u002F`, `bin\u002F`, `obj\u002F`, `out\u002F`, `*.o`, `*.a`, `*.so`, `*.exe`, `*.dll`, `autom4te.cache\u002F`, `config.status`, `config.log`, `.idea\u002F`, `*.log`, `.env*`\n   - **Swift**: `.build\u002F`, `DerivedData\u002F`, `*.swiftpm\u002F`, `Packages\u002F`\n   - **R**: `.Rproj.user\u002F`, `.Rhistory`, `.RData`, `.Ruserdata`, `*.Rproj`, `packrat\u002F`, `renv\u002F`\n   - **Universal**: `.DS_Store`, `Thumbs.db`, `*.tmp`, `*.swp`, `.vscode\u002F`, `.idea\u002F`\n\n   **Tool-Specific Patterns**:\n   - **Docker**: `node_modules\u002F`, `.git\u002F`, `Dockerfile*`, `.dockerignore`, `*.log*`, `.env*`, `coverage\u002F`\n   - **ESLint**: `node_modules\u002F`, `dist\u002F`, `build\u002F`, `coverage\u002F`, `*.min.js`\n   - **Prettier**: `node_modules\u002F`, `dist\u002F`, `build\u002F`, `coverage\u002F`, `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`\n   - **Terraform**: `.terraform\u002F`, `*.tfstate*`, `*.tfvars`, `.terraform.lock.hcl`\n   - **Kubernetes\u002Fk8s**: `*.secret.yaml`, `secrets\u002F`, `.kube\u002F`, `kubeconfig*`, `*.key`, `*.crt`\n\n5. Parse tasks.md structure and extract:\n   - **Task phases**: Setup, Tests, Core, Integration, Polish\n   - **Task dependencies**: Sequential vs parallel execution rules\n   - **Task details**: ID, description, file paths, parallel markers [P]\n   - **Execution flow**: Order and dependency requirements\n\n6. Execute implementation following the task plan:\n   - **Phase-by-phase execution**: Complete each phase before moving to the next\n   - **Respect dependencies**: Run sequential tasks in order, parallel tasks [P] can run together  \n   - **Follow TDD approach**: Execute test tasks before their corresponding implementation tasks\n   - **File-based coordination**: Tasks affecting the same files must run sequentially\n   - **Validation checkpoints**: Verify each phase completion before proceeding\n\n7. Implementation execution rules:\n   - **Setup first**: Initialize project structure, dependencies, configuration\n   - **Tests before code**: If you need to write tests for contracts, entities, and integration scenarios\n   - **Core development**: Implement models, services, CLI commands, endpoints\n   - **Integration work**: Database connections, middleware, logging, external services\n   - **Polish and validation**: Unit tests, performance optimization, documentation\n\n8. Progress tracking and error handling:\n   - Report progress after each completed task\n   - Halt execution if any non-parallel task fails\n   - For parallel tasks [P], continue with successful tasks, report failed ones\n   - Provide clear error messages with context for debugging\n   - Suggest next steps if implementation cannot proceed\n   - **IMPORTANT** For completed tasks, make sure to mark the task off as [X] in the tasks file.\n\n9. Completion validation:\n   - Verify all required tasks are completed\n   - Check that implemented features match the original specification\n   - Validate that tests pass and coverage meets requirements\n   - Confirm the implementation follows the technical plan\n   - Report final status with summary of completed work\n\nNote: This command assumes a complete task breakdown exists in tasks.md. If tasks are incomplete or missing, suggest running `\u002Fspeckit.tasks` first to regenerate the task list.\n\n10. **Check for extension hooks**: After completion validation, check if `.specify\u002Fextensions.yml` exists in the project root.\n    - If it exists, read it and look for entries under the `hooks.after_implement` key\n    - If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally\n    - Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.\n    - For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:\n      - If the hook has no `condition` field, or it is null\u002Fempty, treat the hook as executable\n      - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation\n    - For each executable hook, output the following based on its `optional` flag:\n      - **Optional hook** (`optional: true`):\n        ```\n        ## Extension Hooks\n\n        **Optional Hook**: {extension}\n        Command: `\u002F{command}`\n        Description: {description}\n\n        Prompt: {prompt}\n        To execute: `\u002F{command}`\n        ```\n      - **Mandatory hook** (`optional: false`):\n        ```\n        ## Extension Hooks\n\n        **Automatic Hook**: {extension}\n        Executing: `\u002F{command}`\n        EXECUTE_COMMAND: {command}\n        ```\n    - If no hooks are registered or `.specify\u002Fextensions.yml` does not exist, skip silently\n","## User Input\n\n```text\n$ARGUMENTS\n```\n\nYou **MUST** consider the user input before proceeding (if not empty).\n\n## Pre-Execution Checks\n\n**Check for extension hooks (before implementation)**:\n- Check if `.specify\u002Fextensions.yml` exists in the project root.\n- If it exists, read it and look for entries under the `hooks.before_implement` key\n- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally\n- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.\n- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:\n  - If the hook has no `condition` field, or it is null\u002Fempty, treat the hook as executable\n  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation\n- For each executable hook, output the following based on its `optional` flag:\n  - **Optional hook** (`optional: true`):\n    ```\n    ## Extension Hooks\n\n    **Optional Pre-Hook**: {extension}\n    Command: `\u002F{command}`\n    Description: {description}\n\n    Prompt: {prompt}\n    To execute: `\u002F{command}`\n    ```\n  - **Mandatory hook** (`optional: false`):\n    ```\n    ## Extension Hooks\n\n    **Automatic Pre-Hook**: {extension}\n    Executing: `\u002F{command}`\n    EXECUTE_COMMAND: {command}\n    \n    Wait for the result of the hook command before proceeding to the Outline.\n    ```\n- If no hooks are registered or `.specify\u002Fextensions.yml` does not exist, skip silently\n\n## Outline\n\n1. Run `.specify\u002Fscripts\u002Fbash\u002Fcheck-prerequisites.sh --json --require-tasks --include-tasks` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like \"I'm Groot\", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: \"I'm Groot\").\n\n2. **Check checklists status** (if FEATURE_DIR\u002Fchecklists\u002F exists):\n   - Scan all checklist files in the checklists\u002F directory\n   - For each checklist, count:\n     - Total items: All lines matching `- [ ]` or `- [X]` or `- [x]`\n     - Completed items: Lines matching `- [X]` or `- [x]`\n     - Incomplete items: Lines matching `- [ ]`\n   - Create a status table:\n\n     ```text\n     | Checklist | Total | Completed | Incomplete | Status |\n     |-----------|-------|-----------|------------|--------|\n     | ux.md     | 12    | 12        | 0          | ✓ PASS |\n     | test.md   | 8     | 5         | 3          | ✗ FAIL |\n     | security.md | 6   | 6         | 0          | ✓ PASS |\n     ```\n\n   - Calculate overall status:\n     - **PASS**: All checklists have 0 incomplete items\n     - **FAIL**: One or more checklists have incomplete items\n\n   - **If any checklist is incomplete**:\n     - Display the table with incomplete item counts\n     - **STOP** and ask: \"Some checklists are incomplete. Do you want to proceed with implementation anyway? (yes\u002Fno)\"\n     - Wait for user response before continuing\n     - If user says \"no\" or \"wait\" or \"stop\", halt execution\n     - If user says \"yes\" or \"proceed\" or \"continue\", proceed to step 3\n\n   - **If all checklists are complete**:\n     - Display the table showing all checklists passed\n     - Automatically proceed to step 3\n\n3. Load and analyze the implementation context:\n   - **REQUIRED**: Read tasks.md for the complete task list and execution plan\n   - **REQUIRED**: Read plan.md for tech stack, architecture, and file structure\n   - **IF EXISTS**: Read data-model.md for entities and relationships\n   - **IF EXISTS**: Read contracts\u002F for API specifications and test requirements\n   - **IF EXISTS**: Read research.md for technical decisions and constraints\n   - **IF EXISTS**: Read quickstart.md for integration scenarios\n\n4. **Project Setup Verification**:\n   - **REQUIRED**: Create\u002Fverify ignore files based on actual project setup:\n\n   **Detection & Creation Logic**:\n   - Check if the following command succeeds to determine if the repository is a git repo (create\u002Fverify .gitignore if so):\n\n     ```sh\n     git rev-parse --git-dir 2>\u002Fdev\u002Fnull\n     ```\n\n   - Check if Dockerfile* exists or Docker in plan.md → create\u002Fverify .dockerignore\n   - Check if .eslintrc* exists → create\u002Fverify .eslintignore\n   - Check if eslint.config.* exists → ensure the config's `ignores` entries cover required patterns\n   - Check if .prettierrc* exists → create\u002Fverify .prettierignore\n   - Check if .npmrc or package.json exists → create\u002Fverify .npmignore (if publishing)\n   - Check if terraform files (*.tf) exist → create\u002Fverify .terraformignore\n   - Check if .helmignore needed (helm charts present) → create\u002Fverify .helmignore\n\n   **If ignore file already exists**: Verify it contains essential patterns, append missing critical patterns only\n   **If ignore file missing**: Create with full pattern set for detected technology\n\n   **Common Patterns by Technology** (from plan.md tech stack):\n   - **Node.js\u002FJavaScript\u002FTypeScript**: `node_modules\u002F`, `dist\u002F`, `build\u002F`, `*.log`, `.env*`\n   - **Python**: `__pycache__\u002F`, `*.pyc`, `.venv\u002F`, `venv\u002F`, `dist\u002F`, `*.egg-info\u002F`\n   - **Java**: `target\u002F`, `*.class`, `*.jar`, `.gradle\u002F`, `build\u002F`\n   - **C#\u002F.NET**: `bin\u002F`, `obj\u002F`, `*.user`, `*.suo`, `packages\u002F`\n   - **Go**: `*.exe`, `*.test`, `vendor\u002F`, `*.out`\n   - **Ruby**: `.bundle\u002F`, `log\u002F`, `tmp\u002F`, `*.gem`, `vendor\u002Fbundle\u002F`\n   - **PHP**: `vendor\u002F`, `*.log`, `*.cache`, `*.env`\n   - **Rust**: `target\u002F`, `debug\u002F`, `release\u002F`, `*.rs.bk`, `*.rlib`, `*.prof*`, `.idea\u002F`, `*.log`, `.env*`\n   - **Kotlin**: `build\u002F`, `out\u002F`, `.gradle\u002F`, `.idea\u002F`, `*.class`, `*.jar`, `*.iml`, `*.log`, `.env*`\n   - **C++**: `build\u002F`, `bin\u002F`, `obj\u002F`, `out\u002F`, `*.o`, `*.so`, `*.a`, `*.exe`, `*.dll`, `.idea\u002F`, `*.log`, `.env*`\n   - **C**: `build\u002F`, `bin\u002F`, `obj\u002F`, `out\u002F`, `*.o`, `*.a`, `*.so`, `*.exe`, `*.dll`, `autom4te.cache\u002F`, `config.status`, `config.log`, `.idea\u002F`, `*.log`, `.env*`\n   - **Swift**: `.build\u002F`, `DerivedData\u002F`, `*.swiftpm\u002F`, `Packages\u002F`\n   - **R**: `.Rproj.user\u002F`, `.Rhistory`, `.RData`, `.Ruserdata`, `*.Rproj`, `packrat\u002F`, `renv\u002F`\n   - **Universal**: `.DS_Store`, `Thumbs.db`, `*.tmp`, `*.swp`, `.vscode\u002F`, `.idea\u002F`\n\n   **Tool-Specific Patterns**:\n   - **Docker**: `node_modules\u002F`, `.git\u002F`, `Dockerfile*`, `.dockerignore`, `*.log*`, `.env*`, `coverage\u002F`\n   - **ESLint**: `node_modules\u002F`, `dist\u002F`, `build\u002F`, `coverage\u002F`, `*.min.js`\n   - **Prettier**: `node_modules\u002F`, `dist\u002F`, `build\u002F`, `coverage\u002F`, `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`\n   - **Terraform**: `.terraform\u002F`, `*.tfstate*`, `*.tfvars`, `.terraform.lock.hcl`\n   - **Kubernetes\u002Fk8s**: `*.secret.yaml`, `secrets\u002F`, `.kube\u002F`, `kubeconfig*`, `*.key`, `*.crt`\n\n5. Parse tasks.md structure and extract:\n   - **Task phases**: Setup, Tests, Core, Integration, Polish\n   - **Task dependencies**: Sequential vs parallel execution rules\n   - **Task details**: ID, description, file paths, parallel markers [P]\n   - **Execution flow**: Order and dependency requirements\n\n6. Execute implementation following the task plan:\n   - **Phase-by-phase execution**: Complete each phase before moving to the next\n   - **Respect dependencies**: Run sequential tasks in order, parallel tasks [P] can run together  \n   - **Follow TDD approach**: Execute test tasks before their corresponding implementation tasks\n   - **File-based coordination**: Tasks affecting the same files must run sequentially\n   - **Validation checkpoints**: Verify each phase completion before proceeding\n\n7. Implementation execution rules:\n   - **Setup first**: Initialize project structure, dependencies, configuration\n   - **Tests before code**: If you need to write tests for contracts, entities, and integration scenarios\n   - **Core development**: Implement models, services, CLI commands, endpoints\n   - **Integration work**: Database connections, middleware, logging, external services\n   - **Polish and validation**: Unit tests, performance optimization, documentation\n\n8. Progress tracking and error handling:\n   - Report progress after each completed task\n   - Halt execution if any non-parallel task fails\n   - For parallel tasks [P], continue with successful tasks, report failed ones\n   - Provide clear error messages with context for debugging\n   - Suggest next steps if implementation cannot proceed\n   - **IMPORTANT** For completed tasks, make sure to mark the task off as [X] in the tasks file.\n\n9. Completion validation:\n   - Verify all required tasks are completed\n   - Check that implemented features match the original specification\n   - Validate that tests pass and coverage meets requirements\n   - Confirm the implementation follows the technical plan\n   - Report final status with summary of completed work\n\nNote: This command assumes a complete task breakdown exists in tasks.md. If tasks are incomplete or missing, suggest running `\u002Fspeckit.tasks` first to regenerate the task list.\n\n10. **Check for extension hooks**: After completion validation, check if `.specify\u002Fextensions.yml` exists in the project root.\n    - If it exists, read it and look for entries under the `hooks.after_implement` key\n    - If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally\n    - Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.\n    - For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:\n      - If the hook has no `condition` field, or it is null\u002Fempty, treat the hook as executable\n      - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation\n    - For each executable hook, output the following based on its `optional` flag:\n      - **Optional hook** (`optional: true`):\n        ```\n        ## Extension Hooks\n\n        **Optional Hook**: {extension}\n        Command: `\u002F{command}`\n        Description: {description}\n\n        Prompt: {prompt}\n        To execute: `\u002F{command}`\n        ```\n      - **Mandatory hook** (`optional: false`):\n        ```\n        ## Extension Hooks\n\n        **Automatic Hook**: {extension}\n        Executing: `\u002F{command}`\n        EXECUTE_COMMAND: {command}\n        ```\n    - If no hooks are registered or `.specify\u002Fextensions.yml` does not exist, skip silently\n",{"name":5,"metadata":43,"description":7,"compatibility":46,"disable-model-invocation":47},{"author":44,"source":45},"github-spec-kit","templates\u002Fcommands\u002Fimplement.md","Requires spec-kit project structure with .specify\u002F directory",true,"develop","043add59bbe840e4a90a4253feec21f074b590dd",".claude\u002Fskills\u002Fspeckit-implement",0,"https:\u002F\u002Fgithub.com\u002Fghbvf\u002Fgocell","https:\u002F\u002Fgithub.com\u002Fghbvf","2026-06-20 14:38:06",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":47},[57,60,63],{"tool":58,"command":59},"npx","npx skills add ghbvf\u002Fgocell --skill speckit-implement",{"tool":61,"command":62},"bunx","bunx skills add ghbvf\u002Fgocell --skill speckit-implement",{"tool":64,"command":65},"pnpm","pnpm dlx skills add ghbvf\u002Fgocell --skill speckit-implement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fghbvf\u002Fgocell\u002Fblob\u002Fdevelop\u002F.claude\u002Fskills\u002Fspeckit-implement\u002FSKILL.md",[],[69,90,105,124,134,141],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":38},"01M6KSVEVMZN9HK0ZRVY3MEJEJ","ship","全流程实施：探索→计划→worktree→TDD→实施→PR→review→\u002Ffix Cx1\u002FCx2→人工确认。L1(跳过探索,1 reviewer)\u002FL2(单agent探索,1 reviewer)\u002FL3(默认,三agent探索,按diff行数1\u002F2\u002F3\u002F6 reviewer自动)","https:\u002F\u002Fgithub.com\u002Fghbvf\u002Fgocell\u002Fblob\u002Fdevelop\u002F.codex\u002Fskills\u002Fship\u002FSKILL.md",[],[71,76,77,78,79,80,81,82,83,84,85,86,87,88,89],"Bash","l2","id","backlog","fix","edit","write","read","reviewer","grep","worktree","pr","tdd","review",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":101,"publishedAt":38},"01M6KSVCP8NB3095MY8M2BR235","pr-review","对指定 PR 跑自动分级六维度 review（默认）；或 --check 模式验证上一轮 findings 是否修复 + 抓回归。按 diff 净增删行数自动分配 2\u002F3\u002F6 reviewer agent 并行（\u003C 200 行不派发，主 agent 自审）；主 agent 做根因聚类 + Cx 分级 + 修复分流建议，不自动 fix。","https:\u002F\u002Fgithub.com\u002Fghbvf\u002Fgocell\u002Fblob\u002Fdevelop\u002F.codex\u002Fskills\u002Fpr-review\u002FSKILL.md",[96],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[87,102,89,85,76,103,84,104,80,83],"pr review","check","diff",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":38},"01M6KSV8P4AYPNHCDR1T7B9YN5","issues","GitHub Issues + Project v2 #3 项目管理单源技能。Part A：epic 拆解 + wave 实施顺序评论（找子任务 → blocked-by DAG → wave 1-4 容量装箱排序：每 wave ≤4、pri 优先、wave 内切并行组\u002F串行链、OPEN 重排、已完成与超窗单列 → 只追加 epic 评论；不写 Project 字段、不改 epic body）。Part B：issue\u002FPR 原子操作（建\u002F改 backlog issue、area\u002Ftype\u002Fpri label、PR 双轴状态 label 流转、统一 PR 评论格式 + 冲突预检\u002FCI watch 跟进，ship\u002Ffix 共用）。非 epic issue 号 → 查代码判状态（只判不修，建议 \u002Fship 或 close）。当用户要整理 epic 排 wave、建\u002F改 backlog issue、贴 label、切 PR 状态、给 PR 留评论、核一个 issue 是否还成立时使用。","https:\u002F\u002Fgithub.com\u002Fghbvf\u002Fgocell\u002Fblob\u002Fdevelop\u002F.codex\u002Fskills\u002Fissues\u002FSKILL.md",[],[107,112,113,114,115,116,117,118,119,29,76,36,80,83,120,121,122,87,123,79],"项目管理","create-issue","labels","整理","EPIC","close","ci watch","type","open","ci","create","dag",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":38},"01M6KSV7CX440Q82S9VXQJH02G","git-worktree","Git Worktree 项目约定（编号、基准分支、权限兼容、删除安全）。","https:\u002F\u002Fgithub.com\u002Fghbvf\u002Fgocell\u002Fblob\u002Fdevelop\u002F.codex\u002Fskills\u002Fgit-worktree\u002FSKILL.md",[],[131,86,132,133],"git","git worktree","安全",{"skillNo":135,"name":80,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":38},"01M6KSV5JB0AR3EJ9V2H4F2MN2","问题诊断与修复: 验证+根因+复杂度分级+修复方案+backlog登记。当用户说'这个问题存在吗''帮我分析这个bug''诊断一下这个模块''修复这个问题'时触发。支持单条问题和多方审查报告批量输入。","https:\u002F\u002Fgithub.com\u002Fghbvf\u002Fgocell\u002Fblob\u002Fdevelop\u002F.codex\u002Fskills\u002Ffix\u002FSKILL.md",[],[80,140,81,82,83,85,76],"文件",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":38},"01M6KSV2S9ZK6BM2K1P2V3E4HK","speckit-taskstoissues","Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.","https:\u002F\u002Fgithub.com\u002Fghbvf\u002Fgocell\u002Fblob\u002Fdevelop\u002F.claude\u002Fskills\u002Fspeckit-taskstoissues\u002FSKILL.md",[],[148,19,21,149,23,24,25,26,150,151,29,152,153,33,107,154,34,35,36,155],"speckit taskstoissues","for","actionable","feature","Existing","convert","artifacts","design"]