Codex Spec-Driven Development for Feature Acceptance Criteria
Write a specification for a feature with a user problem, minimal solution, scope, observable acceptance criteria and open questions before implementation.
中文Install in Codex
Open the target project and bring the feature problem, scope boundaries and observable behavior. Follow the project convention for the spec location.
- Review `.agents/skills/spec-driven-development/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/spec-driven-development/` in your project and save the reviewed file as `.agents/skills/spec-driven-development/SKILL.md`.
- Start Codex from that project's root, then type `$spec-driven-development` and select the matching skill.
Example task
Draft a specification for report export using this agreed scope.
{"feature":"report export","format":"csv","included":"current filters","excluded":"scheduled exports","case":"zero matching rows"}What to check
Include `CSV for current filters` and exclude `scheduled exports`. Record what to display for zero matching rows as an open question to resolve before implementation.
Original SKILL.md on GitHub · Updated
Frequently asked question
Is 'export works' sufficient as an acceptance criterion?
Use an observable behavior, such as honoring the current filters. Confirm the desired zero-row behavior and then write it as an observable criterion.