speckit.implement

A command that carries out every task listed in a feature's tasks.md file. It reads the related project guidance, specification, and implementation plan first.

In plain words
What is it for?
Use it to implement a feature after its specification, plan, and task list have been created.
Why use it?
It keeps implementation work in the planned order and records completed checklist items, while stopping when a task fails.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/github/spec-kit/speckit.implement
Clone the repo
git clone --depth 1 https://github.com/github/spec-kit
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 165 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00165
Opus 5 $0.00006 $0.00082
Sonnet 5 $0.00002 $0.00033
Haiku 4.5 $0.00001 $0.00016

Measured 2d ago against content hash d50654ebfad9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

speckit.implement scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

presets/lean/commands/speckit.implement.md · 23 lines

What it actually says

User Input

$ARGUMENTS

Outline

  1. Read .specify/feature.json to get the feature directory path.

  2. Load context: .specify/memory/constitution.md and <feature_directory>/spec.md and <feature_directory>/plan.md and <feature_directory>/tasks.md.

  3. Execute tasks in order:

    • Complete each task before moving to the next
    • Mark completed tasks by changing - [ ] to - [x] in <feature_directory>/tasks.md
    • Halt on failure and report the issue
  4. Validate: Verify all tasks are completed and the implementation matches the spec.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 23 lines · 12 tokens per session scan A d50654ebfad9

Subscribe to this mod's changes

speckit.implement is a command published in the GitHub repository github/spec-kit (132,298 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 165 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other commands, from other repositories