ba

Business analysis transforms noisy multi-channel input into structured artifacts like user stories, use cases, and RACI matrices. This Skill systematizes requirements elicitation, enforces INVEST-aligned story creation, and applies MoSCoW prioritization to map stakeholder needs into actionable specifications.

A RACI matrix clarifies role accountability across activities by assigning Responsible, Accountable, Consulted, and Informed roles. Use it when launching feature development to eliminate ambiguity, prevent gaps in ownership, and ensure stakeholders know their decision rights.

INVEST-compliant user stories pair narrative context with specific, testable acceptance criteria. This Skill generates stories that follow the framework—independent, negotiable, valuable, estimable, small, testable—so engineers and product teams share a common understanding of what done means.

Yes. Business analysis systematically processes high-volume, multi-channel input by extracting key stakeholders, identifying requirements patterns, and consolidating them into structured artifacts like glossaries, risk registers, and scope documents that scale across complex teams.

User stories capture what a user wants and why; use cases detail the step-by-step interaction flow between actors and the system. This Skill generates both formats so teams can map user intent to technical workflows and acceptance criteria comprehensively.

No. Business analysis bridges domain expertise and technical delivery by capturing stakeholder needs in structured formats without requiring coding knowledge. The Skill handles elicitation, prioritization, and artifact generation so business and technical teams align on vision, scope, and requirements.