w-wayfinder — Claude Code skill: decision maps and setup
The w-wayfinder Claude Code skill turns a multi-session task into a map of open decisions. The agent works through one ticket per session.
MIT 543 installs ★ 1 updated 2026-10-02
npx skills add blockmatic-icebox/basilic-skills --skill w-wayfinder -a claude-codeWhat w-wayfinder does
w-wayfinder charts a route when a goal takes more than one session to clarify. The agent asks questions, explores project facts, and records a map in a plan file. Its tickets represent decisions, not chunks of implementation.
The skill has a charting mode and a mode for working from an existing map. Before starting work on a ticket, the agent marks it as claimed, then records the answer and closes it. One session resolves at most one ticket.
It does not implement the map or create GitHub issues. Once no open decisions remain, the agent hands off to w-plan, then to w-build if implementation was requested. Automatic model invocation is disabled, so the skill must be invoked explicitly.
What it helps with
- turn a vague, multi-session task into open decisions
- keep a decision map in a plan file between sessions
- resolve a ticket and record its answer
Example prompts for the agent
- Create a decision map for this task; it will take several sessions.
- Resolve the first available ticket in the plan and record the answer.
- Continue from the map at
plans/roadmap.md.
How to install w-wayfinder
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-wayfinder -a claude-code2Manually: put the files in place
~/.claude/skills/w-wayfinder/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/w-wayfinder/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-wayfinder -a codex2Manually: put the files in place
.agents/skills/w-wayfinder/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-wayfinder -a cursor2Manually: put the files in place
.cursor/skills/w-wayfinder/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install blockmatic-icebox/basilic-skills skills/workflow/w-wayfinder2Manually: put the files in place
.github/skills/w-wayfinder/SKILL.md1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-wayfinder -a gemini-cli2Platform CLI
gemini skills install https://github.com/blockmatic-icebox/basilic-skills --path skills/workflow/w-wayfinderManually: put the files in place
.devin/skills/w-wayfinder/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-wayfinder -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about w-wayfinder
How do I install w-wayfinder in Claude Code?
Run npx skills add blockmatic-icebox/basilic-skills --skill w-wayfinder -a claude-code. The skill file will be at ~/.claude/skills/w-wayfinder/SKILL.md.
What does w-wayfinder do?
It maps unresolved decisions for work that spans multiple sessions, then helps resolve them one ticket at a time. Tickets describe choices, not implementation tasks.
How many tickets does w-wayfinder resolve in one session?
At most one. The agent records the answer on the map and closes that ticket.
Source text
SKILL.md · MIT
--- name: w-wayfinder description: Chart multi-session fog as a plan-file map of decision tickets. disable-model-invocation: true --- Use when the way to a destination is bigger than one session. Tickets are **decisions**, not build slices. [Clarify](../w-clarify/SKILL.md) is sparse gaps; [grill](../w-grill/SKILL.md) is a design-tree interview; this playbook is fog. When the way is already clear, stop and offer [plan](../w-plan/SKILL.md) or [build](../w-build/SKILL.md). Do not implement on the map. Do not create GitHub issues. Two modes. Never resolve more than one ticket per work-through session. ### Chart User invokes with a loose idea. 1. Name the destination with [grill](../w-grill/SKILL.md). The destination fixes scope. 2. Grill again breadth-first for open decisions and first takeable steps. Explore facts via [council](../w-council/SKILL.md). If there is no fog, do not write a map; ask how to proceed. 3. Write the map per [map output](references/map-output.md). Decisions so far empty; fog in Not yet specified; ticket only what is already sharp. 4. List blocking edges on tickets that wait. Research-shaped tickets: council. Look-and-feel: [v0](../w-v0/SKILL.md) or [ui](../w-ui/SKILL.md) as a cheap artifact, not a product UI. Default tickets: grill. 5. Stop. Charting hands off; it does not resolve tickets. ### Work through User invokes with a map (path or open plan). A ticket is optional. 1. Load the map at low resolution. Orient to Destination. 2. Take the named ticket, else the first frontier ticket. Mark it claimed on the map before any work. 3. Resolve it. Grill for HITL decisions. Council for in-repo or docs facts. Call skills named in Notes. 4. Record the answer on the ticket, gist it under Decisions so far, and close the ticket. Graduate fog that is now sharp. Move mis-scoped tickets to Out of scope. 5. When no tickets and no fog remain, the way is clear. Hand off to [plan](../w-plan/SKILL.md), then [build](../w-build/SKILL.md) if they asked to implement.
© blockmatic-icebox · MIT · blockmatic-icebox/basilic-skills