Menu
Whenever you complete a task or phase - record implementation notes.
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.
Reconcile DE/IP/phase/DR execution artefacts during delta work. Use this when implementation changes structured execution state, not just notes.
Mandatory onboarding. Every agent MUST execute this on startup, or as soon as becoming aware of it.
| name | notes |
| description | Whenever you complete a task or phase - record implementation notes. |
Update the card with implementation notes.
If you don't know where it is, find it with spec-driver find.
be concise, but record:
.spec-driver changes were committed promptly per repo doctrine, or are still pending with a reasonIf the note identifies a reusable fact/pattern/gotcha that would save a future
agent meaningful time, run /capturing-memory or /maintaining-memory before
you treat the task, phase, or delta as wrapped.
Run spec-driver validate file <touched-artefact> if the note's edit modified frontmatter or block content.