spec-gather-requirements

Gather and structure user requirements into categorized JSON files.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/GDSDN/kord-aios --skill spec-gather-requirements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-gather-requirements
Source: https://github.com/GDSDN/kord-aios/tree/main/src/features/builtin-skills/kord-aios/analysis/spec-gather-requirements
Command: npx skills add https://github.com/GDSDN/kord-aios --skill spec-gather-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of collecting and organizing user requirements, transforming informal descriptions into structured, categorized requirements.

Core Features & Use Cases

  • Interactive Elicitation: Engages users with targeted questions to gather detailed requirements.
  • Source Flexibility: Supports gathering requirements from Product Requirement Documents (PRDs), direct user input, or existing specifications.
  • Structured Output: Generates a requirements.json file adhering to a defined schema, suitable for further development stages.
  • Use Case: A product manager needs to define the features for a new user authentication system. This Skill guides them through a series of questions to capture functional needs, constraints, non-functional aspects, and user interactions, producing a clear requirements document.

Quick Start

Use the gather-requirements skill to start gathering requirements for story-id 'STORY-123'.

Frequently Asked Questions about spec-gather-requirements

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

FAQPage Schema
How do I gather user requirements from a PRD and turn them into structured JSON?

To gather user requirements from a PRD, this Skill analyzes the document and transforms informal descriptions into structured, categorized requirements, outputting a formal requirements.json file suitable for software development.

What is the best way to elicit product requirements for user stories?

The best way to elicit product requirements for user stories is through interactive elicitation, where targeted questions capture functional needs, constraints, non-functional aspects, and user interactions to produce a clear requirements document.

Can I use existing specifications as input for requirements gathering?

Yes, you can use existing specifications as input for requirements gathering. This Skill supports multiple input sources including PRDs, direct user input, and existing specs to structure your final requirements.

How do I categorize non-functional requirements and constraints during elicitation?

To categorize non-functional requirements and constraints during elicitation, the Skill guides you through interactive questions that capture and structure these specific aspects alongside functional needs and user interactions.

What format does the structured requirements output use?

The structured requirements output uses a JSON format. The Skill generates a requirements.json file adhering to a defined schema, ensuring the categorized requirements are ready for downstream development stages.