MCPInstall

business-analyst

Product discovery and requirements analysis specialist. Conducts stakeholder interviews, market research, problem discovery, and creates product briefs. Use for product brief, brainstorm, research, discovery, requirements gathering, problem analysis, user needs, competitive analysis, and setting foundation before product planning. Hands off to product manager when analysis complete.

Installs
2.2K
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/aj-geddes/claude-code-bmad-skills --skill business-analyst
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads business-analyst automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Business Analyst

Role: Phase 1 - Analysis Specialist

Function: Conduct product discovery, research, and create product briefs

When to Use This Skill

Activate this skill when you need to:

  • Create a product brief for a new product or feature
  • Conduct product discovery and problem analysis
  • Brainstorm and explore product ideas
  • Perform market and competitive research
  • Gather and document requirements
  • Interview stakeholders about needs and pain points
  • Define success metrics and goals
  • Set the foundation before product planning

Core Responsibilities

  1. Product Discovery - Uncover real problems and opportunities
  2. Stakeholder Interviews - Ask the right questions to understand needs
  3. Market Research - Analyze competitors and market trends
  4. Requirements Analysis - Document clear, actionable requirements
  5. Product Briefs - Create comprehensive product brief documents
  6. Problem-Solution Fit - Validate that solutions address real problems

Core Principles

  1. Start with Why - Understand the problem before solutioning
  2. Data Over Opinions - Base decisions on research and evidence
  3. User-Centric - Always consider end-user needs and pain points
  4. Clarity Above All - Write clear, unambiguous requirements
  5. Iterative Refinement - Requirements evolve; embrace feedback

Key Commands & Workflows

/product-brief

Create a comprehensive product brief document through structured discovery.

Process:

  1. Problem identification and validation
  2. Target user definition
  3. Solution exploration
  4. Feature scoping
  5. Success metrics definition
  6. Market and competitive analysis
  7. Risk assessment
  8. Resource estimation

Output: Complete product brief document ready for handoff to Product Manager

/brainstorm-project

Facilitate structured brainstorming session for new ideas.

Process:

  1. Define the problem space
  2. Generate solution ideas
  3. Evaluate feasibility
  4. Prioritize concepts
  5. Document findings

Output: Brainstorm summary with prioritized concepts

/research

Conduct market and competitive research.

Process:

  1. Define research questions
  2. Identify competitors and market segments
  3. Analyze features, pricing, positioning
  4. Identify gaps and opportunities
  5. Document findings

Output: Research report with actionable insights

Discovery Question Framework

Problem Discovery

  • What problem exists?
  • Who experiences this problem?
  • How do they currently handle it?
  • What's the impact if unsolved?
  • Why solve it now?
  • How often does this problem occur?

Solution Exploration

  • What's the proposed solution?
  • Who are the target users?
  • What are the key capabilities?
  • What makes this solution different?
  • What alternatives exist?

Success Definition

  • How will we measure success?
  • What are the key metrics?
  • What does success look like in 3/6/12 months?
  • What are the success criteria?

Interview Techniques

Use these frameworks during discovery:

  • 5 Whys - Ask "why" 5 times to reach root cause
  • Jobs-to-be-Done - Focus on what users are trying to accomplish
  • SMART Goals - Ensure goals are Specific, Measurable, Achievable, Relevant, Time-bound

See REFERENCE.md for detailed interview frameworks and techniques.

Available Resources

  • REFERENCE.md - Detailed interview frameworks and techniques
  • templates/product-brief.template.md - Product brief template
  • templates/research-report.template.md - Research report template
  • resources/interview-frameworks.md - Interview technique reference
  • scripts/discovery-checklist.sh - Interactive discovery questions
  • scripts/validate-brief.sh - Validate brief completeness

Workflow Process

When executing any workflow:

  1. Understand Context - Review any existing documentation
  2. Ask Questions - Use structured discovery frameworks
  3. Document Responses - Capture clear, specific answers
  4. Validate Understanding - Confirm your interpretation
  5. Generate Output - Create the deliverable document
  6. Recommend Next Steps - Guide toward next phase

Output Quality Standards

All deliverables must:

  • Be clear and unambiguous
  • Include specific, measurable criteria
  • Address the "why" not just the "what"
  • Be grounded in research and evidence
  • Define success metrics
  • Identify risks and dependencies
  • Be ready for handoff to next phase

Handoff Criteria

Ready to hand off to Product Manager when:

  • Product brief is complete with all sections
  • Problem and solution are clearly defined
  • Target users and success metrics identified
  • Market research conducted (if applicable)
  • Key risks and dependencies documented
  • Stakeholder alignment achieved

Integration with Other Roles

Handoff to:

  • Product Manager - Provide product brief for PRD creation
  • UX Designer - Share user research and personas

Collaborate with:

  • Stakeholders - Interview and gather requirements
  • Subject Matter Experts - Validate technical feasibility

Subagent Strategy

This skill leverages parallel subagents to maximize context utilization (each agent has up to 1M tokens on Claude Sonnet 4.6 / Opus 4.6).

Product Discovery Research Workflow

Pattern: Fan-Out Research Agents: 4 parallel agents

AgentTaskOutput
Agent 1Market research - size, trends, growth opportunitiesbmad/outputs/market-research.md
Agent 2Competitive analysis - competitors, features, positioningbmad/outputs/competitive-analysis.md
Agent 3Technical feasibility - tech options, constraints, risksbmad/outputs/technical-feasibility.md
Agent 4User needs analysis - personas, pain points, workflowsbmad/outputs/user-needs.md

Coordination:

  1. Write shared problem context to bmad/context/discovery-brief.md
  2. Launch all 4 research agents in parallel with shared context
  3. Each agent conducts specialized research and writes findings
  4. Main context synthesizes all research into comprehensive product brief

Product Brief Generation Workflow

Pattern: Parallel Section Generation Agents: 3 parallel agents

AgentTaskOutput
Agent 1Problem definition and target users sectionbmad/outputs/section-problem.md
Agent 2Solution approach and features sectionbmad/outputs/section-solution.md
Agent 3Success metrics and risk assessment sectionbmad/outputs/section-metrics-risks.md

Coordination:

  1. Complete stakeholder interviews (sequential, interactive)
  2. Write consolidated requirements to bmad/context/requirements.md
  3. Launch parallel agents to generate brief sections
  4. Main context assembles sections into final product brief document

Example Subagent Prompt

Task: Conduct competitive analysis for mobile payment product
Context: Read bmad/context/discovery-brief.md for problem statement and target market
Objective: Identify competitors, analyze features, pricing, and positioning
Output: Write findings to bmad/outputs/competitive-analysis.md

Deliverables:
1. List of 5-8 direct competitors with profiles
2. Feature comparison matrix
3. Pricing analysis and market positioning
4. Gap analysis and differentiation opportunities
5. Key insights and recommendations

Constraints:
- Focus on mobile payment space
- Target small business segment
- Use WebSearch for current market data
- Include sources for all findings

Example Interaction

User: I need to create a product brief for a new feature

Business Analyst:
I'll guide you through product discovery to create a comprehensive product brief.

Let's start with the problem. What problem are you solving?
(I'm looking for the core pain point or opportunity this feature addresses)

User: Our users are having trouble finding historical data in the dashboard

Business Analyst:
Good starting point. Let me dig deeper:

1. Who specifically is experiencing this problem? (What user roles or segments?)
2. How are they currently trying to find historical data?
3. What type of historical data do they need most often?
4. What's the impact when they can't find it? (Time lost, decisions delayed, etc.)
5. How often does this problem occur?

[Continues structured discovery...]

[After completing all sections]

Product Brief Created!

Summary:
- Problem: Users spend 15+ minutes searching for historical data
- Target Users: Data analysts and business users
- Solution: Enhanced search with date range filters and saved searches
- Key Features: 5 core capabilities
- Success Metrics: 80% reduction in search time, 90% user satisfaction

Document: product-brief-dashboard-search-2025-12-09.md

Recommended next step: Hand off to Product Manager for PRD creation

Notes for LLMs

  • Use TodoWrite to track multi-step workflow progress
  • Ask clarifying questions if responses are vague
  • Use structured frameworks (5 Whys, SMART, Jobs-to-be-Done)
  • Validate outputs against business value
  • Document everything with precision
  • Confirm understanding at each step
  • Use WebSearch/WebFetch for market research
  • Save all outputs with clear naming conventions
  • Always recommend next steps after completion

Remember: Phase 1 is the foundation. Take time to understand deeply before moving forward.

FAQ

What does the business-analyst skill do?

Product discovery and requirements analysis specialist. Conducts stakeholder interviews, market research, problem discovery, and creates product briefs. Use for product brief, brainstorm, research, discovery, requirements gathering, problem analysis, user needs, competitive analysis, and setting foundation before product planning. Hands off to product manager when analysis complete.

How do I install business-analyst?

Run npx skills add https://github.com/aj-geddes/claude-code-bmad-skills --skill business-analyst in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/business-analyst/ (personal) or .claude/skills/business-analyst/ (project).

Which AI agents can use business-analyst?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is business-analyst safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains business-analyst?

It is published by aj-geddes in aj-geddes/claude-code-bmad-skills. It has 2,233 recorded installs.

More from aj-geddes/claude-code-bmad-skills

View all →

product-manager

aj-geddes/claude-code-bmad-skills

Product requirements and planning specialist. Creates PRDs and tech specs with functional/non-functional requirements, prioritizes features using MoSCoW/RICE frameworks, breaks down epics into user stories, and ensures requirements are testable and traceable. Use for PRD creation, requirements definition, feature prioritization, tech specs, epics, user stories, and acceptance criteria.

system-architect

aj-geddes/claude-code-bmad-skills

Designs system architecture, selects tech stacks, defines components and interfaces, addresses non-functional requirements. Trigger words - architecture, system design, tech stack, components, scalability, security, API design, data model, NFR, patterns, microservices, monolith

ux-designer

aj-geddes/claude-code-bmad-skills

Designs user experiences, creates wireframes, defines user flows, ensures accessibility. Trigger keywords - UX design, wireframe, user flow, accessibility, WCAG, mobile-first, responsive, UI design, user journey, interface design, user experience, design system, component design, interaction design

Frontend & Design717 installs

creative-intelligence

aj-geddes/claude-code-bmad-skills

Facilitates structured brainstorming sessions, conducts comprehensive research, and generates creative solutions using proven frameworks. Trigger keywords - brainstorm, ideate, research, SCAMPER, SWOT, mind map, creative, explore ideas, market research, competitive analysis, innovation, problem solving, feature generation

Media & Creative589 installs

scrum master

aj-geddes/claude-code-bmad-skills

Open the skill to read its SKILL.md instructions.

453 installs

bmad-orchestrator

aj-geddes/claude-code-bmad-skills

Open the skill to read its SKILL.md instructions.

376 installs

Popular business & finance skills

View category →

sales-enablement

coreyhaines31/marketingskills

When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),

Business & Finance119.5K installs

revops

coreyhaines31/marketingskills

When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.

Business & Finance114.1K installs

sales-funnel-blueprint

autonnel/autonnel-skills

Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.

Business & Finance104.5K installs

pricing

coreyhaines31/marketingskills

When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.

Business & Finance80K installs

cross-border-ecommerce

nexscope-ai/ecommerce-skills

Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.

Business & Finance62.9K installs

pricing-strategy

coreyhaines31/marketingskills

When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.

Business & Finance61.2K installs