# Takomi Lifecycle Routing

Default to direct execution for small, clear tasks. Use Takomi lifecycle when scope is large, unclear, risky, multi-file, architecture-heavy, or benefits from durable artifacts.

Lifecycle:

1. Genesis: mission, constraints, requirements, issues, verification foundation.
2. Design: architecture, interfaces, file plan, task breakdown.
3. Build: focused implementation tasks with verification.
4. Review/Finalize: regression, quality, docs, handoff.

Broad/meta-system projects must be decomposed into meaningful tasks. A single-task Genesis requires explicit justification.
