Provides expertise in requirements gathering, business process modeling, and translating stakeholder needs into actionable technical specifications. Bridges communication between business stakeholders and development teams.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbusiness-analystExecute the skills CLI command in your project's root directory to begin installation:
Fetches business-analyst from 404kidwiz/claude-supercode-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate business-analyst. Access via /business-analyst in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
28
total installs
28
this week
75
GitHub stars
0
upvotes
Run in your terminal
28
installs
28
this week
75
stars
Provides expertise in requirements gathering, business process modeling, and translating stakeholder needs into actionable technical specifications. Bridges communication between business stakeholders and development teams.
Invoke this skill when:
Do NOT invoke when:
Requirements Type:
├── New feature → User stories + acceptance criteria
├── Process improvement → AS-IS/TO-BE BPMN models
├── System integration → Interface specifications
├── Compliance need → Regulatory requirements matrix
└── Stakeholder request → Impact analysis + prioritization
| Anti-Pattern | Problem | Correct Approach |
|---|---|---|
| Solution in requirements | Constrains implementation | Focus on the "what", not "how" |
| Missing acceptance criteria | Unclear definition of done | Every story needs testable criteria |
| No stakeholder validation | Building wrong thing | Regular stakeholder reviews |
| Waterfall requirements | Can't adapt to change | Iterative refinement |
| Technical jargon | Business can't validate | Use business language |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Registry listing for business-analyst matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: business-analyst is focused, and the summary matches what you get after install.
business-analyst fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
business-analyst fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
business-analyst is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
business-analyst reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: business-analyst is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend business-analyst for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added business-analyst from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
business-analyst fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 54