implement-spec

What it does and when to use it

Execute an approved spec's tasks.md test-first, one task per commit, with review subagents. Use when the user asks to implement or continue a spec.

How it works

SKILL.md has no level-two headings · 19 lines, 158 words

---
name: implement-spec
description: Execute an approved spec's tasks.md test-first, one task per commit, with review subagents. Use when the user asks to implement or continue a spec.
---

<!-- Generated from .agents/skills/implement-spec/SKILL.md by scripts/sync_agents.py. Edit the source, not this file. -->

Preconditions: the spec is `Approved` and has `plan.md` and `tasks.md`. If not, stop and
use `/spec-new`.

Loop over unticked tasks in order (respect `[P]` only when working in parallel worktrees):
1. Read the task, the requirements and acceptance criteria it serves.
2. **Tests first**: if the task has no test yet, delegate to `test-engineer`; run the tests
   and confirm they fail for the expected reason.
3. Implement the minimum to make them pass, following AGENTS.md hard rules.
4. `uv run just check` must pass.
5. Do not review each task. Review the branch once, by tier, in `/pre-pr`.
6. Tick the task in `tasks.md`, commit with a Conventional Commit message citing the spec:
   `feat(<scope>): <what> [SPEC-NNNN R<n>]`, signed off (`git commit -s`).

When all tasks are ticked, tick the acceptance criteria in `spec.md`, set status
`Implementing` → leave `Done` to the maintainer, and suggest `/pre-pr`.

Versions

Database snapshot: 13.11.2026 · package version 46c85ea708c6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100spec-implement
  Continue an approved Spec-backed workflow when the user says "implement", "go", "start", or "do it". After Codex Plan Mode, persist the next missing design.md or plan.json artifact and stop. When both artifacts exist, execute plan.json with TDD and report between batches.
• 100flow-next-spec-completion-review
  Spec completion review - verifies all spec tasks implement the spec requirements. Triggers on /flow-next:spec-completion-review.
• 100dx-agent-dev
  Dev Agent: implement code from an RE spec — implement, self-check (build/test/lint), fix failures, commit. Use for 'dev agent', 'implement from spec'.
• 90om-implement-spec
  Implement selected phases of a standalone app specification with routed context, bounded subagents, progress, tests, and review gates without requiring PR automation. Use for "implement this spec", "phase 2", "continue spec", "wdroż specyfikację", or a multi-phase local delivery.
• 100dx-step
  Execute the next pending step in implement.md — implement, test, review, commit, update status. Use to go one step at a time ('next step').
• 90feature
  Implement a feature from a spec (docs/specs/NNN_<name>.md), a spec slice, or a GitHub issue: write the code and tests, run the checks, and stop with a working tree to review. --commit also commits; --pr also opens the PR and runs its review. Use for 'implement the auth spec',…