Business Analyst

Conduct structured product discovery and requirements analysis for new products.

472|75|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/aj-geddes/claude-code-bmad-skills --skill business-analyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Business Analyst
Source: https://github.com/aj-geddes/claude-code-bmad-skills/tree/main/bmad-v6/skills/bmm/analyst
Command: npx skills add https://github.com/aj-geddes/claude-code-bmad-skills --skill business-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the initial product discovery and requirements analysis, ensuring a deep understanding of user needs and market problems before solutioning begins. It prevents building the wrong product by focusing on "why" before "what."

Core Features & Use Cases

  • Product Brief Creation: Generates comprehensive product brief documents with market analysis and user needs.
  • Problem Discovery: Guides through structured interviews and frameworks like "5 Whys" to identify core pain points.
  • Research Facilitation: Supports market, competitive, and user research to inform decisions.
  • Use Case: For a new project idea, use this Skill to create a product brief, defining the problem, target users, and key capabilities, setting a solid foundation for the planning phase.

Quick Start

Create a product brief for my new project idea. /product-brief

Frequently Asked Questions about Business Analyst

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

FAQPage Schema
How do I uncover user needs and define product requirements?

Product discovery uses structured interviews, frameworks like 5 Whys, and market research to identify core pain points and user needs before defining requirements. This approach ensures you understand the problem deeply before designing solutions, preventing wasted effort on the wrong product.

What should a product brief include?

A product brief documents the problem, target users, key capabilities, market analysis, and success metrics. It synthesizes discovery findings into a clear, actionable foundation that guides planning and communicates vision to stakeholders.

When do I need structured problem analysis instead of jumping to solutions?

Use problem framing and requirements analysis when product requirements are unclear, stakeholder expectations conflict, or you're entering a new market. Structured discovery prevents building features nobody needs and surfaces the actual problem worth solving.

Can I use this for competitive analysis and market research?

Yes. This Skill supports market and competitive research as part of product discovery, helping you understand competitive positioning and market gaps alongside user needs to inform product decisions.

How does this help with stakeholder alignment?

By documenting clear problem statements, user needs, and risk assessments, discovery outputs create shared understanding across stakeholders. This alignment surfaces disagreements early and prevents costly rework during development.