From gangsta
Orchestrates domain-specific workers in codebase territories: dispatches work packages to subagents, reviews reports against contracts, accepts/rejects changes, escalates issues, reports status.
npx claudepluginhub kucherenko/gangsta --plugin gangstaThis skill uses the workspace's default tool permissions.
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.
Decomposes coding tasks into verifiable work packages, allocates to crew leads by file territories, manages phase progression, token budgets, and escalations in agentic workflows.
Orchestrates multi-agent parallel execution for complex tasks like features, refactoring, testing, reviews, and documentation using cc-mirror tracking and TodoWrite visibility.
Share bugs, ideas, or general feedback.
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.
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>
The Crew Lead operates ONLY within its territory. Files outside the territory belong to another Crew Lead.
For each Work Package assigned to this territory:
Prepare Worker Brief — Extract from the Work Package:
Dispatch Worker — Launch a subagent with subagent_type: "soldier" (do NOT use "general" or "general-purpose" — these are not valid in a Gangsta Agents installation) and the Worker brief. Multiple Workers can run in parallel on independent Work Packages.
Receive Report — Each Worker returns:
## Report: <WP-ID>
**Status:** success | failure | blocked
**Changes:** <List of files created/modified>
**Tests:** <Test results — pass/fail with output>
**Notes:** <Any issues encountered>
Review Report — Verify against the Contract:
Accept or Reject:
Report to the Underboss after each Work Package completes or fails:
## Territory Status: <Name>
**Completed:** <N> of <Total> Work Packages
**In Progress:** <N>
**Failed/Blocked:** <N>
**Token Usage:** <Used> of <Budget>
### Details
- WP-001: ✅ Complete
- WP-002: ✅ Complete
- WP-003: 🔄 In progress (Worker dispatched)
- WP-004: ❌ Failed — escalated to Underboss