Requirements Gathering Skill

Analyze codebases and generate GitHub-ready requirements documents with acceptance criteria.

Updated Nov 5, 2025
One-click install
npx skills add https://github.com/igpastor/sng-claude-marketplace --skill requirements-gathering-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Requirements Gathering Skill
Source: https://github.com/igpastor/sng-claude-marketplace/tree/main/plugins/sngular-pm/skills/requirements-gathering
Command: npx skills add https://github.com/igpastor/sng-claude-marketplace --skill requirements-gathering-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill transforms vague ideas and high-level requests into structured, detailed, and actionable requirements documents. It saves significant time in the planning phase, reduces miscommunication, and ensures all stakeholders are aligned before development begins.

Core Features & Use Cases

  • Intelligent Elicitation: Asks clarifying questions to uncover functional, non-functional, and technical requirements, constraints, and dependencies.
  • Contextual Analysis: Reviews existing codebase patterns and related documentation to ensure consistency and identify affected components.
  • Structured Documentation: Organizes requirements into clear categories, defines acceptance criteria, prioritizes with MoSCoW, and generates user stories.
  • GitHub-Ready Output: Produces structured markdown documents, including technical specifications and implementation estimates, suitable for direct use in GitHub issues.
  • Use Case: Provide a high-level feature idea like "We need better search," and the skill will ask clarifying questions, analyze the existing codebase, and generate a comprehensive requirements document with user stories and technical specifications.

Quick Start

Gather requirements for a new 'user authentication' feature.

Frequently Asked Questions about Requirements Gathering Skill

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

FAQPage Schema
How do I turn vague feature ideas into structured requirements documents?

Requirements gathering transforms high-level ideas into detailed, actionable specifications by asking clarifying questions, analyzing existing codebase patterns, and organizing findings into functional and non-functional categories with acceptance criteria and user stories ready for GitHub.

What questions should I ask when gathering requirements for a new feature?

Effective requirement elicitation uncovers scope, constraints, and dependencies by asking about functional needs, non-functional requirements like performance or security, affected components, and implementation priorities using MoSCoW prioritization to distinguish must-haves from nice-to-haves.

How do I document requirements in a format GitHub-ready for issues and project planning?

Requirements documentation structures findings into markdown with user stories, acceptance criteria, technical specifications, and implementation estimates that can be directly pasted into GitHub issues, ensuring developers and stakeholders share a common understanding before work begins.

Can I analyze my existing codebase to ensure new requirements align with current patterns?

Contextual analysis reviews existing codebase patterns and related documentation to ensure consistency, identify affected components, and surface dependencies that inform requirement scope and technical constraints.

What's the best way to prioritize requirements when planning product features?

MoSCoW prioritization categorizes requirements as Must-have, Should-have, Could-have, or Won't-have, helping teams focus development effort on critical functionality first and communicate trade-offs to stakeholders transparently.