- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add thedotmack/claude-mem --skill pathfinder -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add thedotmack/claude-mem --skill pathfinder -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add thedotmack/claude-mem --skill pathfinder -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add thedotmack/claude-mem --skill pathfinder -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/thedotmack/claude-mem/tree/HEAD/plugin/skills/pathfinderDe l'éditeur
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.
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.
Each subagent response must include:
file:lineAll artifacts go in PATHFINDER-<YYYY-MM-DD>/ at repo root:
00-features.md — feature inventory with boundaries01-flowcharts/<feature>.md — one Mermaid flowchart per feature02-duplication-report.md — cross-cutting duplicated concerns with evidence03-unified-proposal.md — proposed unified architecture + Mermaid04-handoff-prompts.md — copy-pasteable /make-plan prompts per unified systemDeploy ONE "Feature Discovery" subagent to:
Orchestrator reviews the proposal, adjusts boundaries if needed, writes 00-features.md. Do NOT fan out until feature boundaries are approved.
Deploy ONE "Flowchart" subagent per feature in parallel. Each receives only its feature's scope. Each must:
flowchart TD with every node labeled Name<br/>file:lineOrchestrator writes each flowchart to 01-flowcharts/<feature>.md. Reject any diagram missing file:line labels.
Deploy TWO subagents in parallel:
"Within-Feature Duplication" subagent:
"Cross-Feature Duplication" subagent:
file:line, (c) why they diverged, (d) whether the divergence is legitimate specialization or accidentalOrchestrator synthesizes both into 02-duplication-report.md. Every duplication claim must cite ≥2 file:line locations.
The orchestrator writes 03-unified-proposal.md itself — do not delegate synthesis.
For each duplicated concern from Phase 2 that is NOT legitimate specialization:
End the document with ONE combined Mermaid flowchart showing the proposed unified system. Nodes still labeled with target file:line (new or existing) where knowable.
Anti-patterns to reject in your own proposal:
For each unified system in the proposal, write a ready-to-run /make-plan prompt to 04-handoff-prompts.md. Each prompt must:
01-flowcharts/Format each as a fenced code block the user can copy directly into /make-plan.
file:line/make-plan and /do take it from thereMap 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
---name: pathfinderdescription: Map a codebase into feature-grouped flowcharts, identify duplicated concerns across features, and propose a…---# plugin/skills/pathfinder/SKILL.mdVue d'ensemble
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.
FAQ
Téléchargez plugin/skills/pathfinder/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/thedotmack/claude-mem.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.