Menu
Plan execution for a delta - refine IP objectives/gates and create the next phase sheet with concrete tasks and verification expectations.
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 | plan-phases |
| description | Plan execution for a delta - refine IP objectives/gates and create the next phase sheet with concrete tasks and verification expectations. |
You are turning design intent into an executable phase plan.
Inputs:
DE-XXX.mdDR-XXX.md (when present)IP-XXX.mdProcess:
DR-XXX.md is missing or blank, stop and run /draft-design-revision unless you have been expicitly instructed otherwise.DR-XXX.md exists but is stale relative to the current ask or DE scope, reconcile the DR first. Clarify with the user if ambiguous./draft-design-revision to revise or append to the DR.IP-XXX.md:
uv run spec-driver create phase "<phase name>" --plan IP-XXX/consult./execute-phase for implementation only after DR, IP, and the active phase sheet tell the same story.Outcomes: