the-capo
The Capo: Territory Commander (Crew Lead)
Overview
A Crew Lead is a domain-specific orchestrator that leads a crew of Workers. Each Crew Lead owns a "territory" — a bounded area of the codebase (e.g., frontend components, API layer, database, infrastructure). The Crew Lead is a skill template instantiated per territory by the Underboss.
Territory Context
When the Underboss instantiates a Crew Lead, it provides territory context:
## Territory: <Name>
**Domain:** <What this territory covers>
**Files:** <Glob patterns>
**Conventions:** <From Constitution>
**Workers:** <Parallel count>
**Budget:** <Token allocation>
More from kucherenko/gangsta
drill-tdd
Use when implementing any feature or bugfix — enforces the Red-Green-Refactor drill with no production code allowed without a failing test first
6the-hit
Use when the execution plan is approved and it is time for parallel execution — dispatches workers through crew leads to implement work packages with TDD enforcement, report collection, and escalation protocols
5omerta
Use when enforcing governance guardrails during any gangsta operation — referenced as cross-cutting concern by all skills for anti-hallucination, authorization, state durability, resource management, and spec supremacy rules
5reconnaissance
Use when beginning a new heist — deploys associates to survey the target codebase, existing tests, dependencies, documentation, and the ledger to produce a reconnaissance dossier for the don's review
5the-consigliere
Use when needing impartial architectural advice, security audit, spec integrity review, or a second opinion — operates outside the chain of command with standing authority to invoke truth checks
5audit-review
Use when completing tasks, implementing major features, or before merging — dispatches the-inspector to audit the books before the job is closed
5