What problem does it solve? Business analysts often struggle to convert articulated stakeholder needs into well-specified, verifiable requirements. This Skill guides the BABOK v3 Requirements Analysis & Design Definition knowledge area, turning elicited needs into use case models, user stories, and validated design options. ## Core Features & Use Cases - Requirements Modeling: Build detailed use cases (actors, triggers, main/alternative/exception flows) and user stories with Given/When/Then acceptance criteria. - Quality Verification & Validation: Apply INVEST criteria to user stories and a six-criterion checklist (completeness, consistency, non-ambiguity, verifiability, feasibility, traceability) to every requirement. - 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 completing stakeholder elicitation for a credit approval system, use this Skill to produce a requirements specification with UC models, INVEST-checked user stories, MoSCoW priorities, and a routing decision to the next BABOK knowledge area. ## Quick Start Ask the assistant to run the ba-requirements-analysis step to model and specify the requirements from your elicitation notes into use cases and prioritized user stories.
