skills.rest
dangeles
dangelesCOMMUNITY
Explore all skills by this author →
Website𝕏@sciangelesGitHub

requirements-analyst

Guide requirements elicitation and stakeholder alignment with structured scope outputs.

6|Updated Feb 3, 2026
Search Tags:#planning#requirements#elicitation#MoSCoW#stakeholders#SMART
One-click install
npx skills add https://github.com/dangeles/claude --skill requirements-analyst-dangeles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-analyst
Source: https://github.com/dangeles/claude/tree/main/claude-config/skills/requirements-analyst
Command: npx skills add https://github.com/dangeles/claude --skill requirements-analyst-dangeles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Requirements often start vague or ambiguous, making it difficult to define clear scope and align stakeholders. This skill provides a structured elicitation process to uncover needs, constraints, and success criteria.

Core Features & Use Cases

  • Phase-driven elicitation to identify stakeholders, define scope, and articulate measurable success criteria.
  • Quick Mode for fast framing and Full Mode for comprehensive specification, analysis, and validation.
  • MoSCoW prioritization combined with SMART/Probabilistic criteria to guide prioritization and planning.

Quick Start

Launch the skill in Quick Mode to answer five core questions and generate a concise requirements outline that can be reviewed with stakeholders.

Frequently Asked Questions about requirements-analyst

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clarify vague project requirements with stakeholders?▼

Clarify vague project requirements by running a structured elicitation process that identifies stakeholders, defines IN SCOPE and OUT OF SCOPE boundaries, and establishes measurable success criteria to anchor project scope.

What is the MoSCoW method for prioritizing requirements?▼

The MoSCoW method for prioritizing requirements categorizes scope into Must-have, Should-have, Could-have, and Won't-have items, combined with SMART criteria to guide planning and stakeholder alignment.

How do I define measurable success criteria for ambiguous project scope?▼

Define measurable success criteria for ambiguous scope by applying SMART and Probabilistic criteria during elicitation, validating them against stakeholder expectations, and enforcing a formal approval workflow.

What's the best way to align multiple stakeholders on project scope quickly?▼

Align multiple stakeholders quickly by using Quick Mode to answer five core framing questions, generating a concise requirements outline that captures essential scope and success criteria for immediate review.

Can I use this requirements gathering process for comprehensive specification and validation?▼

Use Full Mode for comprehensive requirements gathering to perform thorough specification, MoSCoW prioritization, risk identification, and validation across multi-stakeholder scenarios with undefined success criteria.

What should be included in a structured requirements document to prevent scope creep?▼

A structured requirements document should include IN SCOPE and OUT OF SCOPE sections, SMART success criteria, identified risks, MoSCoW prioritization, and a clear approval workflow to prevent scope creep.

Related Skills

Explore More Product & Management Skills→
mikeparcewskimikeparcewski
8

requirements-analysis

Convert vague ideas into structured requirements and testable user stories.

Community
Advanced
johannesfritzjohannesfritz
1

prioritization-framework

Score backlog items using RICE, ICE, and MoSCoW frameworks.

Community
Basic
pwnk77pwnk77
59

Progress Tracker

Track task completion and generate automated project status reports.

Community
Intermediate
Nir-BhayNir-Bhay
19

backlog-refinement-guide

Guide backlog refinement sessions using the DEEP framework and Planning Poker.

Community
Intermediate