task-breakdownlisted

# Task Breakdown ## Quick Actions & Routing | User Intent | Action | Resource | |-------------|--------|----------| | Reviewing story first | Understand user goal and value | Step 1: Review the User Story | | Identifying tasks | Map implementation layers | `references/task-layers.md` | | Applying task patterns | Use CRUD/feature/integration patterns | `references/task-patterns.md` | | Defining acceptance criteria | Use testable statement format | Step 4: Define Acceptance Criteria | | Creating task issues | Use template | `references/task-template.md` | | Viewing examples | Load sample task set | `examples/example-task-set.md` | ## Command Integration The `/re:create-tasks` command guides task creation in GitHub Projects. This skill provides the methodology for breaking down stories into tasks—including task patterns, acceptance criteria templates, and layer-by-layer decomposition techniques. Load this skill for deeper understanding of task breakdown concepts or when you need guidance beyond what the command provides. ## Overview Task breakdown transforms user stories into concrete, executable work items that can be assigned, tracked, and completed. Tasks represent the actual implementation steps needed to deliver a user story, each with clear acceptance criteria. This skill guides the process of decomposing stories into well-defined tasks suitable for GitHub issue tracking. ## Purpose Tasks are the execution layer in the requirements hierarchy: - **Above**: User Stor