// Use when beginning a new heist — deploys associates to survey the target codebase, existing tests, dependencies, documentation, and the ledger to produce a reconnaissance dossier for the don's review
Use when receiving code review feedback — processes orders with technical rigor, not blind obedience or performative agreement
Use when starting feature work that needs isolation from the current workspace — sets up a secure safehouse with git worktrees for clean operational bases
Use when the execution plan is approved and it is time for parallel execution — dispatches workers through crew leads to implement work packages with TDD enforcement, report collection, and escalation protocols
Use when starting any conversation — establishes how to find and use Gangsta skills, enforces the 1% invocation rule, maps platform tools, and routes the Don's intent through the Gangsta Agents Family hierarchy
Use when all territories report completion after the hit — handles integration, verification, consigliere final review, cleanup, and ledger updates to produce clean production-ready code
Use when the contract is signed and work packages need to be created — decomposes the contract into bite-sized tasks, sets up git isolation, allocates territories and token budgets, producing the execution plan
| name | reconnaissance |
| description | Use when beginning a new heist — deploys associates to survey the target codebase, existing tests, dependencies, documentation, and the ledger to produce a reconnaissance dossier for the don's review |
Every Heist begins with gathering intel. The Underboss deploys Associates to perform a detailed survey of the target codebase and infrastructure. The output is a Reconnaissance Dossier that informs all subsequent phases.
Invoked when the Don expresses building or creative intent.
The Underboss parses the Don's request to identify:
Dispatch Associate subagents in parallel to gather intel.
Subagent type: Use subagent_type: "associate" for all Associate dispatches. Do NOT use "general" or "general-purpose" — these are not valid in a Gangsta installation.
| Associate Task | What to Survey |
|---|---|
| Codebase Structure | File tree, key directories, framework detection, entry points |
| Existing Tests | Test files, coverage areas, test framework, passing/failing status |
| Dependencies | package.json / requirements.txt / go.mod etc., versions, known issues |
| Documentation | README, existing specs, API docs, inline documentation |
| Ledger Search | Search docs/gangsta/insights/ and docs/gangsta/fails/ for entries with tags matching the objective |
| Constitution | Read docs/gangsta/constitution.md for applicable Commandments and Negative Constraints |
Compile Associate reports into a structured Reconnaissance Dossier.
Save to: docs/gangsta/<heist-name>/recon/YYYY-MM-DD-recon-dossier.md
---
heist: <heist-name>
date: YYYY-MM-DD
status: pending-review
---
# Reconnaissance Dossier: <Heist Name>
## Objective
<What the Don wants to build/change>
## Codebase Overview
<Key files, directories, frameworks, patterns discovered>
## Existing Test Coverage
<What's tested, what's not, test framework and run command>
## Dependencies
<Key dependencies, versions, any concerns>
## Relevant Ledger Entries
### Applicable Insights
- <insight reference + summary>
### Applicable Negative Constraints
- NEVER <constraint> — Source: fails/YYYY-MM-DD-<topic>.md
## Risks and Unknowns
<Anything that couldn't be determined, areas of concern>
## Recommended Scope
<Suggested boundaries for the Heist based on the intel>
Autonomous Mode: Do NOT present the proceed menu below and do NOT wait for human input. Invoke gangsta:don-proxy to review the Dossier. On APPROVE: auto-advance directly to the-Grilling (The Grilling is mandatory in autonomous mode — there is no skip-Grilling path). On REJECT: abort; write the verdict to autonomous-log.md and leave the heist directory in place. The proceed menu is for the default (gated) Heist only.
Otherwise (default Heist):
Save the Dossier file (Step 3), then present its contents to the Don in chat.
DO NOT include the proceed menu in the dossier file. The menu is a chat message only — output it as plain text after presenting the dossier summary.
Required gate — The Sit-Down must not be skipped:
The Sit-Down (spec drafting and Contract signing) is a required phase. The Don may only choose whether The Grilling runs before it — but The Sit-Down itself must always run.
If the Don requests to skip The Sit-Down, explain that the Contract is required before any implementation work begins and re-present the menu below.
The proceed menu MUST use exactly this format — do not paraphrase, abbreviate, or add options:
How do you want to proceed?
1. Approve the dossier + run The Grilling → Multi-agent debate on architecture, then The Sit-Down
2. Approve the dossier + skip The Grilling → Proceed directly to The Sit-Down (spec drafting)
3. Adjust scope — Add/remove anything from the phases before we commit
4. Request more intel — Deploy Associates to dig deeper into a specific area
Wait for the Don's explicit choice before taking any action.
gangsta:the-grilling, then gangsta:the-sit-downgangsta:the-sit-downProceed with one of the choices above to maintain spec integrity (Omerta Law 5).
Write checkpoint after the Don approves (choices 1 or 2):
---
heist: <heist-name>
phase: reconnaissance
status: completed
timestamp: <ISO 8601>
next-action: <"Proceed to The Sit-Down" | "Proceed to The Grilling">
artifacts:
- docs/gangsta/<heist-name>/recon/YYYY-MM-DD-recon-dossier.md
---