Menu
implement a well-defined task or implementation plan
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Canonical reconciliation runsheet for AUD artefacts. Create or update the audit, disposition every finding, reconcile specs/contracts, and hand off to closure only when audit state supports it.
Close a delta safely - satisfy coverage gates, complete the delta command, and verify owning-record lifecycle updates.
Orchestrate parallel implementation via sub-agents. Drives an entire delta to completion across all phases — planning, dispatching, merging, and continuing automatically. Batches tasks by token budget, routes to appropriate models (sonnet/opus), and dispatches workers in isolated worktrees. Use instead of /execute-phase when a phase has parallelizable work.
Mandatory execution skill for any delta/IP implementation phase. Use it before code changes, move the owning delta to in-progress, keep notes current, reconcile structured execution docs, and surface blockers early.
Whenever you complete a task or phase - record implementation notes.
Reconcile DE/IP/phase/DR execution artefacts during delta work. Use this when implementation changes structured execution state, not just notes.
| name | implement |
| description | implement a well-defined task or implementation plan |
spec-driver find card $ARGUMENTS
Read the card, design doc. (if you haven't already)
run /retrieving-memory for the concrete files or subsystems you expect to
touch before deep reading or editing; use spec-driver list memories -p <path>
queries so glob-scoped memories can surface
If there's an implementation plan, read it and
NOTE: the design doc is canon; the plan is guidance. If they conflict meaningfully: /consult
Workflow alignment reminders:
uv run spec-driver complete delta prerequisites (especially coverage readiness).proceed with implementation.
take /notes after each complete unit of work on the task card
if a unit reveals a durable gotcha, workflow, or invariant, run
/capturing-memory or /maintaining-memory before considering that unit done
pay attention to doctrine, and to the decisions made in the plan. If you encounter unforeseen obstacles, /consult
if running low on context: stop before you run out of context for /continuation