Wayfinder Maps plugin
CLI and viewer for wayfinder maps: ticket status, a linter and a star map of the plans an agent keeps under .plan
- 145 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The `wayfinder-pull` script reads GitHub issues with your access and writes files into `.plan/`
- The plugin bundles several skills that run dialogues and write prototypes in the project
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/wayfinder-mapsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The `wayfinder-pull` script reads GitHub issues with your access and writes files into `.plan/`
- The plugin bundles several skills that run dialogues and write prototypes in the project
This is third-party code. Review the repository files before installing.
What it does
Wayfinder Maps is a read-only utility for wayfinder maps, the markdown planning memory an agent leaves under `.plan/` when it charts a large effort as a graph of investigation tickets. Matt Pocock created the wayfinder method and skills, and the repository adapts them and adds tooling. The `wayfinder-maps status` command shows what is resolved, what is in flight and what is ready to claim (the frontier: open, unclaimed tickets with every blocker resolved). `wayfinder-maps lint` checks whether the map still tells the truth. `wayfinder-maps serve` and `app` show the map as a star map in a browser or a native window. The `scripts/wayfinder-pull` script mirrors a map kept as GitHub issues into `.plan/`. The Claude Code plugin bundles the `wayfinder-maps` skill and the four skills it invokes: `grill-me`, `research`, `prototype` and `domain-modeling`. These are MIT adaptations of Pocock skills. The utility is written in Go.
Who it is for. Developers who run large efforts with an agent using the wayfinder method and want to see status, check the truthfulness of the map and view it visually.
Good fit when
- The planning map under `.plan/` has grown and you need to see which tickets are ready
- Decisions on the map may go stale and a linter checks them
- You need a visual star map of the plan in a browser
- The map is kept in GitHub issues and a copy is needed in `.plan/`
Not a fit when
- You do not use the wayfinder method: the utility reads only its format
- You need to edit the map: the utility is read-only
- You need a general task tracker for a team instead of a map kept by an agent
Example request
Show the status of the .plan/daily-timeline map, name the frontier tickets and lint it for stale decisionsLimitations
The utility reads wayfinder-format maps and changes nothing in them. Installing the plugin needs Claude Code, while the skills can be copied into any agent by hand from the `skills/` folder. The native window and viewer depend on the platform, with separate files for macOS, Linux and Windows in the tree. The `wayfinder-pull` script works with GitHub issues and needs access to them. The last commit is dated October 6, 2026, and the skills themselves are adapted from the repository of Matt Pocock.
How to disable. Run `/plugin uninstall wayfinder-maps@wayfinder-maps` in Claude Code, delete the `wayfinder-maps` binary and the copied skill folders. The maps under `.plan/` stay in your projects and can be deleted by hand.
FAQ
What is a wayfinder map?
Markdown planning memory under `.plan/` where an agent lays a large effort out as a graph of investigation tickets.
What is the frontier?
Open, unclaimed tickets whose blockers are all resolved. `wayfinder-maps status` shows them.
Does the utility change maps?
No, it only reads: status, lint and viewing.
How do I install the plugin?
With `/plugin marketplace add rengwu/wayfinder-maps` and `/plugin install wayfinder-maps@wayfinder-maps`.
Who created the wayfinder method?
Matt Pocock. The repository adapts his skills under MIT and adds the utility and viewer.
Discussion
No questions or reviews yet.
Related
PluginsA plan-then-build pipeline for Claude Code and Codex: spec, small contracts, stage checks, review and lessons learned
A Claude Code mod that draws a live map of the work beside the chat: tool calls, hooks, skills and subagents show up at once.
A skill that maps a repository into meaningful blocks, walks through the code on that map step by step and highlights broken spots
A marketplace of six independent Claude Code plugins, from a project map and a task board to a guided installer
A coding-agent monitor with a project component map and an experimental 3D kitchen view of ongoing tasks
codesight maps a project in one run: routes, DB models, dependencies, env vars. It gives the map to an agent as files or through an MCP server
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Wayfinder Maps (this card) | no | 145 | |
| grill-me: plan interview skill | no | 1,560 | a utility for reading and linting wayfinder maps bundled with four skills in a plugin |
| grill-with-ui | no | 330 | shows the planning map as a star chart and checks it with a linter |
README in short
The README explains that this is a read-only CLI and viewer for wayfinder maps and lists the `status`, `lint`, `serve` and `app` commands plus the `wayfinder-pull` script. A sample `status` output shows resolved and open tickets, the frontier and undermined decisions. Plugin installation and the option of copying skills into any agent follow.