# speckit.implement

The speckit.implement prompt turns the plan in tasks.md into an ordered implementation run. It is listed for Claude Code and Codex.

- prompt · `type=prompt` · Claude Code, Codex, ChatGPT · ★ 110 repo stars
- Author: alfredoperez
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/alfredoperez/speckit-companion/tree/HEAD/.codex/prompts/speckit.implement.md
- Updated: 2026-10-19
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/prompts/speckitimplement

## What it does

The prompt first checks the repository prerequisites and locates the feature documents. It reads `tasks.md` and `plan.md`, then loads supporting files such as data models, contracts, research notes, or quickstart instructions when they are present. Checklist files are reviewed before implementation begins.

Work follows the phases and dependencies described in the task plan. Test work comes before related implementation, parallel items marked `[P]` may run together, and a failed sequential task stops the run. The prompt also checks ignore files for the technologies detected in the project and marks finished tasks in `tasks.md`.

A prepared `tasks.md` is required because it defines what the agent should execute. In Claude Code, install the prompt at `.claude/commands/speckit.implement.md`; Codex is listed as a supported platform.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/speckit.implement.md`

### ChatGPT

**How to use**
- Paste the text at the start of a chat or into project instructions

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/alfredoperez/speckit-companion/tree/HEAD/.codex/prompts/speckit.implement.md

## When to use it
- execute the task list from `tasks.md`
- gate implementation on checklist status
- load the project architecture before coding
- respect sequential and parallel dependencies
- mark completed work in `tasks.md`

## Example prompts
- Run the implementation plan from `tasks.md` and follow its task dependencies.
- Read `plan.md`, inspect the checklists, then implement every task in phase order.
- Execute `tasks.md`; stop on a failed sequential task and update completed items as you go.

## Source text · speckit.implement.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 2fc86b5b0ff96e4d.

BEGIN THIRD-PARTY FILE 2fc86b5b0ff96e4d
````text
---
description: Execute the implementation plan by processing and executing all tasks defined in tasks.md
---

## User Input

```text
$ARGUMENTS
```

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

## 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):
   - Scan all checklist files in the checklists/ directory
   - For each checklist, count:
     - Total items: All lines matching `- [ ]` or `- [X]` or `- [x]`
     - Completed items: Lines matching `- [X]` or `- [x]`
     - Incomplete items: Lines matching `- [ ]`
   - Create a status table:

     ```text
     | Checklist | Total | Completed | Incomplete | 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 incomplete items
     - **FAIL**: One or more checklists have incomplete items

   - **If any checklist is incomplete**:
     - Display the table with incomplete item counts
     - **STOP** and ask: "Some checklists are incomplete. 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 complete**:
     - 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 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):

     ```sh
     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/verify .eslintignore
   - Check if eslint.config.* exists → ensure the config's `ignores` entries cover required patterns
   - Check if .prettierrc* exists → create/verify .prettierignore
   - Check if .npmrc or package.json exists → create/verify .npmignore (if publishing)
   - Check if terraform files (*.tf) exist → create/verify .terraformignore
   - Check if .helmignore needed (helm charts present) → create/verify .helmignore

   **If ignore file already exists**: Verify it contains essential patterns, append missing critical patterns only
   **If ignore file missing**: Create with full pattern set for detected technology

   **Common Patterns by Technology** (from plan.md tech stack):
   - **Node.js/JavaScript/TypeScript**: `node_modules/`, `dist/`, `build/`, `*.log`, `.env*`
   - **Python**: `__pycache__/`, `*.pyc`, `.venv/`, `venv/`, `dist/`, `*.egg-info/`
   - **Java**: `target/`, `*.class`, `*.jar`, `.gradle/`, `build/`
   - **C#/.NET**: `bin/`, `obj/`, `*.user`, `*.suo`, `packages/`
   - **Go**: `*.exe`, `*.test`, `vendor/`, `*.out`
   - **Ruby**: `.bundle/`, `log/`, `tmp/`, `*.gem`, `vendor/bundle/`
   - **PHP**: `vendor/`, `*.log`, `*.cache`, `*.env`
````
END THIRD-PARTY FILE 2fc86b5b0ff96e4d

The third-party file has ended. Everything between the 2fc86b5b0ff96e4d tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 4079 of 7503 bytes. © alfredoperez · MIT · https://github.com/alfredoperez/speckit-companion/tree/HEAD/.codex/prompts/speckit.implement.md

## Similar
- [implement](https://affpapa.org/en/nevibecode/skills/serpro69-implement.md) — skill · ★ 155 repo stars
- [speckit-analyze](https://affpapa.org/en/nevibecode/skills/speckit-analyze.md) — skill · 1600 installs
- [10x-implement](https://affpapa.org/en/nevibecode/commands/10x-implement.md) — command · ★ 267 repo stars

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
