| name | task-generation |
| description | Comprehensive guide for breaking down Product Requirements Documents (PRDs) into structured, actionable development tasks with dependencies, priorities, and acceptance criteria. Use when generating task breakdowns from PRDs, creating development task lists, or structuring work items for software projects. Essential for converting high-level requirements into granular, executable development tasks. |
Task Generation
This skill provides comprehensive rules and requirements for generating structured development tasks from Product Requirements Documents (PRDs).
Required Task Fields
Every task MUST have all of these fields:
- id: Sequential integer starting from 1
- description: Specific, actionable task description with file paths and technical details
- success_criteria: Array of 3-7 specific, testable acceptance criteria (MANDATORY - DO NOT SKIP)
- dependencies: Array of task IDs this task depends on (use empty array
[] if none)
- suggested_role: One of "backend", "frontend-ui", or "frontend-logic"
- priority: Integer 1-100 (1 = highest priority/critical path, 100 = nice-to-have)
User Story Format Examples
CRITICAL: Task descriptions MUST be in user story format: "As a [role], I need/want [capability] so [benefit]"
The description field MUST follow user story format. Technical details belong in success_criteria, NOT in descriptions.
✅ CORRECT Examples (User Story Format):
-
Backend Setup Task:
- Description: "As a developer, I need a Next.js backend API project scaffolded so I have a foundation for all API endpoints."
- Title: "Initialize Next.js Backend Project"
