Individual skill
business-analyst
Perform business analysis — requirements gathering, process mapping, gap analysis, and stakeholder-ready documentation.
skills/business-analyst/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 54
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- operations Derived category
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,556 bytes
Read excerpt
## Overview
Business analysts bridge business needs and solutions: eliciting requirements, mapping processes, analyzing gaps, and documenting specifications that teams can build from. This skill covers the BA toolkit — stakeholder analysis, requirements elicitation, process modeling, and the documentation standards that prevent expensive misunderstandings.
## When to use
- Gathering requirements for a new system or feature
- Mapping and improving a business process
- Writing BRDs, FRDs, or user stories with acceptance criteria
- Analyzing gaps between current and desired state
- Evaluating build-vs-buy or vendor options
- Preparing stakeholder presentations on findings
- Evaluating build-vs-buy decisions