Task Breakdown Skill

# Task Breakdown Skill This skill helps break down work into small, verifiable tasks with explicit acceptance criteria. It is used when you have a spec or clear requirements and need to break work into implementable tasks. It is particularly useful when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. ## Key Capabilities - Decompose work into small, verifiable tasks. - Identify dependencies between components. - Map out a dependency graph. - Slice work vertically for better implementation. - Write tasks with acceptance criteria and verification steps. - Order and checkpoint tasks for efficient progress. ## Example Use Case When developing a new feature for a web application, the Task Breakdown Skill can be used to break down the feature into smaller tasks, ensuring that each task is manageable and can be tested independently. This helps in managing the scope and ensuring that the feature is developed efficiently. ## When to Use - When you have a spec or clear requirements. - When a task feels too large to start. - When you need to estimate scope. - When parallel work is possible. ## When NOT to Use - For single-file changes with obvious scope. - When the spec already contains well-defined tasks.