discovery-process

Convert problem hypotheses into validated requirements briefs through structured discovery.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/jason23452/my-skill --skill discovery-process-jason23452
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discovery-process
Source: https://github.com/jason23452/my-skill/tree/main/flow/discovery-process
Command: npx skills add https://github.com/jason23452/my-skill --skill discovery-process-jason23452

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often jump from a solution idea straight to user stories without evidence, leading to misaligned requirements. This Skill runs a lightweight discovery pass that separates evidence from assumptions and produces a requirements brief with enough confidence for User Story generation. ## Core Features & Use Cases - Problem Framing: Frame the problem hypothesis first, using a problem-framing canvas when requests arrive solution-first. - Evidence Synthesis: Gather and group evidence from docs, customer feedback, support tickets, analytics, and stakeholder notes by user outcome rather than requested feature. - Validation Gap Triage: Classify gaps as blocking, important, or non-blocking, then decide whether to draft requirements, ask targeted questions, or defer. - Use Case: A stakeholder requests a new dashboard feature. Use this Skill to frame the underlying problem, synthesize existing feedback, identify blocking gaps around permissions and data, and output validated requirement seeds for the Requirements Agent. ## Quick Start Run a discovery pass on this feature request and produce a requirements brief with evidence, assumptions, and validation gaps.

Frequently Asked Questions about discovery-process

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

FAQPage Schema
How do I run a product discovery process before writing requirements?▼

Frame the problem hypothesis, gather evidence from docs and customer feedback, synthesize opportunities by user outcome, classify validation gaps, then decide whether to draft requirements, ask targeted questions, or defer. The output feeds directly into User Story generation.

What is the difference between discovery and implementation planning?▼

Discovery validates whether a problem is worth solving and produces requirement seeds with evidence. Implementation planning defines how to build the solution. This Skill explicitly covers discovery only and does not create implementation plans.

How do I separate assumptions from evidence in product research?▼

List all inputs from docs, feedback, tickets, and analytics, then explicitly tag each as evidence or assumption. Assumptions that would change scope, users, or acceptance criteria become blocking validation gaps requiring targeted questions.

When should I defer a feature instead of drafting requirements?▼

Defer when blocking gaps exist that would change scope, target users, acceptance criteria, permissions, data, or compliance. Non-blocking gaps can be drafted as documented assumptions without delaying the requirements brief.

Does this discovery process create work items or run experiments?▼

No. The Skill explicitly avoids running experiments, opening sessions, creating work items, or syncing to ADO. It only produces a requirements brief for the downstream Requirements Agent.