Automate interactive discovery sessions into a structured markdown document.
npx skills add https://github.com/Xalior/agent-skills --skill discovery-xalior
Please help me install this Agent Skill. Skill: discovery Source: https://github.com/Xalior/agent-skills/tree/main/discovery Command: npx skills add https://github.com/Xalior/agent-skills --skill discovery-xalior
Interactive requirement discovery before planning starts. Use when the user has an idea or loose requirement and wants to sharpen the goal, scope, and approach before anyone plans tasks or writes code. Produces a single markdown document that survives context reset.
Create a new discovery doc for your idea and follow the Goal, Scope in, Scope out, Approach, and Open Questions steps.
High-intent search queries and answers about installing and using this skill.
To shape loose ideas into a concrete discovery brief, interactive requirement discovery automates section-by-section conversations to define your goal, scope, and approach, producing a single markdown document.
Documenting project scope and open questions during early kickoff sessions is best handled by creating a formal discovery skeleton that captures goals, scope boundaries, approach, and open questions within a markdown file.
You can resume requirement discovery after a context reset by reading the existing markdown discovery document in full, investigating its references, and identifying the next open question to continue the section-by-section loop.
To capture out-of-scope boundaries and approach hypotheses for new features, a discovery conversation guides you step-by-step through scope exclusions and approach formulation, immediately recording your answers into the document.
Brownfield discovery does investigate existing project files before defining requirements by spawning parallel sub-agents to research READMEs, manifests, directory trees, and recent commits, surfacing unknown context.
You should not use an automated discovery process when your requirements are already fully defined, as the tool is designed to sharpen loose ideas and surface vagueness before finalizing a ready-to-plan document.
cinjoffCapture user-defined tasks, ideas, and issues as structured to-dos with duplicate checking and git commits.
Owl-ListenerDefine and document a design brief with problem space, audience, constraints, and success criteria.
BobJu0721Catalog and translate PRD content into a structured blueprint with frontmatter metadata.
Clay-HHKGuides iterative drafting and reader testing of structured documents like RFCs and PRDs.
