how-to-create-a-titanlisted

# How to Create a Titan A titan is the largest unit of autonomous work in the Claws class hierarchy — opus-only, multi-phase, 4-6 hour ceiling, with its own SKILL, PROMPT-BRAIN, canonical memories, blueprint folder, bus topic prefix, and a FILE-OWNERSHIP manifest that coordinates with sibling titans. See [[titan-hierarchy-legendary-class]] for the full class taxonomy. --- ## 1. When you need a titan (vs worker / lead) Use this decision table before reaching for `claws_titan` or `claws_worker(model='opus')`: | Signal | Tool | |---|---| | Single task, <30 min, one file | `claws_worker` (sonnet) | | 3-8 independent tasks, no cross-dep | `claws_fleet` (sonnet workers) | | Sequential phases with a LEAD coordinator | `claws_wave_create` + LEAD pattern | | Deep integration of an external system (CDP, Playwright, RTK…) | **titan** | | Second-round quality pass requiring multiple audit+fix cycles | **titan** | | Multi-titan release coordination with FILE-OWNERSHIP collisions | **titan** fleet (≤5 parallel) | | Mission expected to exceed 2 hours wall-clock | **titan** (opus only survives) | | Mission requires dispatching its own sub-worker army | **titan** | **Hard rule**: if sonnet would auto-compact mid-mission (>~150K tokens), you need a titan. Sonnet compaction drops context and silently degrades output quality. Opus has deeper reasoning and a wider effective window per [[context-ceiling]]. --- ## 2. Scoping a titan ### 4-6 hour ceiling Every titan declares a hard wall-cl