/speckit-implement

name: "speckit-implement"
description: "Execute the implementation plan by processing and executing all tasks defined in tasks.md"
argument-hint: "Optional implementation guidance or task filter"
compatibility: "Requires spec-kit project structure with .specify/ directory"
metadata:
  author: "github-spec-kit"
  source: "templates/commands/implement.md"
user-invocable: true
disable-model-invocation: false

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, do not skip silently: tell the user that `.specify/extensions.yml` could not be read (include the parser error) and that no hooks were checked, including any mandatory (`optional: false`) hooks registered there, then 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
• When constructing command invocations from hook command names, replace dots (`.`) with hyphens (`-`). For example, `speckit.git.commit` → `/speckit-git-commit`.
• 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 `.specify/scripts/bash/check-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").

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-specify` and `/speckit-clarify`; custom checklists generated by `/speckit-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

• **If all checklists are checked**:
• Display the table showing all checklists passed
• Automatically proceed to step 3

3. Load and analyze the implementation context:

• **REQUIRED**: Read tasks.md for the complete task list and execution plan
• **REQUIRED**: Read plan.md for tech stack, architecture, and file structure
• **IF EXISTS**: Read data-model.md for entities and relationships
• **IF EXISTS**: Read contracts/ for API specifications and test requirements
• **IF EXISTS**: Read research.md for technical decisions and constraints
• **IF EXISTS**: Read .specify/memory/constitution.md for governance constraints
• **IF EXISTS**: Read quickstart.md for integration scenarios

4. **Project Setup Verification**:

• **REQUIRED**: Create/verify ignore files based on actual project setup:

**Detection & Creation Logic**:

• Check if the following command succeeds to determine if the repository is a git repo (create/verify .gitignore if so):

     git rev-parse --git-dir 2>/dev/null

• Check if Dockerfile* exists or Docker in plan.md → create/verify .dockerignore
• Check if .eslintrc* exists → create