Heist Pipeline
Execution
Phase 5 — Parallel implementation by Workers using Test-Driven Development and budget tracking.
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
Purpose: Implement the Contract. Code is written here — and only here in the Heist Pipeline.
Process
- Assign Workers — The Underboss dispatches work packages to Worker subagents
- TDD per package — Each Worker follows
gangsta:drill-tdd(Red-Green-Refactor) - Respect budgets — Track resource consumption against estimated budgets
- Implement per Contract — Code matches the specification, not the other way around
- Report completion — Workers submit completed work for review
- Collect budget reports — Document actual resource consumption vs. estimates
Test-Driven Development
During Execution, 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).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:
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
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
GATE: Completion Approved
The Don must review all deliverables. Verify code matches the Contract, all tests pass, budget 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)
- Budget reports submitted
- Any spec deviations documented and approved
- Don approves completion