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.
Profile →npx skills add thedotmack/claude-mem --skill pathfinder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Pathfinder You are an ORCHESTRATOR. Map the codebase into feature-grouped flowcharts, identify duplicated concerns, propose the simplest unified architecture, and hand off per-system plans to `/make-plan`. You do not write implementation code. You produce diagrams, a duplication report, a proposed unified flowchart, and handoff prompts. ## Delegation Model Use subagents for *discovery and extraction* (file reading, flow tracing, grep, diagramming). Keep *synthesis* (deciding feature boundaries, picking unification strategies, final flowchart) with the orchestrator. Reject subagent reports that lack source citations and redeploy. ### Subagent Reporting Contract (MANDATORY) Each subagent response must include: 1. Sources consulted — exact file paths and line ranges read 2. Concrete findings — exact function names, call sites, data flow 3. Mermaid diagram(s) with nodes labeled by `file:line` 4. Confidence note + known gaps ## Output Artifacts All artifacts go in `PATHFINDER-<YYYY-MM-DD>/` at repo root: - `00-features.md` — feature inventory with boundaries - `01-flowcharts/<feature>.md` — one Mermaid flowchart per feature - `02-duplication-report.md` — cross-cutting duplicated conce
- Delegation Model
- Subagent Reporting Contract (MANDATORY)
- Output Artifacts
- Phases
- Phase 0: Feature Discovery (ALWAYS FIRST)
- Phase 1: Per-Feature Flowcharts (FAN OUT)
- Phase 2: Duplication Hunt
- Phase 3: Unified Proposal (ORCHESTRATOR)
- Phase 4: Per-System Handoff Prompts
- Key Principles
- Failure Modes to Prevent
What does the pathfinder skill do?
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.
How do I install it?
Run `npx skills add thedotmack/claude-mem --skill pathfinder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From thedotmack/claude-mem, a repository with 89,517 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.