skills.rest
1ambda
1ambdaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requirements-discovery

Guide stakeholder interviews through five discovery phases to produce structured specifications.

2|1|Updated Dec 26, 2025
Search Tags:#PRD#requirements gathering#elicitation#product discovery#specification writing#stakeholder interview
One-click install
npx skills add https://github.com/1ambda/dataops-platform --skill requirements-discovery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-discovery
Source: https://github.com/1ambda/dataops-platform/tree/main/.copilot/skills/requirements-discovery
Command: npx skills add https://github.com/1ambda/dataops-platform --skill requirements-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of gathering requirements from stakeholders, ensuring all needs are identified, contradictions are surfaced, and clear specifications are produced.

Core Features & Use Cases

  • Structured Interviews: Guides through 5 distinct phases of discovery (Problem, User, Scope, Constraints, Success).
  • Technique Application: Employs methods like "5 Whys", quantifying vague requirements, and identifying policy contradictions.
  • Use Case: Kick off a new feature development by using this Skill to conduct a thorough discovery interview with the product owner, resulting in a well-defined *_FEATURE.md document.

Quick Start

Begin a new feature discovery process by asking the AI to guide you through the problem space phase.

Frequently Asked Questions about requirements-discovery

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

FAQPage Schema
How do I gather product requirements and uncover hidden stakeholder needs?▼

Requirements gathering is facilitated through structured stakeholder interviews that identify hidden needs, surface contradictions, and produce clear product specifications. This Skill guides the elicitation process using a phased discovery approach.

What is the best way to structure a stakeholder interview for product discovery?▼

A structured stakeholder interview for product discovery should follow five distinct phases: problem definition, user analysis, scope definition, constraint identification, and success metric establishment. This ensures comprehensive coverage of the product requirements.

How do I write a PRD from vague feature requests and conflicting constraints?▼

Writing a PRD from vague requests involves applying techniques like the 5 Whys and quantifying vague requirements to identify policy contradictions. This process surfaces hidden conflicts and translates them into a well-defined feature specification document.

Can I use this requirements elicitation process for any product development scale?▼

Yes, requirements elicitation applies to any product development scale where stakeholder alignment is needed. It systematically defines the scope, constraints, and success metrics regardless of the overall feature complexity or team size.

What techniques are used to surface contradictions during requirements gathering?▼

Techniques to surface contradictions during requirements gathering include applying the 5 Whys method, quantifying vague requirements, and actively identifying policy contradictions. These methods clarify conflicting stakeholder demands and refine the scope.

What document output should I expect from a complete product discovery interview?▼

The expected document output from a complete product discovery interview is a well-defined feature specification file. This structured document captures the problem definition, user analysis, scope, constraints, and success metrics established during the session.

Related Skills

Explore More Product & Management Skills→
cshyangcshyang

gsd:workflow:discovery-phase

Plan and execute a project discovery phase to define requirements and scope.

Community
Intermediate
busboom-software-studiobusboom-software-studio
1

create-tickets

Convert architecture-update.md and usecases.md into sequenced tickets with dependencies.

Official
Advanced
guma154-cmdguma154-cmd

aiox-sm

Create and validate user stories from PRDs for Agile sprint planning.

Community
Intermediate
rnaarlarnaarla

to-prd

Generate a PRD from conversation context and publish it to the issue tracker.

Community
Advanced