product-discovery

Conducts structured business interviews to produce validated product requirement briefs.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/duchuyn04/resume-analyze --skill product-discovery-duchuyn04
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-discovery
Source: https://github.com/duchuyn04/resume-analyze/tree/main/.agents/skills/product-discovery
Command: npx skills add https://github.com/duchuyn04/resume-analyze --skill product-discovery-duchuyn04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into building features based on vague or incomplete requirements, leading to scope creep, missed edge cases, and rework. This Skill enforces a rigorous discovery process that turns raw ideas into validated business briefs before any user stories or code are written. ## Core Features & Use Cases - Scale-Calibrated Interviewing: Asks users to pick a project scale (MVP, mid-size system, or enterprise platform) and adjusts interview depth accordingly to avoid over-engineering or superficial analysis. - Six-Pillar Case Study Grilling: Generates concrete scenario-based questions covering state machines, money/math invariants, concurrency, permissions, failure modes, and integration boundaries. - Independent G1 Quality Audit: Dispatches a reviewer subagent to audit the business brief against a four-criteria rubric before requesting user approval, blocking premature progression to user story design. - Use Case: A founder describes an in-house recruitment platform idea. The Skill interviews them across multiple rounds about candidate lifecycle states, scoring rules, and permission matrices, then writes a validated brief to docs/workflow/specs/. ## Quick Start Start a product discovery interview for my new recruitment management platform idea and produce a business brief.

Frequently Asked Questions about product-discovery

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

FAQPage Schema
How do I run a structured product discovery interview before writing user stories?▼

Use this Skill to interview stakeholders through iterative rounds of concrete case study questions covering state machines, business rules, and edge cases. It produces a business brief file that must pass an independent quality audit before user story design begins.

What questions should I ask when gathering requirements for a new software product?▼

Focus on six core pillars: entity lifecycle states, money and math invariants, concurrency conflicts, permission boundaries, failure modes with compensation flows, and integration source-of-truth rules. The Skill generates scenario-based questions automatically based on your project scale.

How do I avoid over-engineering requirements for an MVP?▼

The Skill first asks you to select a project scale: lean MVP, mid-size system, or enterprise platform. For MVPs it limits interviews to 5-15 core scenario questions and explicitly avoids enterprise concerns like distributed locking or multi-branch reconciliation.

Can discovery briefs be approved without a quality review?▼

No. The Skill requires an independent reviewer subagent to audit the brief against a four-criteria rubric covering scale fit, six-pillar coverage, concreteness, and blind spots. A REVISE verdict blocks gate approval and triggers additional interview rounds.

What output does a product discovery process produce?▼

It writes a business brief markdown file to docs/workflow/specs/ containing actors and permission matrices, an epic catalog, As-Is versus To-Be analysis, a domain glossary, business rules with IDs, data lifecycles, scope boundaries, and open questions.