speckit.implement

An implementation command that assigns independent, parallel-safe tasks to separate coding assistants and handles dependent tasks in order.

In plain words
What is it for?
Use it to implement a Spec Kit task list, especially when some tasks can be worked on independently within the same phase.
Why use it?
It helps complete unrelated work concurrently while respecting tasks that depend on earlier changes.

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-copilot/speckit.implement
Clone the repo
git clone --depth 1 https://github.com/github/spec-kit-copilot
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 414 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.00000 $0.00414
Opus 5 $0.00000 $0.00207
Sonnet 5 $0.00000 $0.00083
Haiku 4.5 $0.00000 $0.00041

Measured 2d ago against content hash e53e08198db7, 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.

spec-kit-presets/copilot-sub-agents/commands/speckit.implement.md · 33 lines

What it actually says

Sub-Agent Delegation

When executing this command, delegate independent work to parallel sub-agents to reduce total execution time.

How to dispatch sub-agents in Copilot:

  • VS Code: Use the runSubagent tool to spawn each sub-agent in an isolated context.
  • CLI: Delegate to a sub-agent process — Copilot CLI automatically manages subsidiary sub-agent execution. You can also target custom agents defined in .github/agents/ or ~/.copilot/agents/.

Parallel Task Execution

When processing tasks within a phase, identify all tasks marked with [P] (parallel-safe). Dispatch each parallel-safe task as a separate sub-agent:

  • For each [P] task in the current phase: → Sub-agent: "Implement task {TaskID}: {description}. Context: {relevant plan/spec excerpts}. File path: {target file}. Return: confirmation of completion, files created/modified, and any issues encountered."

Rules for sub-agent dispatch:

  • Only dispatch tasks within the same phase — never cross phase boundaries
  • Sequential tasks (without [P]) must run in the main agent, in order
  • If a parallel task depends on a sequential task in the same phase, wait for the sequential task first
  • After all sub-agents for a phase complete, verify results in the main agent before moving to the next phase
  • Mark each completed task as [X] in tasks.md after verifying the sub-agent's output

Context Loading in Parallel

When loading implementation context (step 3), dispatch parallel reads:

  1. Sub-agent: Load plan context — "Read plan.md and extract tech stack, architecture decisions, and file structure. Return a structured summary."
  2. Sub-agent: Load supporting docs — "Read data-model.md, contracts/, research.md, and quickstart.md (whichever exist). Return a consolidated context summary."

Use the consolidated results to inform implementation.

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 · 33 lines · 0 tokens per session scan A e53e08198db7

Subscribe to this mod's changes

speckit.implement is a command published in the GitHub repository github/spec-kit-copilot (11 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 414 tokens. 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.