skills.rest
LazyNinja435
LazyNinja435COMMUNITY
Explore all skills by this author →
GitHub

Requirement Discovery

Elicit and clarify product requirements into testable acceptance criteria documentation.

1|Updated Jun 3, 2026
Search Tags:#documentation#requirements#discovery#stakeholder#product-management#acceptance-criteria
One-click install
npx skills add https://github.com/LazyNinja435/astrai --skill requirement-discovery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Requirement Discovery
Source: https://github.com/LazyNinja435/astrai/tree/main/.ai/skills/product-owner/requirement-discovery
Command: npx skills add https://github.com/LazyNinja435/astrai --skill requirement-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates ambiguity in product development by systematically eliciting, clarifying, and documenting stakeholder needs before any planning or implementation begins.

Core Features & Use Cases

  • Structured Elicitation: Guides the AI to ask the right questions (who, what, when, why) to uncover hidden constraints and business goals.
  • Standardized Documentation: Ensures all requirements are captured using a consistent template with clear, testable acceptance criteria.
  • Use Case: When a stakeholder requests a new feature, use this skill to move from a vague idea to a fully defined requirement document that is ready for the development team.

Quick Start

Use the requirement discovery skill to interview the stakeholder about the new user authentication feature and document the findings.

Frequently Asked Questions about Requirement Discovery

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

FAQPage Schema
How do I turn vague stakeholder needs into actionable requirements?▼

Requirement discovery systematically elicits and clarifies product requirements from stakeholder inputs to produce unambiguous, actionable documentation with testable acceptance criteria for the development team.

What is the best way to document product requirements with clear acceptance criteria?▼

The best way to document product requirements is by using a standardized template that captures stakeholder inputs through structured elicitation, ensuring all features have unambiguous, testable acceptance criteria aligned with business goals.

How do I conduct stakeholder interviews for product feature discovery?▼

Conduct stakeholder interviews for product feature discovery by asking structured questions covering who, what, when, and why to elicit needs, clarify constraints, and align business goals with technical implementation before planning begins.

When in the product development lifecycle should I use requirement discovery?▼

Requirement discovery should be used during the early stages of the product development lifecycle when project scope and feature definitions are being established, before any planning or implementation begins.

Can I use this to align business goals with technical implementation for new features?▼

Yes, requirement discovery aligns business goals with technical implementation by systematically eliciting and documenting stakeholder needs, ensuring the development team receives unambiguous requirements with testable acceptance criteria.

Related Skills

Explore More Product & Management Skills→
co-cddoco-cddo
4

bmad-agent-analyst

Translate vague business needs into detailed, actionable requirements.

Official
Advanced
root-5root-5

planning

Plan, prioritize, and track project progress with centralized reporting.

Community
Intermediate
darblexdarblex

Project Management & Agile Skill

Decompose projects into user stories, acceptance criteria, and sprint tasks.

Community
Intermediate
YeaChan05YeaChan05

spec

Define problem, scope, and acceptance criteria into a /plan artifact.

Community
Intermediate