pathfinder

To map an unfamiliar codebase for refactoring, you need to inventory features based on source-tree evidence and entry points. This process generates structured feature lists with clear boundaries and per-feature Mermaid flowcharts detailing primary happy paths.

Detecting duplicated concerns across systems requires a subagent-based discovery approach with mandatory source citations. This method produces a cross-feature duplication report identifying overlapping logic with specific file and line evidence.

Generating Mermaid flowcharts for architecture audits involves mapping each feature's primary happy path and key branches. The resulting diagrams include specific file:line node labels, providing visual evidence of codebase structure and flow.

Yes, you can plan a unified architecture across multiple systems. After detecting duplicated concerns, the process proposes the simplest unified architecture supported by evidence, fitting architecture audits and refactor preparation tasks.

To hand off a refactoring plan, you generate copy-paste /make-plan prompts. These handoff prompts are produced alongside the unified architecture proposal, ensuring downstream execution tools receive structured, evidence-based instructions.

You should avoid subagent-based codebase mapping when working with extremely small or simple codebases where manual inspection suffices. This approach is designed for sprawling, unfamiliar codebases requiring cross-feature duplication detection and unified architecture proposals.