reconnaissance

To survey a codebase before starting, deploy associates to analyze the project structure, tests, dependencies, documentation, and ledger. This produces a reconnaissance dossier mapping environment constraints and risks for informed planning.

A codebase reconnaissance dossier is used to compile mapped constraints, risks, and actionable intel from the target project. It informs subsequent planning phases by providing a comprehensive review of code, tests, dependencies, docs, and governance ledger.

To map project dependencies and existing tests, dispatch associates to survey the target environment and compile findings. The process assesses tests and dependencies alongside documentation to produce a structured reconnaissance dossier for decision-making.

Yes, you can use subagents to analyze project documentation and ledger entries. The reconnaissance process requires dispatching associates to survey these specific areas, ensuring the final dossier accurately reflects governance records and project docs.

You should save a reconnaissance dossier to the path docs/gangsta/<heist-name>/recon/YYYY-MM-DD-recon-dossier.md. This standardized file location ensures the compiled codebase and ledger intel is accessible for subsequent planning phases.

Surveying a codebase without a governance ledger limits the reconnaissance dossier by omitting mapped constraints and governance records. A complete survey requires assessing the ledger alongside code, tests, dependencies, and documentation to inform planning accurately.