requirements-discovery
A structured approach to eliciting, defining, and refining project requirements and product specifications.
Install
mkdir -p .claude/skills/requirements-discovery && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11714" && unzip -o skill.zip -d .claude/skills/requirements-discovery && rm skill.zipInstalls to .claude/skills/requirements-discovery
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Stakeholder interviews, PRD structure, and scope definition for software requirements elicitation. Use when gathering requirements, defining project scope, or structuring product requirement documents.Key capabilities
- →Conduct structured interviews with stakeholders
- →Map user personas and their pain points
- →Draft Product Requirements Documents (PRD) with functional and non-functional requirements
- →Write user stories with acceptance criteria
- →Define project scope boundaries and priorities
- →Validate requirement completeness with stakeholders
How it works
The skill guides through discovery, specification, and validation phases. It involves identifying stakeholders, conducting interviews, drafting PRDs, writing user stories, and validating requirements.
Inputs & outputs
When to use requirements-discovery
- →Gather project requirements
- →Write a PRD
- →Define project scope
- →Create user stories
About this skill
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
When not to use it
- →When jumping directly to solutions without understanding the problem
- →When treating requirements as fixed rather than iteratively refined
- →When skipping validation with actual users or stakeholders
Limitations
- →Requires uncovering true user needs, not assumed solutions
- →Requires integrating diverse perspectives without any single voice dominating
- →Requires defining what is explicitly out of scope
How it compares
This skill provides a systematic, structured approach to requirements elicitation through Socratic questioning and progressive refinement, transforming ambiguous ideas into concrete specifications unlike an ad-hoc process.
Compared to similar skills
requirements-discovery side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| requirements-discovery (this skill) | 0 | 3mo | No flags | Intermediate |
| pmbok-project-management | 38 | 9mo | No flags | Intermediate |
| project-planner | 32 | 9mo | Review | Intermediate |
| spec-kit-workflow | 11 | 8mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by NickCrew
View all by NickCrew →You might also like
pmbok-project-management
jgtolentino
Comprehensive PMP/PMBOK project management methodologies and best practices. Use this skill when users need guidance on project management processes, templates, knowledge areas, process groups, tools, techniques, or certification preparation. Covers all 10 PMBOK Knowledge Areas and 5 Process Groups with practical templates, frameworks, and industry-standard approaches. Includes risk management, stakeholder engagement, schedule management, cost control, quality assurance, and resource planning.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
planning-agent
parcadei
Planning agent that creates implementation plans and handoffs from conversation context
pdd
mikeyobrien
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.