← ClaudeAtlas

spec-implementlisted

Orchestrate parallel implementation of a feature specification by dispatching coder agents batch-by-batch with code review gates between batches. Use this skill when the user says "implement this feature", "start implementing", "run the spec", "execute the plan", "continue implementing", or wants to begin coding a previously planned feature from a specs/{feature}/ folder. Also use when the user says "/spec-implement" (or their host's equivalent invocation syntax) or drags a spec folder into the conversation and asks to implement it. This skill does NOT write code itself — it orchestrates coder subagents that work in parallel.
benjaminthomas/spec-driven-dev · ★ 1 · AI & Automation · score 72
Install: claude install-skill benjaminthomas/spec-driven-dev
# Implement Feature Orchestrate the parallel implementation of a feature specification by dispatching coder agents batch-by-batch. This skill reads a spec folder (created by `spec-create`), identifies the next batch of parallelizable work, spawns coder agents for each task, and runs a code review gate before moving to the next batch. The orchestrator never writes code itself. Its job is to: 1. Parse the spec and determine what to do next 2. Give each coder agent exactly the context it needs 3. Verify the results via code review 4. Manage the fix loop if review finds issues 5. Track progress and commit completed batches ## Orchestration Model This skill's parallelism assumes your host can run multiple independent agents at once — Claude Code's Agent/Task tool, Codex CLI's `spawn_agent`/`wait_agent`, Cursor's Subagents or Background Agents, Antigravity's `invoke_subagent`, or whatever equivalent your host provides. Use that mechanism throughout; give each dispatched agent only the context specified in Step 4 below, never the full conversation history. If your host has no such mechanism, fall back to processing each batch's tasks sequentially in the current session — implement one task fully, then the next — rather than skipping the batch. The review gate (Step 6) still applies; run it as a distinct pass with a fresh, unbiased read of the diff, even without a separate agent to run it in. ## Prerequisites A `specs/{feature}/` directory containing: - `README.md` with batch