task-breakdown

Break down large backlog items by identifying split axes like user flow or API contract, then drafting candidate subtasks with explicit scope, dependencies, and completion criteria. Each session task receives a clear verification path mapped to smoke, unit, or integration gates.

Scoping ambiguous coding tasks requires converting them into bounded session-sized chunks with explicit verification mappings. You apply structured decomposition to define priority and dependencies, producing artifacts compatible with repository verification commands for predictable handoff.

Verification-first task scoping requires a clear verification path for each decomposed task before execution. It maps backlog items to smoke, unit, integration, E2E, or full verification gates, ensuring every session-sized task has explicit completion criteria and test boundaries.

You do not need an external planner to decompose coupled features. The skill acts as a planner-led decomposition tool, analyzing state boundaries and verification boundaries to generate structured task artifacts with IDs, priorities, and dependency mappings.

You can use it to recover from overscoped coding sessions by splitting oversized work into prioritized, bounded tasks. It updates current-task artifacts and recommends the first selectable task for execution to safely resume implementation.

Splitting work along API contract boundaries depends on identifying clear state and verification boundaries. If the tightly coupled backlog items lack distinct split axes or clear verification paths, generating bounded session-sized tasks with explicit scope becomes difficult.