requirements-gathering

Interrogates ambiguous requests into scoped specifications with measurable requirements and evidence citations.

4|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/douglance/sdlc-plugin --skill requirements-gathering-douglance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-gathering
Source: https://github.com/douglance/sdlc-plugin/tree/main/.rulesync/skills/requirements-gathering
Command: npx skills add https://github.com/douglance/sdlc-plugin --skill requirements-gathering-douglance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ambiguous, high-blast-radius, or hard-to-reverse requests often hide missing product decisions. This Skill stress-tests requirements through relentless one-at-a-time questioning, codebase exploration, and falsification until the work is unambiguous, producing a scoped specification instead of guesswork. ## Core Features & Use Cases - Requirement Falsification: Probes reversibility, edge cases, scale, security, and internal contradictions to break weak requirements before they reach design. - Evidence-Backed Specification: Produces functional and nonfunctional requirements with stable IDs, measurable quality-of-service targets, and an evidence ledger citing exact path:line references. - Unresolved Decision Surfacing: Answers what it can from the codebase and returns the rest as questions with recommended answers for the main thread to resolve. - Use Case: A stakeholder asks to "add real-time collaboration." The Skill interrogates scope, latency targets, and conflict-resolution behavior, cites prior art in the repository, and delivers a draft spec with REQ IDs plus a short list of material open decisions. ## Quick Start Ask the agent to run requirements-gathering on your feature request and return a scoped specification with measurable requirements and unresolved questions.

Frequently Asked Questions about requirements-gathering

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

FAQPage Schema
How do I turn a vague feature request into a specification?▼

Run requirements-gathering on the request. It interrogates the requirement one question at a time, answers what it can from the codebase, and produces a draft spec with scoped functional and nonfunctional requirements, each carrying a stable ID and measurable targets.

How to write measurable nonfunctional requirements?▼

Pin quality-of-service targets such as latency, throughput, availability, and security as concrete numbers rather than adjectives. The Skill separates functional from nonfunctional requirements and makes each target measurable so design, tasks, and tests can trace back to it.

When should I use requirements-gathering versus going straight to design?▼

Use it when a request is ambiguous, high-blast-radius, difficult to reverse, or missing a material product decision. If the work is already unambiguous and low-risk, you can skip this phase and proceed directly to planning or design.

Does requirements-gathering require access to the codebase?▼

Yes, it explores the repository to answer questions itself and cites exact path:line references for every claim about current behavior, conventions, or feasibility. Unsupported assumptions are moved to open questions rather than stated as facts.

What happens to questions the requirements process cannot answer?▼

Each unresolved question is returned to the main thread with a recommended answer. The main thread resolves them or escalates to the user, keeping the specification free of unsupported assumptions.