skills.rest
echarabati
echarabatiCOMMUNITY
Explore all skills by this author →
GitHub

discovery-expert

Conduct structured product discovery interviews and generate a Discovery Brief document.

Updated Feb 2, 2026
Search Tags:#scoping#documentation#requirements#product management#discovery#briefing
One-click install
npx skills add https://github.com/echarabati/adi-capital-admin --skill discovery-expert
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discovery-expert
Source: https://github.com/echarabati/adi-capital-admin/tree/main/.agent/skills/roles/discovery
Command: npx skills add https://github.com/echarabati/adi-capital-admin --skill discovery-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the initial product discovery phase by systematically gathering and documenting project requirements, ensuring clarity and alignment before development begins.

Core Features & Use Cases

  • Structured Interviewing: Guides users through a comprehensive 10-section discovery brief template.
  • Requirement Validation: Identifies gaps, inconsistencies, and risks in project scope.
  • Use Case: When starting a new software project, use this Skill to conduct a thorough discovery interview with stakeholders, generating a detailed Discovery Brief that serves as the project's foundational document.

Quick Start

Use the discovery-expert skill to start a new project discovery interview.

Frequently Asked Questions about discovery-expert

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

FAQPage Schema
What is product discovery and how does it help scope a new software project?▼

Product discovery systematically gathers project requirements to map scope, user roles, core features, and business rules. It ensures clarity and alignment before development begins by validating existing documentation and identifying risks.

How do I conduct a product discovery interview to gather requirements?▼

Conduct a product discovery interview by guiding stakeholders through a structured 10-section discovery brief template. This systematically captures project scope, data models, and business rules to generate a foundational requirements document.

Can I use this to validate existing project documentation and identify gaps?▼

Yes, you can use it to validate existing documentation. It identifies inconsistencies, gaps, and risks in project scope, ensuring your ongoing project maintains clear requirements and alignment.

What's the best way to map project scope and define user roles for a new project?▼

The best way to map project scope is to use a structured discovery brief template. It systematically captures user roles, core features, data models, and business rules into a comprehensive foundational document.

When do I need a discovery brief for product management?▼

You need a discovery brief when starting a new software project or ongoing phase. It streamlines the initial product discovery phase by documenting requirements and addressing critical gaps before development begins.

Related Skills

Explore More Product & Management Skills→
Davie521Davie521
7

teach-impeccable

Scan a codebase and write design context to .impeccable.md.

Community
Advanced
edlngedlng
2

pr-comment-humanizer

Rewrite pull request review comments into terse, imperative engineering tone.

Community
Intermediate
sumpalabssumpalabs
10

to-prd

Synthesize project conversations and codebase context into structured PRDs.

Official
Intermediate
martinffxmartinffx
39

atelier-spec-product

Conduct discovery interviews to define feature scope and requirements.

Community
Intermediate