reconnaissance
Reconnaissance: Intel and Environment Mapping
Overview
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.
Trigger
Invoked when the Don expresses building or creative intent.
Process
Step 1: Analyze Intent
The Underboss parses the Don's request to identify:
- Objective: What is being built or changed?
- Scope: Which parts of the system are affected?
- Constraints: Any explicit requirements or limitations?
More from kucherenko/gangsta
drill-tdd
Use when implementing any feature or bugfix — enforces the Red-Green-Refactor drill with no production code allowed without a failing test first
6the-capo
Use when orchestrating workers within a specific domain territory — managing work package dispatch, reviewing reports against the contract, and reporting status to the underboss
5the-hit
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
5omerta
Use when enforcing governance guardrails during any gangsta operation — referenced as cross-cutting concern by all skills for anti-hallucination, authorization, state durability, resource management, and spec supremacy rules
5the-consigliere
Use when needing impartial architectural advice, security audit, spec integrity review, or a second opinion — operates outside the chain of command with standing authority to invoke truth checks
5audit-review
Use when completing tasks, implementing major features, or before merging — dispatches the-inspector to audit the books before the job is closed
5