anvil-wayfinder

Plans large multi-session efforts as decision-ticket maps on an issue tracker.

1|Updated Aug 27, 2026
One-click install
npx skills add https://github.com/rogerznts/anvil --skill anvil-wayfinder-rogerznts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: anvil-wayfinder
Source: https://github.com/rogerznts/anvil/tree/main/anvil/.claude/skills/anvil-wayfinder
Command: npx skills add https://github.com/rogerznts/anvil --skill anvil-wayfinder-rogerznts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large, fuzzy efforts that exceed a single agent session lose context between sessions and drift without a shared plan. This Skill charts the work as a map of decision tickets on the repo's issue tracker, so every session orients to the destination and resolves one decision at a time. ## Core Features & Use Cases - Map as index: Creates a single tracker issue labelled wayfinder:map holding the destination, notes, decisions-so-far, fog of war, and out-of-scope sections. - Typed decision tickets: Spawns child issues labelled research, prototype, grilling, or task, each sized to one 100K-token session, with native blocking edges defining the frontier. - Two invocation modes: Chart a new map from a loose idea, or work through an existing map by claiming, resolving, and closing one ticket per session. - Use Case: You need to plan a data-structure migration too big for one session. Invoke the Skill to grill out the destination, fan out the open decisions into tickets, fire research subagents in parallel, then resolve tickets one at a time until the route is clear. ## Quick Start Ask the agent to chart a wayfinder map for your large loosely-defined effort, naming the destination you want to reach.

Frequently Asked Questions about anvil-wayfinder

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

FAQPage Schema
How do I plan work too big for one agent session?▼

Invoke the Skill with your loose idea to chart a map: it grills out the destination, fans out open decisions breadth-first, and creates child tickets on your issue tracker. Each later session claims and resolves exactly one ticket until the route is clear.

How do I break a large project into decision tickets on an issue tracker?▼

The Skill creates a map issue labelled wayfinder:map, then spawns child issues for each sharply-stated question, wiring blocking edges in a second pass. Questions you cannot yet phrase precisely stay in the map's Not yet specified fog section.

What issue trackers does the wayfinding map support?▼

The map works on any tracker the repo has configured via its tracker doc, which defines how maps, child tickets, blocking, and frontier queries are expressed. If no tracker is provided, it defaults to a local-markdown tracker.

Can multiple agent sessions work on the same map in parallel?▼

Yes. A session claims a ticket by assigning it before starting work, so concurrent sessions skip claimed tickets. The frontier is the set of open, unblocked, unclaimed child issues, and each session resolves at most one ticket.

When should I not use a wayfinding map?▼

Skip the map when charting surfaces no fog: if the way to the destination is already clear and the whole journey fits one session, a map adds overhead. The Skill itself stops and asks how to proceed in that case.