What is speckit.implement?

A command that executes the tasks in an implementation plan. It first checks that the required feature documents and task file exist, and it reports whether project checklists are complete.

It helps verify prerequisites, inspect checklist completion, and carry out the tasks recorded in tasks.md.

It reduces the chance of starting implementation with missing planning documents or overlooked checklist items. The checklist status shows whether required review work has been finished.

speckit.implement — Command for Claude Code by startvibe

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.

Clone the repo

git clone --depth 1 https://github.com/startvibe/startvibe-cc-marketplace

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/startvibe/startvibe-cc-marketplace/speckit.implement/github.svg)](https://agentmods.dev/commands/startvibe/startvibe-cc-marketplace/speckit.implement)

Your own site

<a href="https://agentmods.dev/commands/startvibe/startvibe-cc-marketplace/speckit.implement"><img src="https://agentmods.dev/badge/commands/startvibe/startvibe-cc-marketplace/speckit.implement/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/startvibe/startvibe-cc-marketplace/speckit.implement"><img src="https://agentmods.dev/badge/commands/startvibe/startvibe-cc-marketplace/speckit.implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,023 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 91% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00014	$0.02023
Opus 5	$0.00007	$0.01012
Sonnet 5	$0.00003	$0.00405
Haiku 4.5	$0.00001	$0.00202

Measured 8d ago against content hash 00120dd2f440, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 8d 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.

Origin

This is a copy

91% identical to speckit.implement — 17 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/speckit.implement.md · 136 lines

How it starts

The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.

User Input

$ARGUMENTS

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

Outline

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").
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:
```
| 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
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

Read the full file on GitHub · 136 lines

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.

8d ago First seen · 136 lines · 14 tokens per session scan A 00120dd2f440

Subscribe to this mod's changes

speckit.implement is a command published in the GitHub repository startvibe/startvibe-cc-marketplace (2 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 2,023 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to speckit.implement, differing in 17 lines, and is treated as a copy.

Planning

speckit.implement

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

User Input

Outline

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

converge

implement

analyze