Heist Pipeline
The Sit-Down
Phase 3 — Draft the formal specification (Contract). No code allowed.
The Sit-Down
Phase 3 of the Heist Pipeline
Draft the formal specification — the Contract. This is the most critical phase. No code is allowed. If any code appears during The Sit-Down, the phase must restart.
Skill: gangsta:the-sit-downSkill type: Rigid — the "no code" rule is non-negotiable
No code allowed during The Sit-Down. This phase produces a specification, not an implementation. If code appears, restart the phase.
Process
- Review the Dossier — Ground the spec in verified intel from Reconnaissance
- Incorporate Grilling Conclusions — Include the design decisions from The Grilling
- Draft the Contract — Write the formal specification document
- Review for completeness — Ensure scope, out-of-scope, acceptance criteria, and rules are all present
- Present for signature — The Don reviews and signs the Contract
Output: The Contract
The Contract is the authoritative source of truth for the entire Heist. It includes:
- Objective — What's being built and why
- Requirements — Functional and non-functional requirements
- Architectural Decisions — Key design choices and their rationale
- Grilling Conclusions — Debated decisions and rejected alternatives
- Applicable Constitution Rules — Project-specific rules that apply
- Acceptance Criteria — How success is verified
- Out of Scope — What's explicitly not being built
- Open Risks — Known risks with severity and mitigation
Phase Gate
GATE: Contract Signed
The Don must review and sign the Contract before proceeding. Verify every requirement is testable, scope matches expectations, out-of-scope items are listed, and acceptance criteria are clear. Only sign when confident the Contract is complete and correct.
Contract File
The Sit-Down produces the Contract at:
docs/gangsta/{heist-name}/specs/{date}-contract.md
This file is referenced during The Hit when verifying that implementation matches specification.
Spec is Law
The Contract is governed by Omerta Law #5:
If code contradicts the Contract, revise the Contract — not the code.The spec is the source of truth. During The Hit, if implementation reveals a spec issue:
- Stop implementation
- Propose a Contract revision
- Get Don approval for the revision
- Resume implementation
Checklist Before Proceeding
- Dossier findings incorporated
- Grilling Conclusions incorporated
- All requirements are testable
- Out-of-scope items explicitly listed
- Acceptance criteria are clear and measurable
- Open risks documented
- Contract reviewed and signed by Don