ferrox-map-codebase

To analyze an unfamiliar codebase for onboarding, you can use parallel agents to map repository intelligence across technical, architectural, quality, and risk scenarios. This generates structured documentation directly on disk for consistent project intelligence.

The best way to map codebase architecture before a refactor is by spawning focused parallel agents to assess technology, architecture, quality, and concerns. This approach produces seven standard documents under a dedicated directory for pre-refactor investigation.

Parallel codebase analysis works by spawning focused agents that target specific areas like technology, architecture, and quality. This prevents loading everything into context at once and produces a structured repository intelligence map directly on disk.

Mapping a repository generates seven standard documents under the `.planning/codebase/` directory. These structured outputs provide consistent project intelligence covering technical, architectural, quality, and risk scenarios.

Yes, you can refresh codebase documentation after major changes by running the analysis again. It supports post-change refreshes by regenerating the structured repository intelligence map to reflect the current state of the codebase.

No, you do not need to load the entire codebase into context to map it. The skill coordinates parallel mapper agents that analyze the codebase and produce a structured map directly on disk without loading everything at once.