Business Analysis Skills

Guides business analysts in writing requirements, user stories, use cases, and BRD/SRS documents.

Updated May 12, 2026
One-click install
npx skills add https://github.com/ZzZueszZ/claude-kit --skill business-analysis-skills-zzzueszz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Business Analysis Skills
Source: https://github.com/ZzZueszZ/claude-kit/tree/main/.claude/skills/business-analysis
Command: npx skills add https://github.com/ZzZueszZ/claude-kit --skill business-analysis-skills-zzzueszz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Business analysts often produce vague requirements, incomplete user stories, and inconsistent documentation that lead to rework during development. This Skill enforces mandatory rules and proven formats for requirements elicitation, user stories, use cases, BRD/SRS documents, BPMN process models, data dictionaries, and acceptance testing. ## Core Features & Use Cases - Requirements Elicitation: Distinguishes functional vs non-functional requirements, defines scope, stakeholders, and acceptance criteria with clear good/bad examples. - User Stories & Use Cases: Enforces INVEST-compliant stories with Given-When-Then acceptance criteria and full use case flows (main, alternative, exception). - Documentation Standards: Provides BRD and SRS (IEEE 830) structures, BPMN 2.0 process modeling rules, data dictionary conventions, and UAT test case templates. - Use Case: A BA documenting a notification label module can follow the included end-to-end example covering user stories, display configuration use cases, auto-labeling rules with JSON condition structures, and process flows. ## Quick Start Ask the assistant to act as a business analyst and write INVEST-compliant user stories with acceptance criteria for your feature.

Frequently Asked Questions about Business Analysis Skills

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

FAQPage Schema
How do I write a good user story with acceptance criteria?▼

Use the format 'As a [role], I want [goal], so that [benefit]' and ensure the story follows INVEST principles: Independent, Negotiable, Valuable, Estimable, Small, Testable. Write acceptance criteria in Given-When-Then format and include edge cases.

What is the difference between a BRD and an SRS document?▼

A BRD describes the business problem and objectives without technical solutions, covering scope, stakeholders, and business rules. An SRS, based on IEEE 830, details the technical system to be built, including interfaces, functional requirements, and data requirements.

How do I write a complete use case description?▼

A complete use case includes Actor, Precondition, numbered Main Flow steps, Alternative Flows referencing main flow steps, Exception Flows, and Postcondition. Every branch must have a clear condition so no flow remains ambiguous.

What should a data dictionary include for business analysis?▼

Each entity needs a business description, fields with types and business rules, and relationships with explicit cardinality. Field names should reflect business meaning rather than abbreviations, and related business rules must be documented.

How do I create test cases from acceptance criteria?▼

Each test case needs an ID, description, precondition, steps, expected result, and priority. Cover both happy paths and edge cases, and use a traceability matrix to map requirements to user stories to test cases.