business-analyst

Gather business requirements by conducting stakeholder interviews and facilitated workshops, then documenting findings in a Business Requirements Document. This Skill structures the elicitation process and translates needs into functional specifications and user stories.

Write user stories in the format of role, goal, and benefit, then attach testable acceptance criteria defining done conditions. This Skill generates both artifacts and validates them against the underlying business requirements.

A BRD captures high-level business objectives and stakeholder needs, while a functional specification translates those needs into detailed system behavior for developers. This Skill produces both document types as standard deliverables.

BPMN suits business process flows shared with non-technical stakeholders, while UML fits system-oriented modeling like use cases and interactions. This Skill supports both notations depending on the audience and analysis goal.

Avoid it for pure implementation tasks like writing code, debugging, or infrastructure setup, where engineering-focused skills fit better. It adds value when requirements are ambiguous or business and technical teams need alignment.