mcpField
R
requirements-discovery

requirements-discovery

github.com/nickcrewDevelopment6295 installsUpdated 17w ago
Repository

About requirements-discovery

requirements-discovery is a skill for product teams and stakeholders to turn vague ideas into testable requirements. It structures discovery, specification, and validation, including stakeholder needs, scope, and acceptance criteria.

Key features

  1. 01Structured stakeholder interviews
  2. 02PRD and user story drafting
  3. 03Functional and non-functional requirements
  4. 04Scope and priority definition
  5. 05Testable acceptance criteria
  6. 06Specification validation and handoff

Use cases

  1. 01Clarifying requirements for a new project
  2. 02Reconciling competing stakeholder needs
  3. 03Preparing a PRD and user stories
  4. 04Checking specifications before implementation

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nickcrew/claude-cortex --skill requirements-discovery

After installing, type/requirements-discoveryin Claude Code to confirm it loaded.

Bundled filesreferences/elicitation-techniques.md

Details

From the project README

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

TaskLoad reference
Interview patterns, PRD structure, scope definition, user story mappingskills/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

Comments

Markdown supported