requirements-discovery
Stakeholder interviews, PRD structure, and scope definition for software requirements elicitation. Use when gathering requirements, defining project scope, or structuring product requirement documents.
Best use case
requirements-discovery is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Stakeholder interviews, PRD structure, and scope definition for software requirements elicitation. Use when gathering requirements, defining project scope, or structuring product requirement documents.
Teams using requirements-discovery should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/requirements-discovery/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How requirements-discovery Compares
| Feature / Agent | requirements-discovery | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Stakeholder interviews, PRD structure, and scope definition for software requirements elicitation. Use when gathering requirements, defining project scope, or structuring product requirement documents.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Requirements Discovery Systematic requirements elicitation through structured questioning, stakeholder analysis, and specification development. Transforms ambiguous project ideas into concrete, measurable specifications. ## When to Use This Skill - Gathering requirements for a new project or feature from vague descriptions - Conducting stakeholder interviews to uncover needs and constraints - Writing or structuring a Product Requirements Document (PRD) - Defining project scope with clear boundaries and priorities - Creating user stories with well-defined acceptance criteria - Identifying non-functional requirements (performance, security, scalability) - Resolving conflicting stakeholder priorities - Validating requirement completeness before handing off to implementation ## Quick Reference | Task | Load reference | | --- | --- | | Interview patterns, PRD structure, scope definition, user story mapping | `skills/requirements-discovery/references/elicitation-techniques.md` | ## Core Principles - **Ask "why" before "how"**: Uncover true user needs, not assumed solutions - **Socratic questioning**: Guide discovery through questions rather than assumptions - **Progressive refinement**: Move from broad goals to specific, testable criteria - **Stakeholder balance**: Integrate diverse perspectives without letting any single voice dominate ## Workflow ### 1. Discovery Understand the problem space before defining solutions. - Identify all stakeholders and their roles - Conduct structured interviews with open and closed questions - Map user personas and their pain points - Capture constraints (technical, budget, timeline, regulatory) ### 2. Specification Transform raw input into structured requirements. - Draft PRD with functional and non-functional requirements - Write user stories with acceptance criteria - Prioritize using MoSCoW or similar framework - Define scope boundaries (what is explicitly out of scope) ### 3. Validation Verify completeness and alignment before implementation. - Review specifications with stakeholders - Confirm acceptance criteria are testable and measurable - Baseline success metrics and KPIs - Log open questions and follow-up actions - Prepare implementation handoff document ## Common Mistakes - Jumping to solutions before understanding the problem - Treating requirements as fixed rather than iteratively refined - Missing non-functional requirements (performance, security, accessibility) - Failing to define what is out of scope - Writing acceptance criteria that cannot be objectively tested - Skipping validation with actual users or stakeholders
Related Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization
workflow-security-audit
Comprehensive security assessment and remediation. Use for security reviews, compliance checks, vulnerability assessments.
workflow-performance
Systematic performance analysis and optimization. Use when things are slow, need optimization, or preparing for scale.
workflow-feature
Complete feature development workflow from design to deployment. Use when implementing new features or functionality.
workflow-feature-development
Complete workflow for developing new features from design to deployment. Use when starting a new feature, adding functionality, or building something new.
workflow-bug-fix
Systematic approach to identifying, fixing, and validating bug fixes. Use when fixing bugs, resolving issues, or addressing errors.
wiring-audit
User-triggered audit that finds wiring drift between a project's UI surfaces and backend capabilities — orphan surfaces (UI calls endpoints/hooks/procedures that no longer exist), unwired capabilities (backend routes/exports that nothing surfaces), shape drift (both exist but contracts mismatch), method drift (URL matches, HTTP verb does not), validation drift (frontend vs backend rules diverged), permission drift (UI exposes what backend forbids or vice versa), stale labels (UI text references renamed backend concepts), and unsurfaced configuration (env vars or flags that gate behavior with no UI or CLI to control them). This skill should be used when the user asks to "audit our wiring," "find UI/backend drift," "find unwired capabilities," "find stale surfaces," "check for contract violations," "find unused endpoints," "find unused hooks," "what mismatches between UI and backend," or any similar request whose deliverable is a prioritized findings report rather than a descriptive snapshot. Generic across UI frameworks but optimized for React applications (hooks, fetch, react-query, SWR, tRPC, server actions, react-router, Next.js). Not for descriptive architectural snapshots (use architectural-analysis), security audits (use security-auditor), or performance audits (use workflow-performance).
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Use when verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
web-researcher
Use this skill when you need to research a topic online, gather information from multiple sources, or evaluate source credibility. Trigger phrases: 'research', 'find information about', 'look up', 'investigate'. Not for academic systematic reviews (use literature-reviewer) or fact-checking specific claims (use fact-checker).
visual-modes
Use when activating visual showcase modes (supersaiyan, kamehameha, over9000) for UI or interaction design - provides mode-specific enhancement checklists.
vibe-security
Comprehensive secure coding guide covering OWASP web vulnerabilities with prevention patterns and checklists. Use when writing or reviewing web application code to prevent XSS, CSRF, SSRF, SQL injection, access control flaws, and other common security vulnerabilities.
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always