business-analyst

Name: business-analyst
Availability: InStock
Author: belokonm

Document stakeholder requirements as user stories and acceptance criteria with BPMN models.

8|11|Updated Feb 15, 2026

Search Tags:#requirements #bpmn #user-stories #business-analysis #acceptance-criteria #stakeholders #functional-spec

Ready to run

npx skills add https://github.com/belokonm/claude-supercode-skills --skill business-analyst-belokonm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: business-analyst
Source: https://github.com/belokonm/claude-supercode-skills/tree/main/business-analyst-skill
Command: npx skills add https://github.com/belokonm/claude-supercode-skills --skill business-analyst-belokonm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridges the gap between stakeholder needs and technical specifications by turning ambiguous requests into clear requirements, user stories, and process models.

Core Features & Use Cases

Requirements capture and analysis: gather, validate, and document stakeholder needs, constraints, and success metrics.
Modeling and documentation: produce BPMN models, AS-IS/TO-BE diagrams, and functional specs that align business and tech teams.
Acceptance criteria and traceability: generate testable acceptance criteria and maintain requirements traceability across the project lifecycle.

Quick Start

Gather requirements from stakeholders and translate them into user stories and acceptance criteria using a structured template.

Frequently Asked Questions about business-analyst

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

FAQPage Schema

How do I translate stakeholder requirements into clear user stories and acceptance criteria?▼

To translate stakeholder requirements, you gather and validate the initial needs, then apply structured business analysis methods to produce well-formed user stories and testable acceptance criteria that align business and technical teams.

What is the best way to document AS-IS and TO-BE process models for business analysis?▼

Documenting AS-IS and TO-BE process models involves applying BPMN modeling techniques to current workflows and proposed improvements, resulting in functional specifications that bridge the gap between stakeholder requests and technical execution.

How do I maintain requirements traceability across a project lifecycle?▼

Maintaining requirements traceability requires generating testable acceptance criteria linked to original stakeholder needs and continuously mapping these requirements through the project phases to ensure alignment and documentation standards.

Can I use BPMN modeling for functional specification generation from ambiguous requests?▼

Yes, applying BPMN modeling to ambiguous stakeholder requests allows you to visually structure the workflows, which helps clarify constraints and produce structured functional specifications for development teams.

Why does my project need structured business analysis for stakeholder communication?▼

Structured business analysis is needed because it transforms ambiguous requests into clear requirements and process models, ensuring that technical outputs satisfy stakeholder needs and maintain clear communication with development teams.

Does this approach support generating success metrics and validation for user stories?▼

Yes, the requirements capture process includes gathering and validating stakeholder needs, constraints, and success metrics, which are then directly translated into the acceptance criteria for your user stories.