pocock-wayfinder

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

Updated Dec 18, 2025
One-click install
npx skills add https://github.com/l0lxl0lw/dotfiles --skill pocock-wayfinder-l0lxl0lw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pocock-wayfinder
Source: https://github.com/l0lxl0lw/dotfiles/tree/main/ai/shared/skills/mattpocock/pocock-wayfinder
Command: npx skills add https://github.com/l0lxl0lw/dotfiles --skill pocock-wayfinder-l0lxl0lw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large, ambiguous efforts exceed what a single agent session can hold, and the path from idea to destination is unclear. This Skill breaks such work into a shared map of decision tickets on the repo's issue tracker, resolving them one at a time until the route is clear. ## Core Features & Use Cases - Map-based planning: Creates a single map issue (labelled wayfinder:map) holding the destination, notes, decisions-so-far index, fog of war, and out-of-scope sections. - Typed decision tickets: Child issues labelled research, prototype, grilling, or task, each sized to one agent session, with native tracker blocking to define the frontier. - Two invocation modes: Chart a new map from a loose idea, or work through an existing map by claiming and resolving 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, chart the open decisions as tickets, fire research subagents in parallel, then resolve tickets session by session until the way is clear. ## Quick Start Ask the agent to use the pocock-wayfinder skill to chart a wayfinding map for your loosely defined project idea on the repo's issue tracker.

Frequently Asked Questions about pocock-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?

Use wayfinding: chart a map issue on the repo's issue tracker holding the destination and fog of war, then create decision tickets as child issues. Resolve one ticket per session until no decisions remain and the way to the destination is clear.

What is a decision ticket in issue-tracker-based planning?

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

Does pocock-wayfinder work with any issue tracker?

The map, tickets, blocking, and frontier queries are tracker-specific and defined by a tracker doc provided to the skill. If no tracker is provided, it defaults to a local-markdown tracker; native blocking is preferred over body conventions.

When should I not use wayfinding for a task?

Skip it when the way to the destination is already clear and the whole journey fits in one session — charting surfaces no fog. It is also planning-only by default, so pure execution work should be handed off rather than mapped.

How are tickets claimed and resolved across parallel sessions?

A session claims a ticket by assigning it before any work, so concurrent sessions skip it. Resolution posts an answer comment, closes the issue, and appends a context pointer to the map's Decisions-so-far section.