From gangsta
Drafts binding project specification after grilling consensus approval. Prohibits code generation; synthesizes inputs, proposes 2-3 approaches, reviews for clarity, and finalizes spec governing implementation.
npx claudepluginhub kucherenko/gangsta --plugin gangstaThis skill uses the workspace's default tool permissions.
The Sit-Down is where the Don, Consigliere, and Underboss finalize the Contract — the binding specification for the Heist. This is a "Plan-First" phase where code generation is STRICTLY PROHIBITED.
Explores intent, requirements, and design for features, phases, or initiatives before coding. Produces HOTL contracts (intent, verification, governance) and design docs for approval.
Runs multi-agent adversarial debate for brainstorming architectural solutions post-reconnaissance: proposer suggests plan, devil's advocate critiques, synthesizer integrates don feedback; strict round limits.
Transforms raw brain dumps, messy ideas, and stream-of-consciousness dictation into structured contracts, PRDs, and implementation specs saved to ./docs/ideation/{project-name}/. Use for feature planning and spec generation.
Share bugs, ideas, or general feedback.
The Sit-Down is where the Don, Consigliere, and Underboss finalize the Contract — the binding specification for the Heist. This is a "Plan-First" phase where code generation is STRICTLY PROHIBITED.
Invoked after the Don approves the Grilling consensus (The Grilling complete).
NO CODE GENERATION DURING THE SIT-DOWN.
Not pseudocode. Not "example snippets." Not "draft implementations." NOTHING that looks like code. If you catch yourself writing code, STOP. You are violating Omerta Law 5.
The Contract describes WHAT and WHY. Implementation details (HOW) belong in the Work Packages created during Resource Development.
digraph sit_down {
"Synthesize inputs\n(Dossier + Grilling + Constitution)" [shape=box];
"Propose 2-3 approaches" [shape=box];
"Don approves approach?" [shape=diamond];
"Draft the Contract" [shape=box];
"Consigliere review\n(contradiction, ambiguity, completeness)" [shape=box];
"Consigliere verdict?" [shape=diamond];
"Don signs Contract?" [shape=diamond];
"Invoke gangsta:resource-development" [shape=doublecircle];
"Synthesize inputs\n(Dossier + Grilling + Constitution)" -> "Propose 2-3 approaches";
"Propose 2-3 approaches" -> "Don approves approach?";
"Don approves approach?" -> "Propose 2-3 approaches" [label="revise"];
"Don approves approach?" -> "Draft the Contract" [label="approved"];
"Draft the Contract" -> "Consigliere review\n(contradiction, ambiguity, completeness)";
"Consigliere review\n(contradiction, ambiguity, completeness)" -> "Consigliere verdict?";
"Consigliere verdict?" -> "Draft the Contract" [label="REJECT"];
"Consigliere verdict?" -> "Don signs Contract?" [label="APPROVE"];
"Don signs Contract?" -> "Draft the Contract" [label="changes requested"];
"Don signs Contract?" -> "Invoke gangsta:resource-development" [label="signed"];
}
Gather and internalize all available intelligence:
Before writing any spec, the Underboss must present the Don with 2-3 distinct viable approaches to the problem. Each approach must cover:
### Approach A: <Name>
<One-sentence description>
**Pros:** <key advantages>
**Cons:** <key trade-offs>
**Risk:** HIGH / MEDIUM / LOW
**Best when:** <conditions that favour this approach>
Rules:
Autonomous Mode: Do NOT ask the human Don for approach selection. Invoke gangsta:don-proxy to select the approach. Proceed to Step 3 with don-proxy's selection without waiting for human input. On REJECT (don-proxy finds no approach above the Constitutional Floor): abort.
Otherwise (default Heist): Present all approaches then ask: "Which approach do you want to proceed with, or would you like adjustments?"
Wait for the Don's explicit selection before writing anything.
Using the approved approach as the architectural foundation, draft the formal specification.
The Contract must include:
---
heist: <heist-name>
date: YYYY-MM-DD
status: draft
signatories: []
---
# Contract: <Heist Name>
## Objective
<What is being built, in one paragraph>
## Requirements
### Functional Requirements
1. <FR-001> <Requirement>
2. <FR-002> <Requirement>
...
### Non-Functional Requirements
1. <NFR-001> <Requirement (performance, security, accessibility, etc.)>
...
## Architectural Decisions
<Key decisions from the Grilling consensus, with rationale>
## Grilling Conclusions
### Key Decisions
- <Decision>: <rationale>
### Rejected Alternatives
- <Alternative>: <why rejected>
### Unresolved Objections
- <Objection> — Risk: HIGH/MEDIUM/LOW — Mitigation: <if any>
## Applicable Constitution Rules
### Commandments
- <Commandment text> — Source: insights/<file>
### Negative Constraints
- NEVER <constraint> — Source: fails/<file>
## Acceptance Criteria
<How do we know the Heist is complete? Specific, testable criteria.>
## Out of Scope
<What this Heist explicitly does NOT cover>
## Open Risks
<From the Grilling — any unresolved objections with assessed risk>
Invoke gangsta:the-consigliere for spec integrity review:
The Consigliere returns a verdict: APPROVE, APPROVE WITH CONCERNS, or REJECT.
If REJECTED: Underboss revises based on Consigliere feedback. Re-review.
Autonomous Mode: When invoked under gangsta:autonomous-mode, see § Per-Phase Interaction Schemas → the-Sit-Down in that skill. Otherwise this skill operates as written.
Autonomous Mode: Do NOT present the Contract to the human Don for approval. Invoke gangsta:don-proxy to review and sign. The Dual-Veto applies: both Consigliere (Step 4) and don-proxy must return non-REJECT. Either REJECT is terminal — there is no tie-break and no re-vote. On dual non-REJECT: sign the Contract and auto-advance to Resource Development. Do not pause for human input.
Otherwise (default Heist): Present the Contract to the Don:
"The Contract for Heist '' is ready for your review. The Consigliere's verdict: [verdict]. [If concerns, list them.] Do you approve?"
The Don may:
gangsta:resource-development — do NOT ask the Don what to do next, do NOT pause, do NOT prompt for confirmation. Auto-advance is mandatory.Autonomous Mode auto-advance: Under gangsta:autonomous-mode, this auto-advance fires when don-proxy SIGNS and Consigliere returns non-REJECT. Either REJECT is terminal (Dual-Veto).
Update the Contract frontmatter:
status: signed
signatories: [Don, Consigliere, Underboss]
Save to: docs/gangsta/<heist-name>/specs/YYYY-MM-DD-contract.md
---
heist: <heist-name>
phase: the-sit-down
status: completed
timestamp: <ISO 8601>
next-action: Proceed to Resource Development
artifacts:
- docs/gangsta/<heist-name>/specs/YYYY-MM-DD-contract.md
---