Planning and Task Breakdown

What Is This

Planning and Task Breakdown is a foundational design skill that involves decomposing a technical specification or requirement into discrete, manageable tasks. The goal is to transform a high-level feature request or vague requirement into a series of implementable units, each with clear boundaries and explicit acceptance criteria. This skill enables teams and agents to work more effectively by ensuring that each task is small enough to be implemented, tested, and verified in a single focused session. The process is particularly important when tasks are too broad, ambiguous, or complex to tackle directly, or when work needs to be distributed across multiple contributors or sessions.

Why Use It

Breaking down work using the Planning and Task Breakdown skill offers several key benefits:

• Clarity and Focus: Large, ambiguous tasks are daunting and error-prone. Decomposing them clarifies what needs to be done and how to proceed.
• Parallelization: Well-defined, independent tasks can be distributed among multiple agents or team members, accelerating delivery.
• Accurate Estimation: Smaller tasks are easier to estimate in terms of scope, time, and resources, leading to better project planning.
• Risk Management: Task breakdown exposes dependencies, risks, and unknowns early, allowing for proactive mitigation.
• Communication: A clear plan provides a roadmap that is easy to share and understand, making progress and scope transparent to stakeholders.
• Quality Assurance: With explicit acceptance criteria for each task, verification and testing become straightforward, reducing the likelihood of defects.

How to Use It

The Planning and Task Breakdown process involves several deliberate steps:

1. Enter Plan

Mode

Before any implementation begins, switch to a read-only, analytical mindset:

• Review the Specification: Carefully read the provided spec or requirements document.
• Understand the Codebase: Identify relevant sections of the codebase and existing patterns or conventions.
• Map Dependencies: Note how different components or features depend on each other.
• Identify Risks: Highlight areas of ambiguity, technical unknowns, or potential blockers.

Do not write any code during this phase. The sole output should be a detailed plan document.

2. Identify the Dependency

Graph

Visualize the order in which tasks must be completed. For example:

Database schema
    │
    ├── API models/types
    │     └── API endpoints
    │           └── Frontend integration

This mapping clarifies which tasks can be worked on in parallel and which must be completed sequentially.

3. Break Down into Implementable

Tasks

• Granularity: Each task should be small enough to complete, test, and verify in a single session.
• Verifiability: Define explicit acceptance criteria for each task.
• Order: List tasks in a logical sequence, respecting dependencies.

Example Plan

Suppose you need to add a "favorite articles" feature:

1. Update database schema to support user favorites
    - Acceptance: Migration applied, schema verified
2. Add API model for favorites
    - Acceptance: Model passes unit tests
3. Implement API endpoints: add/remove favorites
    - Acceptance: Endpoints return correct status and data
4. Integrate favorite/unfavorite actions in frontend
    - Acceptance: UI updates reflect backend state
5. Add tests for end-to-end favorite functionality
    - Acceptance: All tests pass

4. Document and

Communicate

Produce a plan document that lists each task, its acceptance criteria, and any dependencies. Share this with stakeholders or team members before starting implementation.

When to Use It

Planning and Task Breakdown is best employed when:

• You have a specification or clear requirements but no defined implementation plan
• A task feels too large or vague to begin
• Work needs to be parallelized across multiple agents or sessions
• You need to estimate scope or communicate progress to others
• The order of implementation is not obvious

Do not use this skill if the change is minor, easily scoped (such as a single-file edit), or if the specification already contains well-defined, granular tasks.

Important Notes

• Stay in Plan Mode: Resist the urge to prototype or write code before the plan is complete. This ensures a thorough analysis and more reliable results.
• Be Explicit: Each task should have clear, objective acceptance criteria.
• Avoid Over-Fragmentation: While granularity is important, overly small tasks can cause unnecessary overhead.
• Revisit and Revise: Planning is iterative. Update your plan as new information arises.
• Documentation Is Key: A well-documented plan is vital for onboarding, handoffs, and future maintenance.

By mastering Planning and Task Breakdown, you ensure that every project starts with a solid foundation, reducing ambiguity, increasing transparency, and setting the stage for consistent, high-quality implementation.