skills.rest
nexus-substrate
nexus-substrateOFFICIAL
Explore all skills by this author →
GitHub

requirements-gathering

Extract structured functional and non-functional requirements from vague user requests.

18|1|Updated Jan 3, 2026
Search Tags:#requirements#acceptance criteria#gap analysis#user stories#product discovery#capability mapping#scope planning
One-click install
npx skills add https://github.com/nexus-substrate/nexus-agents --skill requirements-gathering-nexus-substrate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-gathering
Source: https://github.com/nexus-substrate/nexus-agents/tree/main/skills/requirements-gathering
Command: npx skills add https://github.com/nexus-substrate/nexus-agents --skill requirements-gathering-nexus-substrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you convert ambiguous user requests into clear, structured requirements and user stories with acceptance criteria, reducing scope drift and downstream implementation churn.

Core Features & Use Cases

  • Functional and non-functional requirement extraction: Converts raw input into a structured set of requirements, constraints, and assumptions.
  • Capability mapping and gap identification: Benchmarks each requirement against available capabilities to flag what exists versus what must be added.
  • User-story specification with acceptance criteria: Produces actionable user stories (P1–P4) that can be used directly for planning and execution.

What it looks like in practice

When someone says “break down this feature and make it happen,” it turns that statement into prioritized user stories, measurable acceptance criteria, and a capability-to-gap matrix you can take into engineering.

Quick Start

Ask it to analyze your feature request for requirements, generate user stories with acceptance criteria, and map each requirement to existing nexus-agents capabilities while listing any gaps.

Frequently Asked Questions about requirements-gathering

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

FAQPage Schema
How do I turn vague feature requests into testable user stories?▼

Acceptance criteria for user stories are generated by extracting functional and non-functional requirements from your raw input, then formatting them into measurable conditions that validate each story's implementation readiness.

What is the best way to identify capability gaps during product discovery?▼

To map requirements to existing capabilities, you benchmark each extracted functional and non-functional specification against current system features, generating a matrix that explicitly reports gaps requiring new development.

How do I write functional and non-functional specifications from ambiguous project scopes?▼

You write functional and non-functional specifications from ambiguous scopes by parsing raw user intent to separate it into structured requirements, constraints, and assumptions that reduce scope drift and downstream churn.

Does this requirements gathering approach work for epic breakdown and scope planning?▼

Yes, this requirements gathering approach works for epic breakdown and scope planning by translating high-level user intent into implementation-ready, traceable specifications with explicit priority assignment and gap reporting.

Related Skills

Explore More Product & Management Skills→
OzeroHAXOzeroHAX
32

planning-requirements-extraction

Extract verifiable requirements and acceptance criteria from user requests.

Community
Basic
alex-tgkalex-tgk

agile-product-owner

Generate INVEST-compliant user stories with acceptance criteria from epics.

Community
Intermediate
Colten-CovingtonColten-Covington

product-planning

Define scope, requirements, and acceptance criteria for new features.

Community
Basic
product-on-purposeproduct-on-purpose
527

deliver-user-stories

Generate user stories and Given/When/Then acceptance criteria from product requirements.

Official
Basic