Task Breakdown Orchestrator FAQs

Question 1

How does this skill handle Task Sizing?

Accepted Answer

It validates that every task is sized between 0.5 and 1 day (4-8 hours). If a task is too large, it is split; if too small, it is grouped with related tasks to maintain a consistent development velocity.

Question 2

How is TDD enforced by this skill?

Accepted Answer

The skill generates a TDD triplet for every component: one task for writing the failing test (Red), one for implementation (Green), and one for code cleanup (Refactor).

Question 3

What is the primary goal of the Task Breakdown Phase skill?

Accepted Answer

The primary goal is to transform a high-level plan.md file into a structured tasks.md file containing 20-30 concrete, testable tasks that follow a Test-Driven Development sequence.

Question 4

Does it require specific input files?

Accepted Answer

Yes, it requires a completed planning phase output (plan.md) which defines the architecture, components, and reuse strategy before the breakdown can begin.

Question 5

What kind of output does it generate?

Accepted Answer

It produces a tasks.md file which includes the task list, complexity estimates, testable acceptance criteria, and a dependency map indicating the critical path.

Task Breakdown Orchestrator

Key Features

Use Cases

Task Breakdown Orchestrator

Key Features

Use Cases