requirements-gathering

Guide stakeholder interviews to document feature requirements and scope.

Updated Jan 4, 2026

Search Tags:#requirements #discovery #MVP #interviews #scope #stakeholders

Ready to run

npx skills add https://github.com/shwilliamson/a-test --skill requirements-gathering-shwilliamson

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-gathering
Source: https://github.com/shwilliamson/a-test/tree/main/.automatasaurus/skills/requirements-gathering
Command: npx skills add https://github.com/shwilliamson/a-test --skill requirements-gathering-shwilliamson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams structure and execute thorough discovery by guiding you through targeted questions, checklists, and techniques to define scope before creating issues.

Core Features & Use Cases

Structured Interview Guide: A reusable framework of questions to extract goals, users, data, and constraints from stakeholders.
Scope & Edge Case Definition: Tools to delineate in-scope vs out-of-scope items and surface edge cases early.
Documentation & Alignment: Templates and prompts to capture decisions and approval signals for alignment across teams.
Use Case: When starting a new feature, run this skill to elicit requirements, confirm success metrics, and lock in MVP boundaries.

Quick Start

To begin, run the discovery skill to outline goals, identify users, list data requirements, and document edge cases before creating any issues.

Frequently Asked Questions about requirements-gathering

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

FAQPage Schema

How do I gather requirements before building a new feature?▼

Gather requirements by running a structured discovery process that guides stakeholder interviews to extract goals, users, data needs, and constraints. This approach ensures you capture edge cases and define MVP boundaries before creating any issues.

What is the best way to define scope and success criteria during discovery?▼

Defining scope and success criteria involves using structured interview guides to delineate in-scope versus out-of-scope items early. This process surfaces edge cases and locks in MVP boundaries to align product, design, and engineering teams.

How do I conduct stakeholder interviews for MVP planning?▼

Conduct stakeholder interviews for MVP planning by applying a reusable framework of targeted questions. This framework elicits goals, data requirements, constraints, and success metrics to document decisions and secure cross-team alignment.

Can I use this requirements discovery process for both product and engineering teams?▼

Yes, you can use this requirements discovery process across product, design, and engineering teams. It provides templates and prompts to capture goals, document edge cases, and confirm approval signals, ensuring alignment throughout the project lifecycle.

Why should I document edge cases before creating issues?▼

Documenting edge cases before creating issues prevents scope creep and misalignment by surfacing constraints early. This structured discovery process captures data needs and MVP boundaries upfront, reducing downstream development friction.

What do I need to start eliciting requirements for a project?▼

To start eliciting requirements, you need access to stakeholders for interviews and a feature concept to evaluate. The discovery process then guides you through outlining goals, listing data requirements, and documenting edge cases.