planning-and-task-breakdown

To break down a large spec into implementation tasks, this Skill reads your requirements document in read-only mode, maps dependencies, and slices features vertically to produce ordered, verifiable task cards with acceptance criteria.

Vertical slicing in task planning is the practice of dividing features so each task delivers a working, testable slice of the system. This approach ensures every work item delivers end-to-end value rather than isolating architectural layers.

You map dependencies for parallel work by analyzing the requirements document and relevant code to build a dependency graph. This validates execution order and checkpoints so you can coordinate parallel agents without ambiguity.

Task cards for coordinating parallel agents should include numbered descriptions, acceptance criteria, verification steps, dependencies, affected files, and estimated scope to ensure clear handoffs between different engineers.

You need plan mode for spec decomposition when large requirements feel overwhelming or lack execution detail. It enforces reading the full spec and relevant code in read-only mode to uncover patterns, dependencies, and risks before touching any code.

This Skill applies when the agent has a clear requirements document and needs scoped, ordered work items. Without a clear spec, it cannot validate dependencies, acceptance criteria, and checkpoints to keep the plan actionable before coding begins.