skills.rest
Tcuzzo
TcuzzoCOMMUNITY
Explore all skills by this author →
GitHub

the_path

Converts an unclear destination into a decision-resolving ticket map for planning work.

1|Updated Jun 17, 2026
Search Tags:#planning#requirements#roadmap#task decomposition#scope management#wayfinding#decision tickets
One-click install
npx skills add https://github.com/Tcuzzo/HydraAgent_public --skill the-path-tcuzzo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: the_path
Source: https://github.com/Tcuzzo/HydraAgent_public/tree/main/skills/the_path
Command: npx skills add https://github.com/Tcuzzo/HydraAgent_public --skill the-path-tcuzzo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a goal arrives as vague prose or an ambiguous request, teams either guess at a route or stall by parking questions on a human. This Skill turns a destination into a map of decision-resolving tickets, resolving unknowns from evidence instead of asking. ## Core Features & Use Cases - Decision-first planning: Each ticket resolves a decision rather than a slice of build work, so the map ends when nothing is left to decide. - Fog of war management: Undecidable future questions stay as fog until resolving a live ticket makes them specifiable, graduating them one at a time. - Ask-me bar discipline: Only genuine human decisions (taste, vision, destructive risk) reach the user; everything else resolves from invariants, memory, and intent. - Use Case: A stakeholder says "make onboarding feel effortless." The Skill deconstructs the ambiguous ask, charts named tickets for each open decision, and hands off only when the way is clear. ## Quick Start Invoke the path skill to chart the way from my current goal and produce a map of named decision tickets.

Frequently Asked Questions about the_path

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

FAQPage Schema
How do I turn a vague request into an actionable plan?▼

Chart the destination into named tickets where each ticket resolves one decision, not a slice of build work. Ambiguous prose asks are first deconstructed through syntactic, cultural, and intent analysis before any route is charted.

What is the difference between a ticket and fog in planning?▼

A ticket is a question you can state precisely now, even if blocked. Fog covers decisions you can sense coming but cannot yet phrase sharply; resolving live tickets clears the fog and graduates new tickets one at a time.

When should a decision be escalated to a human?▼

Escalate only when the decision is genuinely theirs: taste, vision, or destructive and data-loss risk. Everything else resolves from invariants, memory, and intent, and a real ask arrives as a plain summary with choices.

How do I avoid hallucinating file paths during planning?▼

Read the exact map blocks and use the repository's own source truth, live help output, and real schema before acting. Guessing a path is treated as a terminal failure under the never-run-lost invariant.

When is this planning approach not appropriate?▼

It is not suited for work beyond the stated destination, which is out of scope rather than fog and never graduates into tickets. It also plans rather than executes, so hand off once the map is clear.

Related Skills

Explore More Product & Management Skills→
Brave-LabsBrave-Labs

Dev10x-park

Route deferred items to PRs, tickets, code comments, or project TODOs.

Official
Advanced
NAMEWTANAMEWTA
2

wayfinder

Plans large ambiguous work as a map of investigation tickets on an issue tracker.

Community
Advanced
anionzoanionzo

brainstorming

Convert vague requests into concrete directions with locked decisions.

Community
Intermediate
jellyrockjellyrock
37

sonnet

Execute procedural implementation plans for the JellyRock Roku client on the Sonnet model.

Official
Advanced