pathfinder

Map a codebase into feature-grouped flowcharts with mermaid diagrams.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/chicago-joe/manymems --skill pathfinder-chicago-joe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pathfinder
Source: https://github.com/chicago-joe/manymems/tree/main/plugin/skills/pathfinder
Command: npx skills add https://github.com/chicago-joe/manymems --skill pathfinder-chicago-joe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map a codebase into feature-grouped flowcharts, identify duplicated concerns across features, and propose a unified architecture before refactors.

Core Features & Use Cases

  • Map the repository into feature boundaries and flowcharts to visualize architecture
  • Identify duplicated concerns across features and propose a unified approach
  • Emit a proposed unified flowchart plus per-system handoff prompts for implementation

Quick Start

Provide a unified flowchart and per-system handoff prompts for the repository.

Frequently Asked Questions about pathfinder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map a codebase into flowcharts to visualize architecture?▼

To map a codebase into flowcharts, this Skill groups repository features into mermaid diagrams labeled by file and line. It produces a features inventory and per-feature flowcharts to reveal architecture boundaries.

How do I identify duplicated concerns across features before refactoring?▼

Identify duplicated concerns across features using the generated duplication reports. The Skill audits cross-feature duplications and proposes a unified architecture flowchart to guide refactoring efforts.

Can I generate per-system handoff prompts for implementation from a codebase audit?▼

Yes, you can generate per-system handoff prompts from the codebase audit. The Skill emits these prompts alongside a proposed unified flowchart to direct implementation after identifying duplicated concerns.

What is the best way to audit architecture before a major codebase refactor?▼

The best way to audit architecture before a refactor is mapping feature boundaries into flowcharts. This process reveals structural duplication and produces a unified proposal plus handoff prompts for implementation.

Does the architecture flowchart mapping support mermaid diagrams with file and line labels?▼

Yes, the architecture flowchart mapping supports mermaid diagrams labeled by file and line. It visualizes feature boundaries and cross-feature flows to clarify the codebase structure during an audit.

When should I not use feature-grouped flowcharts for codebase analysis?▼

Feature-grouped flowcharts may not suit codebases lacking clear feature boundaries or those too small to produce cross-feature duplication. The unified proposals and handoff prompts target complex refactors requiring architectural auditing.