Clarify ambiguous requirements through guided Q&A and structured planning.
npx skills add https://github.com/outfitter-dev/agents --skill pathfinding
Please help me install this Agent Skill. Skill: Pathfinding Source: https://github.com/outfitter-dev/agents/tree/main/baselayer/skills/pathfinding Command: npx skills add https://github.com/outfitter-dev/agents --skill pathfinding
This Skill provides adaptive Q&A to turn unclear requirements into clear paths, helping teams brainstorm, plan, and validate ideas before implementation.
Initiate a pathfind session to clarify requirements and generate a concrete plan.
High-intent search queries and answers about installing and using this skill.
Clarifying requirements means using structured Q&A to identify missing details, assumptions, and dependencies. This Skill guides you through a phase-driven workflow—Prep, Explore, Clarify, Deliver—to transform ambiguous requests into concrete plans with clear next steps and confidence-tracked decisions.
Collaborative brainstorming works best with guided questions that surface hidden assumptions and missing context. This Skill provides adaptive Q&A and artifact generation to help teams validate ideas, track readiness levels, and produce a structured plan before implementation begins.
Convert vague requests into actionable plans by running a pathfinding session that elicits missing details through guided questions, produces quick-start steps, and tracks confidence levels. The phase-driven workflow ensures decisions are documented and implementation barriers are identified early.
Yes, this Skill works across brainstorming sessions, planning activities, and requirements clarification. It applies structured Q&A and tool guidance to any ambiguous task where you need to move from unclear goals to clear, validated requirements and deliverables.
A pathfinding session produces structured artifacts including a clear plan, quick-start steps, identified decisions, and confidence-level tracking. These deliverables give teams the concrete direction needed to move from requirements gathering into implementation.
magnus919Map stakeholders, conduct interviews, and distill requirements into formal specifications.
ev3rlitValidate built features through conversational user-acceptance testing with phase logs.
timequityLog architectural decisions as ADR entries to docs/DECISIONS.md.
mcampbellrGuide Socratic ideation sessions and route outputs to GSD artifacts.
