mcpField
W
w-wayfinder

w-wayfinder

github.com/blockmatic-iceboxAgent workflows1543 installsUpdated 4w ago
Repository

About w-wayfinder

w-wayfinder is a Basilic workflow skill for mapping work that spans multiple sessions and resolving one ticket at a time. It separates exploratory charting from implementation and hands off to planning or building when the path is clear.

Key features

  1. 01Charts a destination from a loose idea
  2. 02Interviews to surface open decisions
  3. 03Explores repository and documentation facts
  4. 04Tracks tickets, dependencies, and decisions in a map
  5. 05Hands off to planning or building when ready

Use cases

  1. 01Mapping a broad idea into decisions and tickets
  2. 02Working through a saved plan one ticket at a time
  3. 03Identifying unresolved questions before implementation

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/blockmatic-icebox/basilic-skills --skill w-wayfinder

After installing, type/w-wayfinderin Claude Code to confirm it loaded.

Details

From the project README

Use when the way to a destination is bigger than one session. Tickets are decisions, not build slices. Clarify is sparse gaps; grill is a design-tree interview; this playbook is fog. When the way is already clear, stop and offer plan or build. 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. The destination fixes scope.
  2. Grill again breadth-first for open decisions and first takeable steps. Explore facts via council. If there is no fog, do not write a map; ask how to proceed.
  3. Write the map per map output. 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 or ui 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, then build if they asked to implement.

Comments

Markdown supported