Codex release planning with a task dependency graph
Turn a delivery plan into independently shippable tasks, essential blockers, and explicit QA gates while preserving parallel work.
中文Install in Codex
Codex with a milestone plan, task owners, and current board state.
- Review `.agents/skills/create-task-dag/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/create-task-dag/` in your project and save the reviewed file as `.agents/skills/create-task-dag/SKILL.md`.
- Start Codex from that project's root, then type `$create-task-dag` and select the matching skill.
Example task
Turn an ebook release checklist into a task dependency graph.
plan=`ebook-demo`; tasks=`cover, index, qa`; qaNeeds=`cover,index`; coverNeeds=[]; indexNeeds=[]What to check
`cover` and `index` can run in parallel. `qa` waits for both. The two edges are `cover → qa` and `index → qa`.
Original SKILL.md on GitHub · Updated
Frequently asked question
When should a task depend on another task?
Add a dependency when the next task needs the previous deliverable or verification result. Keep independent work parallel.