planning-and-task-breakdown

Task breakdown decomposes large specifications into small, verifiable units with explicit acceptance criteria. It maps dependencies and creates vertical slices, enabling incremental delivery and proactive risk management through structured checkpoints and risk notes.

To break down a large feature spec, outline the feature and generate a phased task list using a standardized template. This enforces explicit acceptance criteria, verification steps, dependency mapping, and checkpoints to guide safe, incremental delivery of working increments.

The best way to create vertical slices for parallel work is to convert features into small, end-to-end task units that deliver working increments. This involves explicit dependency analysis to identify parallel opportunities and map relationships before implementation begins.

Yes, you can use plan mode for read-only analysis to understand patterns, dependencies, and risks before coding. This approach clarifies scope and enforces a plan document template with task sizing and risk notes to guide safe, incremental delivery.

Vertical slicing for project planning may not suit projects where scope is already fully clarified and dependencies do not exist. If work cannot be structured into small, end-to-end task units delivering working increments, this planning process adds unnecessary overhead.