task-breakdown

Task decomposition transforms large requests into atomic subtasks under 30 minutes each with defined dependencies and execution order. The skill assesses complexity across scope, time, agents, dependencies, and documentation needs, then outputs a numeric score (0-20) and orchestration level (0-3) to guide your planning and delegation strategy.

Complexity assessment scores tasks across five dimensions: scope breadth, time estimate, agent requirements, dependencies, and documentation needs. This produces a 0-20 complexity score and corresponding orchestration level (0-3) with rationale, helping you determine whether to handle the work solo or escalate to multi-agent orchestration.

Dependency mapping identifies which subtasks must run sequentially versus in parallel by analyzing task relationships and prerequisites. The skill maps these dependencies explicitly so you can execute independent tasks concurrently and chain dependent tasks in the correct order for efficient project execution.

Yes. Task breakdown is designed for multi-domain, non-trivial requests spanning backend, frontend, infrastructure, or long-running workflows. It decomposes these complex cross-domain projects into isolated subtasks with clear ownership and execution sequencing.

Use task breakdown when facing vague, complex requests that risk analysis paralysis. Manual planning works for simple, single-domain tasks; automated decomposition prevents planning delays and ensures atomic, independently verifiable subtasks with mapped dependencies for projects with multiple domains or long execution timelines.