requirements-discovery — Claude Code skill: requirements
The requirements-discovery Claude Code skill gathers requirements, sets project boundaries, and structures PRDs. It activates for feature discovery, stakeholder interviews, or specification reviews.
MIT 101 installs ★ 71 updated 2026-06-29
npx skills add NickCrew/Claude-Cortex --skill requirements-discovery -a claude-codeWhat requirements-discovery does
The skill turns an unclear project idea into structured requirements. It helps identify stakeholders and constraints, prepare interview questions, draft a PRD, and write user stories with acceptance criteria.
Its workflow moves from discovery to specification and validation before implementation. Requirements are refined in stages, and prioritisation can use MoSCoW. Scope boundaries include explicit exclusions.
Validation checks whether acceptance criteria are measurable and testable, while tracking success metrics and open questions. Interview techniques, PRD structure, and story mapping are covered in skills/requirements-discovery/references/elicitation-techniques.md.
What it helps with
- turn a vague feature idea into concrete requirements
- prepare questions for stakeholder interviews
- draft a PRD with functional and non-functional requirements
- set project boundaries and prioritise requirements
- check acceptance criteria before implementation
Example prompts for the agent
- Gather requirements for this feature and prepare stakeholder interview questions.
- Turn these notes into a PRD with acceptance criteria and project boundaries.
- Review the specification for open questions and criteria that cannot be tested.
How to install requirements-discovery
1Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill requirements-discovery -a claude-code2Manually: put the files in place
~/.claude/skills/requirements-discovery/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/requirements-discovery/
1Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill requirements-discovery -a codex2Manually: put the files in place
.agents/skills/requirements-discovery/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill requirements-discovery -a cursor2Manually: put the files in place
.cursor/skills/requirements-discovery/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install NickCrew/Claude-Cortex skills/requirements-discovery2Manually: put the files in place
.github/skills/requirements-discovery/SKILL.md1Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill requirements-discovery -a gemini-cli2Platform CLI
gemini skills install https://github.com/NickCrew/Claude-Cortex --path skills/requirements-discoveryManually: put the files in place
.devin/skills/requirements-discovery/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add NickCrew/Claude-Cortex --skill requirements-discovery -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about requirements-discovery
How do I install requirements-discovery in Claude Code?
Run npx skills add NickCrew/Claude-Cortex --skill requirements-discovery -a claude-code. The skill file is at ~/.claude/skills/requirements-discovery/SKILL.md.
What does requirements-discovery do?
It helps elicit needs and constraints, organise them into a PRD and user stories, then validate the specification before implementation.
What stages does requirements-discovery cover?
It supports discovery, specification, and validation: identifying stakeholders, drafting requirements, and checking completeness. MoSCoW is one prioritisation option.
Source text
SKILL.md · MIT
--- name: requirements-discovery description: Stakeholder interviews, PRD structure, and scope definition for software requirements elicitation. Use when gathering requirements, defining project scope, or structuring product requirement documents. keywords: - gather requirements - stakeholder interview - requirements - discovery - requirements discovery --- # 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
© NickCrew · MIT · NickCrew/Claude-Cortex