wayfinder

Create a human-readable map of project work, dependencies, and decisions.

Updated May 3, 2026
One-click install
npx skills add https://github.com/druejaramillo/skills --skill wayfinder-druejaramillo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/druejaramillo/skills/tree/main/project/wayfinder
Command: npx skills add https://github.com/druejaramillo/skills --skill wayfinder-druejaramillo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of project ambiguity by creating a human-readable map of work items, dependencies, and open decisions, ensuring that team members understand the path forward without relying on automated subagents or implicit assumptions.

Core Features & Use Cases

  • Dependency Mapping: Visualizes directional links between work items and identifies blockers.
  • Decision Tracking: Captures critical decisions, evidence, and remaining unknowns to prevent project stalls.
  • Use Case: Use this when you need to clarify the delivery path for a complex feature launch, ensuring all stakeholders agree on the scope, risks, and current status of each component.

Quick Start

Use the wayfinder skill to map the work and dependencies required to ship the new authentication feature.

Frequently Asked Questions about wayfinder

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

FAQPage Schema
How do I map project dependencies and identify blockers for a complex feature launch?

To map project dependencies and identify blockers, this skill creates a human-readable map of work items and their directional links. It visualizes delivery paths to help stakeholders agree on scope, risks, and current status without relying on automated subagents.

What is dependency mapping and how does it clarify project delivery paths?

Dependency mapping is the process of visualizing directional links between work items to clarify project delivery paths. It creates a human-readable record that ensures team members understand the path forward and identify blockers without implicit assumptions.

How do I track open decisions and prevent project stalls across my backlog?

To track open decisions and prevent project stalls, this skill captures critical decisions, supporting evidence, and remaining unknowns. It maintains a persistent, evidence-backed record of work status to improve legibility and alignment across features.

Can I use local Markdown files to maintain a persistent record of project work status?

Yes, you can use local Markdown files to maintain a persistent, evidence-backed record of project work status. The skill requires access to project trackers or local Markdown files to map work items, dependencies, and open decisions effectively.

When should I use a human-owned project map instead of automated subagents for work breakdown?

You should use a human-owned project map instead of automated subagents when you need to clarify the delivery path for complex initiatives and ensure stakeholders explicitly agree on scope, risks, and status without relying on implicit assumptions.