prd-discovery

Coordinate structured discovery interviews and generate a Discovery Brief for PRD authoring.

2|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/yesplease-studio/prd-please --skill prd-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-discovery
Source: https://github.com/yesplease-studio/prd-please/tree/main/skills/prd-discovery
Command: npx skills add https://github.com/yesplease-studio/prd-please --skill prd-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run a structured pre-authoring interview to surface what is known, confirm what can be inferred, and explicitly name what is unknown across all product domains. Produces a Discovery Brief that PRD author ingests as its primary input, enabling a solid foundation before writing a Strategic PRD.

Core Features & Use Cases

  • Comprehensive context gathering: collects available inputs (transcripts, briefs, notes) and assesses what domains are missing.
  • Domain-focused interview: conducts Phase 2 interviews across Problem & Context, Users & Scenarios, Commercial Context, Technical Constraints, Data & Privacy, Design & Experience, and Open Questions.
  • Discovery Brief synthesis: produces a concise artifact detailing confirmed facts, inferences, and open questions with owners to guide PRD authoring.

Quick Start

Initiate by gathering any available context, perform the Phase 2 domain interviews across Problem, Users, Commercial Context, Technical Constraints, Data & Privacy, Design, and Open Questions, and generate the Discovery Brief.

Frequently Asked Questions about prd-discovery

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

FAQPage Schema
What is a product discovery interview and how does it inform a PRD?

A product discovery interview is a structured process to surface known facts, inferences, and unknowns across product domains before writing a Strategic PRD. It synthesizes stakeholder input into a Discovery Brief that serves as the primary foundation for PRD authoring.

How do I conduct stakeholder discovery interviews for product requirements?

You conduct stakeholder discovery interviews by first gathering available context like transcripts and notes, then applying structured interviews across domains like Problem, Users, Commercial Context, Technical Constraints, Data, and Design to produce a concise Discovery Brief.

What domains should I cover when gathering context for a product discovery brief?

When gathering context for a product discovery brief, you should cover Problem & Context, Users & Scenarios, Commercial Context, Technical Constraints, Data & Privacy, Design & Experience, and Open Questions to ensure comprehensive pre-authoring input.

Can I use existing notes and transcripts as input for PRD discovery?

Yes, you can use existing notes and transcripts as input for PRD discovery. The process collects available inputs to assess existing knowledge and identify missing domains before conducting structured interviews to finalize the Discovery Brief.

What is the best way to identify open questions before writing a Strategic PRD?

The best way to identify open questions before writing a Strategic PRD is to run structured discovery interviews that explicitly distinguish confirmed facts from inferred conclusions and unresolved queries, assigning owners to each open question in the final Discovery Brief.

What is the difference between confirmed facts and inferred conclusions in a Discovery Brief?

In a Discovery Brief, confirmed facts are validated knowledge gathered during stakeholder interviews, while inferred conclusions are logical deductions made from available context. The brief explicitly separates these to guide PRD authoring and highlight domains needing additional input.