From gangsta
Dispatches crew leads and workers for parallel execution of approved coding work packages with TDD enforcement, report collection, reviews, and escalations.
npx claudepluginhub kucherenko/gangsta --plugin gangstaThis skill uses the workspace's default tool permissions.
Workers and Crew Leads implement the Work Packages defined in the Execution Plan. Crews work simultaneously on their assigned territories, providing Reports (status updates) to 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 parallel implementation of 3+ independent tasks with coder-overseer pairs, reviewing bugs, gaps, errors, and cohesion against shared contracts.
Orchestrates 4-phase execution loop (IMPLEMENT, VALIDATE, ADVERSARIAL REVIEW, COMMIT) for complex work units with specs. Verifies outputs adversarially in multi-agent setups.
Share bugs, ideas, or general feedback.
Workers and Crew Leads implement the Work Packages defined in the Execution Plan. Crews work simultaneously on their assigned territories, providing Reports (status updates) to the Underboss.
Invoked after the Don approves the Execution Plan (Resource Development complete).
For each territory, the Underboss sends the Crew Lead:
Each Crew Lead (invoke gangsta:the-capo) processes their Work Packages:
For each independent Work Package, dispatch a Worker subagent with subagent_type: "soldier" (do NOT use "general" or "general-purpose" — these are not valid in a Gangsta Agents installation), providing:
Workers work in parallel within their territory (up to the allocated Worker count)
Every Worker MUST follow gangsta:drill-tdd — the full Red-Green-Refactor cycle:
A Worker that writes implementation before tests has its Report REJECTED.
Each Worker returns a Report:
## Report: <WP-ID>
**Status:** success | failure | blocked
**TDD Cycle:**
- Test written: YES/NO
- Test failed first: YES/NO
- Implementation written: YES/NO
- Test passes: YES/NO
**Changes:**
- <file path>: <created/modified>
**Test Output:**
```
**Notes:**
```
The Crew Lead reviews each Report (invoke gangsta:the-capo):
Accept, reject with feedback, or escalate.
Crew Leads report territory status to the Underboss. The Underboss synthesizes for the Don:
## Heist Progress: <Heist Name>
| Territory | Completed | In Progress | Failed | Budget Used |
|-----------|-----------|-------------|--------|-------------|
| Frontend | 3/5 | 1 | 1 | 60% |
| Backend | 4/4 | 0 | 0 | 45% |
| ... | | | | |
**Overall:** <N>/<Total> Work Packages complete
When a Worker fails:
Autonomous Mode: When invoked under gangsta:autonomous-mode, see § Per-Phase Interaction Schemas → the-Hit in that skill. Under autonomous mode, the mini-Grilling escalation produces a deviation report only and cannot mutate the signed Contract. Otherwise this skill operates as written.
When all Crew Leads report territory completion:
gangsta:laundering — do NOT ask the Don what to do next, do NOT pause, do NOT prompt for confirmation. Auto-advance is mandatory.Write checkpoint after each significant batch of Work Packages completes (not just at the end):
---
heist: <heist-name>
phase: the-hit
status: in-progress | completed
timestamp: <ISO 8601>
next-action: <Continue Hit | Proceed to Laundering (auto)>
completed-wps: [WP-001, WP-002, ...]
pending-wps: [WP-003, ...]
failed-wps: [WP-004, ...]
artifacts:
- <list of modified/created files>
---