planning-and-task-breakdown
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
Security Assessment
About planning-and-task-breakdown
The Planning and Task Breakdown skill helps users decompose large, complex work into small, actionable, and verifiable tasks. It is designed to solve the common problem of overwhelming or unclear projects by providing a structured methodology for planning, task sequencing, and dependency management. By breaking work into discrete, manageable units, the skill ensures that each task can be implemented, tested, and verified in a focused session, reducing the risk of errors and enhancing reliability.
Key features of this skill include creating a dependency graph to identify the correct implementation order, vertical slicing to build complete feature paths rather than isolated layers, and detailed task documentation with clear descriptions, acceptance criteria, and verification steps. Users are guided to prioritize high-risk tasks, arrange tasks so dependencies are satisfied, and establish checkpoints after every few tasks to ensure continuous validation of the work. Additionally, the skill provides task sizing guidelines to categorize tasks from XS (single function or config change) to L (multi-file feature slices), supporting effective scope estimation and resource planning.
This skill is ideal for developers, project managers, or AI agents tasked with implementing software features or complex workflows. It is particularly useful when starting large tasks, estimating project scope, parallelizing work across teams, or communicating implementation plans to stakeholders. Use cases include breaking down feature development for a web application, preparing structured work plans for multi-agent AI systems, or organizing tasks for iterative delivery in agile environments.
FAQ
When should I use the Planning and Task Breakdown skill?
Use this skill when you have a specification and need to decompose it into implementable tasks, when a task is too large or unclear to start, when work needs parallelization, or when communicating scope to humans or agents.
Can I use this skill for small, single-file changes?
No, it is not intended for tasks with obvious scope or when the specification already contains well-defined tasks. It's best for larger or more complex work.
Does the skill handle actual code implementation?
No, the skill operates in a planning mode and focuses on generating a structured plan with tasks, dependencies, and checkpoints. Implementation should occur separately.
How are tasks prioritized and verified?
Tasks are arranged based on dependencies, with high-risk tasks early. Verification includes automated tests, build success checks, and manual checks, with explicit checkpoints after every 2-3 tasks.
What guidelines exist for task sizing?
Tasks are sized based on files and scope: XS (single function), S (1-2 files/component), M (3-5 files/feature slice), and L (5+ files). This helps estimate effort and organize work efficiently.
Install planning-and-task-breakdown
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
addyosmani/agent-skills