From gangsta
Decomposes signed contracts into bite-sized verifiable work packages, sets up git isolation with branches and worktrees, defines territories, allocates token budgets, and produces execution plans.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gangsta:resource-developmentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The Underboss decomposes the signed Contract into Work Packages, sets up infrastructure for parallel execution, and produces the Execution Plan — the detailed task breakdown that governs The Hit.
The Underboss decomposes the signed Contract into Work Packages, sets up infrastructure for parallel execution, and produces the Execution Plan — the detailed task breakdown that governs The Hit.
Invoked after the Don signs the Contract (The Sit-Down complete).
For each requirement in the Contract:
Each Work Package must be:
Group Work Packages by domain and define Crew Lead territories:
## Territory: <Name>
**Domain:** <Description>
**Files:** <Glob patterns>
**Work Packages:** WP-001, WP-003, WP-007
**Workers:** <Parallel count>
**Budget:** <Token allocation>
If the project uses git:
heist/<heist-name>If not:
Before The Hit begins:
Compile everything into the Execution Plan.
Save to: docs/gangsta/<heist-name>/plans/YYYY-MM-DD-execution-plan.md
---
heist: <heist-name>
date: YYYY-MM-DD
total-work-packages: <N>
territories: <N>
estimated-total-budget: <tokens>
---
# Execution Plan: <Heist Name>
## Territories
### Territory: <Name 1>
**Crew Lead Domain:** <description>
**Files:** <globs>
**Workers:** <N parallel>
**Budget:** <tokens>
### Territory: <Name 2>
...
## Work Packages
**Prevention Guidance (all Work Packages):** Do NOT reproduce Gangsta-internal spec identifiers (FR-xxx, NFR-xxx, WP-xxx, where xxx is one or more digits) in any deliverable — source code, test files, code comments, or documentation. These identifiers belong only in `docs/gangsta/`.
### WP-001: <Title>
**Territory:** <Name>
**Contract Clause:** <FR-NNN>
**Files:**
- Create: `path/to/file`
- Test: `tests/path/to/test`
**Acceptance Criteria:**
1. <criterion>
**Verification:** `<command>`
**Budget:** <tokens>
**Dependencies:** None | WP-XXX
### WP-002: <Title>
...
## Execution Order
1. Independent packages (can run in parallel): WP-001, WP-002, WP-005
2. Depends on group 1: WP-003 (needs WP-001)
3. ...
## Baseline Verification
- Tests: <PASS/FAIL — must be PASS>
- Dependencies: <OK/MISSING>
- Branch: heist/<heist-name> created from <base>
Autonomous Mode: Do NOT ask the human Don. Invoke gangsta:don-proxy to review the Execution Plan for Constitutional-Floor violations (Work Package scope, territory allocation, budget assumptions). On APPROVE: /gangsta:heist writes docs/gangsta/.last-heist and exits — The Hit does NOT auto-start; the real Don must invoke /gangsta:go. On REJECT: abort; write the verdict to autonomous-log.md. Do not present the Plan to the human Don.
Otherwise (default Heist): Present to the Don:
"Execution Plan ready. Work Packages across territories. Estimated budget: . Ready to execute The Hit?"
---
heist: <heist-name>
phase: resource-development
status: completed
timestamp: <ISO 8601>
next-action: Proceed to The Hit
artifacts:
- docs/gangsta/<heist-name>/plans/YYYY-MM-DD-execution-plan.md
---
npx claudepluginhub kucherenko/gangsta --plugin gangstaDecomposes coding tasks into verifiable work packages, allocates to crew leads by file territory, manages heist phases, resources, escalations, and status rollups.
Orchestrates plan-driven builds by reading plan.json or requirements.md and dispatching workers. Use when executing /execute or running a blueprint plan.
Converts approved specs into executable implementation plans with task breakdowns, file maps, and verification steps. Use before multi-step coding work.