| name | spec-init |
| description | Start or resume the primary OpenSpec change flow from Codex. Use when Codex should pick the active change and create the next OpenSpec artifact directly. |
| license | MIT |
Start or resume the primary change from Codex.
Core contract
- Codex remains the orchestrator.
- OpenSpec remains the source of truth for change state.
- This is the native entrypoint for the primary spec-driven flow.
Steps
- Confirm OpenSpec is available with
openspec --version.
- Inspect current changes with
openspec list --json.
- If no suitable change exists, create one with
openspec new change "<change-name>".
- Run
openspec status --change "<change-name>" --json to identify the first ready artifact.
- Create or update the next OpenSpec artifact directly from Codex.
- Stop after the change is selected and the next bounded artifact step is clear.
Output
- active change id
- current artifact status
- next artifact Codex should create
- next skill:
spec-plan
Guardrails
- Do not redirect artifact creation into Claude.
- Do not skip OpenSpec status checks.
- Keep change-selection and artifact-progression decisions in Codex.
