pathfinder
Map a codebase into feature-grouped flowcharts, identify duplicated concerns across features, and propose a unified architecture. Use when asked to "find the ideal path," unify duplicated systems, or audit architecture before a refactor. Emits a proposed unified flowchart plus per-system /make-plan prompts.
Security Assessment
About pathfinder
Pathfinder is an orchestrator skill for auditing a codebase's architecture before a refactor. It maps the code into feature-grouped flowcharts, identifies concerns that are duplicated across features, and proposes the simplest unified architecture, without writing implementation code itself.
It runs a phased workflow: feature discovery (establishing boundaries first), per-feature Mermaid flowcharts with nodes labeled by file:line, a duplication hunt (both within-feature and cross-feature), an orchestrator-authored unified proposal, and copy-pasteable /make-plan handoff prompts per unified system. Discovery and extraction (reading files, tracing flow, diagramming) are delegated to subagents under a strict reporting contract requiring cited sources, concrete findings, Mermaid diagrams, and confidence notes, while synthesis decisions stay with the orchestrator. All artifacts are written to a dated PATHFINDER-<date>/ directory.
It is most useful for engineers who want to unify duplicated systems or understand a codebase's ideal path before a large refactor, emphasizing evidence over intuition and preferring deletion and simplification over new abstraction layers.
FAQ
What does Pathfinder produce?
A feature inventory, one Mermaid flowchart per feature, a cross-cutting duplication report, a proposed unified architecture diagram, and per-system /make-plan handoff prompts, all under a dated PATHFINDER-<date>/ folder.
Does it write code?
No. It is an orchestrator that produces diagrams, reports, and handoff prompts; implementation is handed off to /make-plan and /do.
How does it use subagents?
Subagents handle discovery and extraction under a mandatory reporting contract, while the orchestrator keeps synthesis decisions like feature boundaries and unification strategy.
How does it ensure accuracy?
Every diagram node and duplication claim must cite file:line evidence; reports lacking citations are rejected and the subagent is redeployed.
What unification philosophy does it follow?
Simplest unification wins, preferring deletion over abstraction and one path over configurable paths, while treating legitimate specialization as not duplication.
Install pathfinder
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
thedotmack/claude-mem