requirements-elicitation

Extract complete, unambiguous requirements from specifications by identifying functional/non-functional requirements and clarifying ambiguities

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026⬇️1downloads

When & Why to Use This Skill

The Requirements Elicitation skill for Claude is a specialized tool designed to bridge the gap between vague project ideas and technical execution. It systematically analyzes specifications to extract functional and non-functional requirements while proactively identifying ambiguities and constraints. By transforming high-level requests into clear, actionable documentation with testable acceptance criteria, it helps teams prevent scope creep and ensures alignment between stakeholders and developers.

Use Cases

  • 1. Feature Scoping and Specification: Transform brief user requests or 'napkin sketches' into comprehensive requirement documents that define exactly what needs to be built.
  • 2. Ambiguity Detection: Analyze existing project briefs to flag contradictory statements or missing information, generating targeted questions to clarify business needs.
  • 3. Technical Constraint Mapping: Identify hidden technical, resource, or business limitations within a proposal to improve project estimation and risk management.
  • 4. Backlog Refinement: Assist Product Owners in breaking down complex features into granular, unambiguous components with well-defined acceptance criteria.
name"Requirements Elicitation"
description"Extract complete, unambiguous requirements from specifications by identifying functional/non-functional requirements and clarifying ambiguities"
category"analysis"
required_tools["Read", "Write", "Grep"]

Requirements Elicitation

Purpose

Extract complete, unambiguous requirements from user specifications, identifying what needs to be built while clarifying unclear or missing information.

When to Use

  • Analyzing new feature requests
  • Processing enhancement specifications
  • Breaking down large features into components
  • Identifying missing information in requirements

Key Capabilities

  1. Extract Requirements - Identify functional and non-functional requirements
  2. Clarify Ambiguities - Flag unclear specifications and ask targeted questions
  3. Identify Constraints - Find technical, business, and resource limitations

Approach

  1. Read entire specification thoroughly
  2. Extract explicit requirements (stated clearly)
  3. Identify implicit requirements (assumed but not stated)
  4. Flag ambiguities and inconsistencies
  5. Document acceptance criteria for each requirement

Example

Context: Feature request to "add export functionality"

Approach:

  • What formats? (CSV, JSON, PDF?)
  • What data to export? (All fields or subset?)
  • Who can export? (All users or admins only?)
  • Size limits? (Max rows, file size?)
  • Output: Clear requirements with acceptance criteria

Best Practices

  • ✅ Ask "what" questions, not "how"
  • ✅ Document assumptions explicitly
  • ✅ Create testable acceptance criteria
  • ❌ Avoid: Making technical implementation decisions