wayfinder

Plans large efforts as decision tickets on an issue tracker.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/MSC72m/DevForge --skill wayfinder-msc72m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/MSC72m/DevForge/tree/main/skills/wayfinder
Command: npx skills add https://github.com/MSC72m/DevForge --skill wayfinder-msc72m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large, ambiguous efforts often exceed what a single agent session can hold, leaving teams without a clear path from a loose idea to a defined destination. This Skill charts that path as a shared map of decision tickets on the repo's issue tracker, resolving them one at a time until the way forward is clear. ## Core Features & Use Cases - Map Creation: Converts a loose idea into a single map issue (labelled wayfinder:map) with a named destination, notes, decisions-so-far index, and fog-of-war sections. - Decision Tickets: Breaks the effort into child issues typed as research, prototype, grilling, or task, with native blocking relationships defining the workable frontier. - Session-Based Resolution: Claims and resolves one ticket per session, records answers as resolution comments, and graduates newly specifiable fog into fresh tickets. - Use Case: A team facing a vague data-structure migration invokes the Skill to chart a map, then works through research and grilling tickets across multiple sessions until every decision blocking the migration is resolved. ## Quick Start Ask the agent to use the wayfinder skill to chart a map for your loosely defined project idea on the issue tracker.

Frequently Asked Questions about wayfinder

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

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

Invoke the Skill with your loose idea to chart a map: it names the destination, sketches unspecifiable questions into a Not yet specified section, and creates decision tickets as child issues. Each later session resolves one ticket until the way is clear.

What is a decision ticket in issue tracker planning?▼

A decision ticket is a child issue of the map whose resolution is a decision rather than a build slice. Each carries a type label: research, prototype, grilling, or task, and is sized to fit one 100K token agent session.

Does this planning approach work with any issue tracker?▼

The map, child tickets, blocking, and frontier queries are tracker-specific and defined in the tracker doc's Wayfinding operations section. If no tracker is provided, it defaults to a local-markdown tracker.

How are concurrent agent sessions prevented from duplicating work?▼

A session claims a ticket by assigning it to the dev driving the map before any work begins. Open unassigned tickets are unclaimed, so concurrent sessions skip assigned ones and pick from the remaining frontier.

When should a question stay as fog instead of becoming a ticket?▼

A question becomes a ticket when it can be stated precisely now, even if blocked. If it cannot yet be phrased sharply, it belongs in the map's Not yet specified section until resolving other tickets makes it specifiable.