About

Imported from nickcrew/claude-cortex (skills/requirements-discovery/SKILL.md). Install upstream with npx skills add nickcrew/claude-cortex --skill requirements-discovery. Copyright stays with the author.

Requirements Discovery

Name: requirements-discovery
Author: nickcrew

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

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/nickcrew-claude-cortex-requirements-discovery/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

nickcrew-claude-cortex-requirements-discovery.ocm.jsonjson

{
  "ocm": "1",
  "id": "nickcrew-claude-cortex-requirements-discovery",
  "kind": "skill",
  "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.",
  "publisher": "nickcrew",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "gather-requirements",
      "stakeholder-interview",
      "requirements",
      "discovery",
      "requirements-discovery",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Stakeholder interviews, PRD structure, and scope definition for software requirements elicitation. Use when gathering requirements, defining project scope, or structuring product requirement documents."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/nickcrew/claude-cortex",
      "path": "skills/requirements-discovery/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/nickcrew/claude-cortex/blob/HEAD/skills/requirements-discovery/SKILL.md",
      "key": "nickcrew/claude-cortex/skills/requirements-discovery/SKILL.md"
    }
  },
  "instructions": "# Requirements Discovery\n\nSystematic requirements elicitation through structured questioning, stakeholder analysis, and specification development. Transforms ambiguous project ideas into concrete, measurable specifications.\n\n## When to Use This Skill\n\n- Gathering requirements for a new project or feature from vague descriptions\n- Conducting stakeholder interviews to uncover needs and constraints\n- Writing or structuring a Product Requirements Document (PRD)\n- Defining project scope with clear boundaries and priorities\n- Creating user stories with well-defined acceptance criteria\n- Identifying ",
  "cost": {
    "context_tokens": 657
  }
}

Fetch it by URL: GET /api/v1/registry/nickcrew-claude-cortex-requirements-discovery/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.