| name | create-tasks |
| description | Create implementation task plans and task files from complete PRDs and TechSpecs. Use when Codex is asked to create, draft, generate, or save tasks; break a PRD and technical specification into deliverable implementation tasks; define subtasks, success criteria, test requirements, relevant files, rule conformance, or skill conformance; or create files under tasks/prd-[feature-name]/tasks.md and tasks/prd-[feature-name]/[num]_task.md. |
Create Tasks
Core Workflow
Use this skill to turn an existing PRD and TechSpec into approved, implementation-ready task files saved in the project task structure.
Read resources/create-tasks.md before starting. Treat that file as the canonical workflow for this skill.
Load resources/task-list-template.md only when creating tasks.md. Load resources/task-template.md only when creating individual task files. Treat both files as the required task template standards.
Execution Rules
- Confirm and read the PRD at
tasks/prd-[feature-name]/prd.md.
- Confirm and read the TechSpec at
tasks/prd-[feature-name]/techspec.md.
- Analyze requirements, technical decisions, relevant project rules, and relevant project skills.
- Before generating any files, show the high-level task list to the user for approval.
- Do not implement code.
- Make each main task a well-defined deliverable.
- Include unit and integration tests for every main task; include E2E tests where applicable.
- Generate
tasks.md from the exact template in resources/task-list-template.md.
- Generate each
[num]_task.md from the exact template in resources/task-template.md.
- Save files under
tasks/prd-[feature-name]/.
- Report the generated file paths and wait for confirmation before any implementation begins.
Expected Inputs
Typical input is a PRD/TechSpec directory, feature name, or request such as:
- "Use $create-tasks for tasks/prd-team-invitations."
- "Create implementation tasks for the checkout-flow PRD and TechSpec."
- "Generate task files from this PRD and technical specification."
If the feature directory is unclear, inspect tasks/prd-* directories and ask for clarification only when multiple plausible feature folders exist.
