investigar-area

To investigate a codebase area, you provide a project map path and a scoped task. The skill analyzes the targeted subsystem, reads local instructions, and outputs a structured report with evidence, boundaries, and risks.

The best way to analyze a subsystem without implementing changes is to use a scoped investigation task. This approach reads project maps and local instructions to deepen understanding of the code area while avoiding feature work or bug fixes.

An area investigation report uses AGENTS.md and local instructions to ground the analysis. By reading these relevant files, the investigation captures accurate evidence and boundaries for the targeted codebase area.

Yes, you need a general project map to perform a scoped subsystem investigation. Providing the project map path allows the skill to rebuild context and execute the deep area analysis required for the final report.

Yes, you can use this approach to analyze a code area for risks and boundaries. The investigation process generates a structured area report that captures evidence and defines the limits of the scoped subsystem.

You should not use a scoped area investigation when you need project-wide mapping, feature implementation, or bug fixes. This process is designed specifically for analyzing a code area without implementing changes.