wayfinder

Manage project decisions and investigations via GitHub issues with YAML.

25|5|Updated May 9, 2026
One-click install
npx skills add https://github.com/kamp-us/phoenix --skill wayfinder-kamp-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/kamp-us/phoenix/tree/main/claude-plugins/kampus-pipeline/skills/wayfinder
Command: npx skills add https://github.com/kamp-us/phoenix --skill wayfinder-kamp-us

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of transforming a fuzzy project idea into a structured plan, reducing ambiguity and ensuring a clear path forward.

Core Features & Use Cases

  • Chart Mode: Create a new issue to define the project's destination and list open decisions.
  • Work Mode: Progress the project by resolving open decisions and investigations.
  • Use Case: When planning a new feature for a software product, use Wayfinder to outline the requirements and potential challenges before writing code.

Quick Start

To start a new wayfinder map, use the command: /wayfinder chart "Develop a new feature for the task management app."

Frequently Asked Questions about wayfinder

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

FAQPage Schema
How do I structure project ideation and track decisions using GitHub issues?

Project ideation is structured by creating a living map of decisions within GitHub issues using YAML. This approach tracks open investigations and resolves them to clear the path for software development or strategic planning.

What is the best way to outline requirements before writing code for a new feature?

The best way to outline requirements is using chart mode to define the project destination and list open decisions. This transforms a fuzzy idea into a structured plan before any development begins.

Do I need GitHub API access to manage project planning investigations?

Yes, GitHub API access is required to manage project planning investigations. The system uses the API to directly create and modify issues containing structured YAML content for decision tracking.

How does decision tracking work during software product planning?

Decision tracking works by applying chart mode to initially define requirements and work mode to progressively resolve open investigations. This maintains a living map that reduces ambiguity throughout the product planning lifecycle.

Can I use YAML to format issue content for project planning?

Yes, YAML is used to format issue content for project planning. This structured format allows the system to manage decisions and investigations directly within GitHub issues.

What are the limitations of using GitHub issues for strategic planning and decision tracking?

GitHub issue limitations for strategic planning include relying entirely on API access for creation and modification, and requiring YAML formatting for structured content, making it less suited for unstructured brainstorming.