breakdown-taskslisted

# Task Breakdown — Orchestrator *Productivity — multi-agent orchestration. Break architecture into executable tasks; consumers implement one at a time.* **Core Question:** "Can an engineer pick up any single task and ship it independently?" > Methodology (risk-first, vertical slices, stable IDs, multi-agent rationale), principles, when NOT to use: [`references/playbook.md`](references/playbook.md) [PLAYBOOK]. **Capabilities surfaced:** decompose, task-breakdown, sprint-plan, work-breakdown, acceptance criteria, task dependencies, implementation order, risk-first ordering. ## Critical Gates Critic-agent verifies ALL before delivery: - [ ] Every task has exactly ONE acceptance test - [ ] No task depends on something not yet defined - [ ] Risky/uncertain work is front-loaded - [ ] All external config is in Prerequisites, not buried in tasks - [ ] A junior dev could verify each acceptance criterion - [ ] No task requires unstated knowledge - [ ] Tasks are vertical slices (each delivers a testable increment through all layers); horizontal-only needs explicit justification **On fail:** critic names the agent; orchestrator re-dispatches with feedback. Max 2 rounds; round >2 → DONE_WITH_CONCERNS. ## Before Starting Apply [`references/_shared/before-starting-check.md`](references/_shared/before-starting-check.md) [PLAYBOOK]: | # | Action | |---|---| | 0 | Mode resolve per [`references/_shared/mode-resolver.md`](references/_shared/mode-resolver.md). Default `standard`. Downg