Execution

Phase 5 of the Heist Pipeline

Implementation. Workers implement the Execution Plan, writing code that fulfills the Contract. Each task follows Test-Driven Development within its budget.

Skill: gangsta:the-hitSkill type: Rigid — TDD discipline and budget tracking are non-negotiable

Process

1. Assign Workers — The Underboss dispatches work packages to Worker subagents
2. TDD per package — Each Worker follows gangsta:drill-tdd (Red-Green-Refactor)
3. Respect budgets — Track resource consumption against estimated budgets
4. Implement per Contract — Code matches the specification, not the other way around
5. Report completion — Workers submit completed work for review
6. Collect budget reports — Document actual resource consumption vs. estimates

Test-Driven Development

During Execution, all implementation follows the Red-Green-Refactor cycle:

1. Red — Write a failing test that defines the desired behavior
2. Green — Write the minimum code to make the test pass
3. Refactor — Improve the code while keeping all tests green

Budget Tracking

Each work package has a budget estimated during Resource Development. During Execution:

• Within budget — Task completed within estimate ✅
• Over budget — Task consumed more resources than estimated ⚠️
• Flagged — Over-budget tasks must report to the Don for review

Spec Deviations

If implementation reveals that the Contract is wrong:

This ensures every design change is intentional and tracked — not accidental drift.

Output

Execution produces:

• Implemented code — Fulfilling the Contract
• Test suite — Proving the implementation works
• Budget report — Actual vs. estimated resource consumption
• Spec deviations — Any Contract revisions that were needed

Phase Gate

Autonomous Mode

In Autonomous Mode (started via /gangsta:heist), The Hit executes after you sign the Contract with /gangsta:go. The key difference: the Don Proxy only intervenes at Worker-failure mini-Grilling. If a mini-Grilling occurs during Execution, it produces a deviation report only — the signed Contract remains byte-identical before and after. Contract amendment requires a fresh Sit-Down.

Execution auto-advances to Laundering when all Work Packages report complete. Full Autonomous Mode docs →

Checklist Before Proceeding

• All work packages implemented
• All tests passing (Red-Green-Refactor followed)
• Code matches Contract (no unauthorized spec deviations)
• Budget reports submitted
• Any spec deviations documented and approved
• Don approves completion

Previous: Resource Development ← | Next: The Delivery →