Codex Technical Design Document Skill for Scope and Acceptance Criteria
Turn a feature brief into a handoff-ready design with a clear scope, proposed approach, and checkable rollout conditions.
中文Install in Codex
Open the project in Codex with the problem statement, known constraints, and observable acceptance criteria. Try the design document workflow with a fictional feature brief if needed.
- Review `.agents/skills/design-doc-writing/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/design-doc-writing/` in your project and save the reviewed file as `.agents/skills/design-doc-writing/SKILL.md`.
- Start Codex from that project's root, then type `$design-doc-writing` and select the matching skill.
Example task
Write part of a technical design document for this fictional event signup feature. Show its scope and validation.
{"feature":"Save an unfinished signup locally","scope":"single tab","excluded":"cross-device sync","acceptance":"draft survives one refresh"}What to check
State `single tab` as the scope and list `cross-device sync` outside it. Include `draft survives one refresh` as observable acceptance criteria.
Original SKILL.md on GitHub · Updated
Frequently asked question
Should a Codex technical design document always list multiple approaches?
Give one recommended design, its scope, and acceptance criteria. Record alternatives when the reviewer asks for a comparison.