speckit-implement

name	speckit-implement
description	Execute the implementation plan by processing and executing all tasks defined in tasks.md
scripts	{"sh":"scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks","ps":"scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks","py":"scripts/python/check_prerequisites.py --json --require-tasks --include-tasks"}

Vendored GitHub Spec Kit command template (v1.0.1). Do not run specify init inside this Express app. Use these skills for constitution / specify / plan / tasks / implement (and clarify / analyze / checklist / converge / taskstoissues). Greenfield: specify init --here --integration cursor-agent. CLI pin: uv tool install specify-cli --from git+https://github.com/github/spec-kit.git@v1.0.1. Helper scripts: this pack's scripts/ directory. Document templates: this pack's references/.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Pre-Execution Checks

Check for extension hooks (before implementation):

• Check if .specify/extensions.yml exists in the project root.
• If it exists, read it and look for entries under the hooks.before_implement key
• If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
• Filter out hooks where enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
• For each remaining hook, do not attempt to interpret or evaluate hook condition expressions:
  • If the hook has no condition field, or it is null/empty, treat the hook as executable
  • If the hook defines a non-empty condition, skip the hook and leave condition evaluation to the HookExecutor implementation
• For each executable hook, output the following based on its optional flag:
  • Optional hook (optional: true):

    ## Extension Hooks
    
    **Optional Pre-Hook**: {extension}
    Command: `/{command}`
    Description: {description}
    
    Prompt: {prompt}
    To execute: `/{command}`
    

  • Mandatory hook (optional: false):

    ## Extension Hooks
    
    **Automatic Pre-Hook**: {extension}
    Executing: `/{command}`
    EXECUTE_COMMAND: {command}
    
    Wait for the result of the hook command before proceeding to the Outline.
    

    After emitting the block above you MUST actually invoke the hook and wait for it to finish before continuing. Run it the same way you would run the command yourself in this agent/session (the invocation may differ from the literal {command} id shown above, e.g. a skills-mode agent runs it as /skill:speckit-... or $speckit-...). Emitting the block alone does not run the hook.
• If no hooks are registered or .specify/extensions.yml does not exist, skip silently

Outline

1. Run {SCRIPT} 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").

2. Check checklists status (if FEATURE_DIR/checklists/ exists):

   • Treat checklist markers as a read-only gate: scan checkbox state, report status, and ask before proceeding when needed; do NOT modify checklist files or markers

   • checklists/requirements.md is the built-in spec-quality checklist maintained by __SPECKIT_COMMAND_SPECIFY__ and __SPECKIT_COMMAND_CLARIFY__; custom checklists generated by __SPECKIT_COMMAND_CHECKLIST__ are reviewer-owned requirements-quality review artifacts

   • For custom checklists, [x] means the reviewer determined the requirements-quality criterion is satisfied; it does NOT mean implementation work is complete

   • Scan all checklist files in the checklists/ directory

   • For each checklist, count:

     • Total items: All lines matching - [ ] or - [X] or - [x]
     • Checked items: Lines matching - [X] or - [x]
     • Unchecked items: Lines matching - [ ]

   • Create a status table:

     | Checklist | Total | Checked | Unchecked | Status |
     |-----------|-------|---------|-----------|--------|
     | ux.md     | 12    | 12      | 0         | ✓ PASS |
     | test.md   | 8     | 5       | 3         | ✗ FAIL |
     | security.md | 6   | 6       | 0         | ✓ PASS |
     

   • Calculate overall status:

     • PASS: All checklists have 0 unchecked items
     • FAIL: One or more checklists have unchecked items

   • If any checklist has unchecked items:

     • Display the table with unchecked item counts
     • STOP and ask: "Some checklists have unchecked items. Do you want to proceed with implementation anyway? (yes/no)"
     • Wait for user response before continuing
     • If user says "no" or "wait" or "stop", halt execution
     • If user says "yes" or "proceed" or "continue", proceed to step 3

Note: This command assumes a complete task breakdown exists in tasks.md. If tasks are incomplete or missing, suggest running __SPECKIT_COMMAND_TASKS__ first to regenerate the task list.

Mandatory Post-Execution Hooks

You MUST complete this section before reporting completion to the user.

Check if .specify/extensions.yml exists in the project root.

• If it does not exist, or no hooks are registered under hooks.after_implement, skip to the Completion Report.
• If it exists, read it and look for entries under the hooks.after_implement key.
• If the YAML cannot be parsed or is invalid, skip hook checking silently and continue to the Completion Report.
• Filter out hooks where enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
• For each remaining hook, do not attempt to interpret or evaluate hook condition expressions:
  • If the hook has no condition field, or it is null/empty, treat the hook as executable
  • If the hook defines a non-empty condition, skip the hook and leave condition evaluation to the HookExecutor implementation
• For each executable hook, output the following based on its optional flag:
  • Mandatory hook (optional: false) — You MUST emit EXECUTE_COMMAND: for each mandatory hook:

    ## Extension Hooks
    
    **Automatic Hook**: {extension}
    Executing: `/{command}`
    EXECUTE_COMMAND: {command}
    

    After emitting the block above you MUST actually invoke the hook and wait for it to finish before continuing. Run it the same way you would run the command yourself in this agent/session (the invocation may differ from the literal {command} id shown above, e.g. a skills-mode agent runs it as /skill:speckit-... or $speckit-...). Emitting the block alone does not run the hook.
  • Optional hook (optional: true):

    ## Extension Hooks
    
    **Optional Hook**: {extension}
    Command: `/{command}`
    Description: {description}
    
    Prompt: {prompt}
    To execute: `/{command}`
    

Completion Report

Report final status with summary of completed work.

Done When

• All tasks in tasks.md completed and marked [X]
• Implementation validated against specification, plan, and test coverage
• Extension hooks dispatched or skipped according to the rules in Mandatory Post-Execution Hooks above
• Completion reported to user with summary of completed work