Heist Pipeline
The Hit
Phase 5 — Parallel execution by Soldiers using Test-Driven Development and tribute tracking.
The Hit
Phase 5 of the Heist Pipeline
Execution. Soldiers implement the War Plan, writing code that fulfills the Contract. Each task follows Test-Driven Development within its tribute budget.
Skill: gangsta:the-hitSkill type: Rigid — TDD discipline and tribute tracking are non-negotiable
Purpose: Implement the Contract. Code is written here — and only here in the Heist Pipeline.
Process
- Assign Soldiers — The Underboss dispatches work packages to Soldier subagents
- TDD per package — Each Soldier follows
gangsta:drill-tdd(Red-Green-Refactor) - Respect tributes — Track resource consumption against estimated budgets
- Implement per Contract — Code matches the specification, not the other way around
- Report completion — Soldiers submit completed work for review
- Collect tributes — Document actual resource consumption vs. estimates
Test-Driven Development
During The Hit, all implementation follows the Red-Green-Refactor cycle:
- Red — Write a failing test that defines the desired behavior
- Green — Write the minimum code to make the test pass
- Refactor — Improve the code while keeping all tests green
No code without a test. Every feature, every fix, every change starts with a test. This isn't a preference — it's the drill (
gangsta:drill-tdd).Tribute Tracking
Each work package has a tribute (budget) estimated during Resource Development. During The Hit:
- 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:
Don't just change the code.Omerta Law #5: Spec is Law. If the code contradicts the spec:
- Stop implementation
- Propose a Contract revision (with reasoning)
- Get Don approval for the revision
- Resume implementation under the revised spec
This ensures every design change is intentional and tracked — not accidental drift.
Output
The Hit produces:
- Implemented code — Fulfilling the Contract
- Test suite — Proving the implementation works
- Tribute report — Actual vs. estimated resource consumption
- Spec deviations — Any Contract revisions that were needed
Phase Gate
GATE: Completion Approved
The Don must review all deliverables. Verify code matches the Contract, all tests pass, tribute reports are reviewed for over-budget items, and any spec deviations are documented. Only approve when all tasks are complete and verified.
Checklist Before Proceeding
- All work packages implemented
- All tests passing (Red-Green-Refactor followed)
- Code matches Contract (no unauthorized spec deviations)
- Tribute reports submitted
- Any spec deviations documented and approved
- Don approves completion