requirements-discovery

Included with Lifetime

$97 forever

Stakeholder interviews, PRD structure, and scope definition for software requirements elicitation. Use when gathering requirements, defining project scope, or structuring product requirement documents.

General

What this skill does


# 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

Files: 2

Size: 13.2 KB

Complexity: 31/100

Category: General

Source: https://github.com/nickcrew/claude-cortex/tree/main/skills/requirements-discovery

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts