| name | Generate Tasks |
| description | Create a detailed, step-by-step task list from requirements or a PRD. Generates parent tasks first for review, then breaks down into sub-tasks.
|
| argument-hint | [prd-path-or-requirements] |
Generate Tasks
Create a detailed task list in Markdown format from user requirements or a PRD.
When to use
- After a PRD is approved
- When you have feature requirements ready for implementation
- Before starting development work
Output
- Format: Markdown (
.md)
- Location:
/tasks/
- Filename:
tasks-[feature-name].md
Process
- Receive requirements: Feature request, task description, or existing documentation
- Analyze requirements: Functional requirements, user needs, implementation scope
- Phase 1 - Generate parent tasks: Create high-level tasks (always include task 0.0 "Create feature branch"). Present to user and wait for "Go"
- Wait for confirmation: Pause for user approval
- Phase 2 - Generate sub-tasks: Break down each parent task into actionable sub-tasks
- Identify relevant files: List files that will need to be created or modified
- Generate final output: Combine into final Markdown structure
- Save task list: Save to
/tasks/ directory
Target audience
Assume the primary reader is a junior developer. Requirements should be explicit and unambiguous.
For the full output format and interaction model, see references/generate-tasks.md.
Follow the writing standards in _shared/writing-standards.md for all outputs.
