| name | spec-plan |
| description | Prepare the execution handoff contract from Codex. Use when a change needs design, task refinement, and a bounded execution packet. |
| license | MIT |
Plan the change from Codex and prepare the execution handoff.
Core contract
- Codex remains the orchestrator.
- Codex owns planning, boundary-setting, and acceptance criteria.
- Claude executes only after Codex has prepared a bounded handoff.
Steps
- Select the active change with
openspec status --change "<change-name>" --json.
- Read
proposal.md, design.md, tasks.md, and all relevant specs/**/*.md.
- Update the OpenSpec artifacts so they clearly define:
- allowed change surface
- protected surface
- work packages
- required verification
- rework triggers
- Ensure
design.md contains an Execution Handoff Contract section.
- Ensure
tasks.md is broken into concrete execution slices that can be implemented without reopening product decisions.
- End by preparing the exact bounded packet Codex will later send for execution.
Output
- change id
- execution goal
- allowed/protected file boundaries
- required verification checklist
- next skill:
spec-impl
Guardrails
- Do not modify product code in this step.
- Do not ask Claude to decide the plan.
- Do not turn the plan into another round of product design debate.
