skills.rest
njt
njtCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gathering-requirements

Elicit software requirements through Socratic questioning and document analysis.

11|Updated Feb 8, 2026
Search Tags:#documentation#project planning#socratic method#requirements gathering#elicitation#stakeholder interview
One-click install
npx skills add https://github.com/njt/reqskill --skill gathering-requirements-njt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gathering-requirements
Source: https://github.com/njt/reqskill/tree/main/skills/gathering-requirements
Command: npx skills add https://github.com/njt/reqskill --skill gathering-requirements-njt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill helps you build a comprehensive requirements.md file from scratch by interactively questioning stakeholders and analyzing existing documentation.

Core Features & Use Cases

  • Socratic Elicitation: Guides users through a structured questioning process to uncover needs.
  • Document Analysis: Extracts implicit requirements from provided documents (code, wikis, etc.).
  • Use Case: When starting a new software project, use this Skill to systematically define what the system should do, its constraints, and its non-goals, ensuring a solid foundation before development begins.

Quick Start

Use the gathering-requirements skill to start building requirements.md for a new project.

Frequently Asked Questions about gathering-requirements

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

FAQPage Schema
How do I elicit software requirements from stakeholders for a new project?▼

Elicit software requirements through interactive Socratic questioning and analysis of existing documentation to uncover implicit needs and systematically define system behavior, constraints, and non-goals.

What is the Socratic method for requirements gathering?▼

The Socratic method for requirements gathering uses structured, iterative dialogue to guide stakeholders through targeted questions, systematically uncovering implicit needs and fleshing out incomplete project specifications.

How do I extract implicit requirements from existing project documentation?▼

Extract implicit requirements by analyzing provided documents like code and wikis, identifying existing system behaviors and constraints, and structuring them into a formal requirements specification.

Can I use this requirements gathering process to flesh out incomplete project specifications?▼

Yes, you can use this interactive requirements gathering process to flesh out incomplete specifications by engaging in iterative dialogue that uncovers missing needs and refines existing project definitions.

What is the best way to start building a requirements.md file from scratch?▼

The best way to build a requirements.md file from scratch is through structured Socratic elicitation and document analysis, drafting formal requirements iteratively before development begins.

Do I need existing documentation to start the requirements elicitation process?▼

No, you do not need existing documentation to start elicitation; the process uses Socratic questioning to build a formal requirements.md file from scratch, though analyzing existing docs can extract implicit needs.

Related Skills

Explore More Product & Management Skills→
xoaixoai
25

ux-discovery

Analyze codebase scans and documentation to produce user-context-notes, persona-profiles, and journey-maps.

Community
Advanced
knowz-ioknowz-io
1

knowzcode-explore

Analyze project architecture and patterns to generate implementation roadmaps.

Official
Advanced
datorresbdatorresb

ce-plan

Convert raw feature descriptions into structured planning documents for issue tracking.

Community
Advanced
jbalcombjbalcomb
26

write-a-prd

Creates a GitHub-issue-ready PRD from interviews, codebase analysis, and module design.

Community
Advanced