ba-requirements-analysis

Model and specify requirements with use cases, user stories, INVEST, and MoSCoW prioritization.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/NestorMonroy/thyrox --skill ba-requirements-analysis-nestormonroy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ba-requirements-analysis
Source: https://github.com/NestorMonroy/thyrox/tree/main/.claude/skills/ba-requirements-analysis
Command: npx skills add https://github.com/NestorMonroy/thyrox --skill ba-requirements-analysis-nestormonroy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Business needs gathered during elicitation often remain vague and unverifiable, leading teams to build the wrong solution. This Skill converts articulated stakeholder needs into formally specified, verified, and validated requirements following the BABOK v3 Requirements Analysis & Design Definition knowledge area. ## Core Features & Use Cases - Requirements Modeling: Build Use Case Models with main, alternative, and exception flows, or write User Stories with Given/When/Then acceptance criteria. - Quality Verification & Validation: Apply the INVEST criteria to user stories, run a six-criterion verification checklist (completeness, consistency, non-ambiguity, verifiability, feasibility, traceability), and validate requirements with stakeholders. - Prioritization & Design Options: Classify requirements with MoSCoW (enforcing the ≤60% Must Have rule) and document high-level design options with pros, cons, and constraints. - Use Case: After a strategy analysis identifies capability gaps, use this Skill to produce a ba-requirements-analysis.md artifact containing UC-001 use cases, prioritized user stories, and stakeholder sign-off records. ## Quick Start Ask the AI to model the requirements for your project using use cases and user stories, verify them against INVEST, and prioritize them with MoSCoW into a requirements analysis document.

Frequently Asked Questions about ba-requirements-analysis

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

FAQPage Schema
How do I write user stories with acceptance criteria?▼

Write the story as 'As a [role], I want [capability], so that [benefit]', then add acceptance criteria in Given/When/Then format covering the normal case, alternatives, and error handling. Verify each story against the six INVEST criteria before accepting it.

What is the difference between requirement verification and validation in BABOK?▼

Verification checks whether a requirement is well written: complete, consistent, unambiguous, verifiable, feasible, and traceable. Validation confirms with business stakeholders that the requirement actually addresses their real need, using prototypes, UAT, or walkthroughs.

When should I use a decision table versus a decision tree?▼

Use a decision table when multiple conditions combine simultaneously to determine actions, since it covers all 2^n combinations. Use a decision tree when conditions are evaluated sequentially and stakeholders need to visualize the decision flow.

How does MoSCoW prioritization work for requirements?▼

Classify each requirement as Must Have, Should Have, Could Have, or Won't Have with stakeholders. Must Have items should stay at or below 60% of the total; exceeding that threshold signals the scope is too large or prioritization is not genuine.

When should I not use requirements analysis?▼

Skip this step if business needs are not yet articulated, since elicitation or strategy analysis must come first. It is also the wrong step for managing already-specified requirements, which belongs to requirements life cycle management.