requirements-gathering

Convert vague user requests into structured requirements with capability mappings.

18|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/williamzujkowski/nexus-agents --skill requirements-gathering-williamzujkowski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirements-gathering
Source: https://github.com/williamzujkowski/nexus-agents/tree/main/skills/requirements-gathering
Command: npx skills add https://github.com/williamzujkowski/nexus-agents --skill requirements-gathering-williamzujkowski

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users convert vague or ambiguous input into clear, structured requirements for development and planning.

Core Features & Use Cases

  • Requirement Extraction: Analyzes user requests and decomposes them into functional, non-functional, and constraint requirements.
  • Mapping Capabilities: Cross-references requirements with existing nexus-agents capabilities to identify gaps.
  • User Story Generation: Produces detailed user stories with acceptance criteria and priorities.
  • Planning and Decomposition: Suggests implementation phases, dependency graphs, and handles divergent and convergent thinking for ambiguous ideas.
  • Use Case: A product manager wants to scope a new feature with developers; this Skill converts the initial vague request into a clear, prioritized set of actionable stories and constraints.

Quick Start

Provide a vague feature request and receive a detailed requirements document including user stories and capability mappings.

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 structured user stories?

To turn vague feature requests into structured user stories, the Skill decomposes input into functional, non-functional, and constraint requirements. It then generates detailed user stories complete with acceptance criteria and priorities for clear planning.

What is the best way to analyze feature scope and map it to existing capabilities?

Analyzing feature scope and mapping it to existing capabilities involves cross-referencing extracted requirements against current system functions to identify gaps. This ensures that new feature planning accurately highlights missing functionality and development needs.

How do I break down ambiguous product ideas into implementation phases and dependency graphs?

Breaking down ambiguous product ideas into implementation phases and dependency graphs requires divergent and convergent thinking. The Skill processes ambiguous input to suggest structured implementation phases and visual dependency graphs for development.

Can I use this requirements analysis tool for process improvement planning as well as feature development?

Yes, you can use this requirements analysis tool for process improvement planning as well as feature development. It converts ambiguous input into detailed, structured requirements suitable for planning both development tasks and process enhancements.

What limitations exist when mapping requirements to existing capabilities?

A limitation when mapping requirements to existing capabilities is that the accuracy depends on the clarity of the initial vague request. While the Skill identifies gaps and constraints, highly undefined inputs may still require manual refinement for precise capability mapping.