| name | spec-driven-development |
| description | Use the repository SDD workflow for non-trivial behavior, architecture, protocol, persistence, or test changes. Create or update work-item specs under `docs/spec/` before implementation and keep baseline specs synchronized when lasting rules change. |
Spec-Driven Development
This is the Codex skill entrypoint for the repository SDD workflow.
Keep this file short. Detailed workflow rules live in WORKFLOW.md inside this skill directory.
When To Use
- New user-facing features
- Non-trivial bug fixes
- Behavior changes in editor, inspector, canvas, build, or save/reload flows
- Architecture, protocol, persistence, runtime ownership, or performance changes
- Refactors that change stable interfaces or module boundaries
- Tests that redefine expected behavior rather than only mechanics
Command Entry
For non-trivial repository work in Codex, read this workflow first:
.agents/skills/spec-driven-development/WORKFLOW.md
Then use these repository sources of truth:
- Workflow guide:
docs/spec-driven-development.md
- Spec index and baseline map:
docs/spec/README.md
- Work-item specs:
docs/spec/<short-slug>.md
For bug fixes, the default expectation is root-cause-first: identify why the bug happens before implementing the fix.
Canonical References
