wayfinder

Plan large multi-session work as decision tickets on an issue tracker.

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/richard-jh-mccrae/PokemonAI --skill wayfinder-richard-jh-mccrae
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/richard-jh-mccrae/PokemonAI/tree/main/.agents/skills/wayfinder
Command: npx skills add https://github.com/richard-jh-mccrae/PokemonAI --skill wayfinder-richard-jh-mccrae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large projects often exceed what a single agent session can hold in context, causing lost decisions, duplicated work, and unclear progress. This Skill decomposes a huge chunk of work into a shared map of decision tickets on your issue tracker so progress survives across sessions. ## Core Features & Use Cases - Decision Ticket Mapping: Breaks an oversized body of work into individual decision tickets tracked on your issue tracker. - Incremental Resolution: Resolves tickets one at a time until the path to the destination is clear. - Cross-Session Continuity: Uses the issue tracker as shared memory so any agent session can pick up where the last one stopped. - Use Case: You need to migrate a large monorepo to a new framework. Use this Skill to create a ticket map of every open decision, then work through them session by session without losing context. ## Quick Start Use the wayfinder skill to plan this large migration project as decision tickets on my issue tracker and start resolving them one at a time.

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 large for one agent session?▼

Decompose the work into a map of decision tickets on your issue tracker, then resolve them one at a time. The tracker acts as shared memory so each new session can continue where the previous one stopped.

How do decision tickets help with multi-session agent workflows?▼

Decision tickets externalize project state onto an issue tracker instead of relying on conversation context. Each ticket captures one open decision, so any session can read the map and continue resolving work without re-discovery.

Does this approach require a specific issue tracker?▼

The workflow is defined around an issue tracker as the shared map of decision tickets, but the skill delegates to an authoritative workflow document for host-specific invocation details. Tool names are translated to the host environment's equivalents.

When should I not use ticket-based planning for agent work?▼

Avoid it for small tasks that fit comfortably in a single session, where ticket overhead adds no value. It is designed for work larger than one session can hold, where decisions would otherwise be lost between sessions.