bmad-agent-analyst

Convert ambiguous product ideas into evidence-based requirements.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/mol4/BMAD-Board --skill bmad-agent-analyst-mol4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-analyst
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-agent-analyst
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-agent-analyst-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users move from vague product ideas to clear, evidence-based requirements by acting as a structured business analyst and research partner in the BMad Method analysis phase.

Core Features & Use Cases

  • Requirements Elicitation: Turns open-ended goals, stakeholder needs, and rough concepts into actionable specifications.
  • Market and Domain Analysis: Supports competitive research, customer insight gathering, and domain terminology exploration before committing to a build.
  • Product Discovery Support: Helps create briefs, brainstorm solutions, and assess technical feasibility so teams can make better early decisions.
  • Use Case: A founder with an unclear app idea can use this Skill to shape the concept, identify risks, and produce a stronger product brief for the next workflow step.

Quick Start

Ask the skill to analyze your idea, gather requirements, and recommend the best next discovery step.

Frequently Asked Questions about bmad-agent-analyst

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

FAQPage Schema
How do I turn vague product ideas into evidence-based requirements?

To turn vague product ideas into evidence-based requirements, you need structured requirements elicitation that gathers domain research and stakeholder needs, converting open-ended goals into actionable specifications and clear product briefs.

What is the best way to conduct market research and technical feasibility analysis before building an app?

Conducting market research and technical feasibility analysis requires gathering competitive insights, customer data, and domain terminology to assess risks early and produce a stronger product brief for subsequent development phases.

How do I analyze stakeholder needs for product discovery?

Analyzing stakeholder needs for product discovery involves synthesizing stakeholder-oriented insights through structured evidence gathering, transforming rough concepts and open-ended goals into actionable product specifications.

Can I use business analysis to create a product brief from an unclear app concept?

Yes, business analysis can create a product brief from an unclear app concept by performing brainstorming, domain exploration, and structured evidence gathering to clarify the idea and identify technical risks.

When do I need structured requirements elicitation instead of just brainstorming solutions?

Structured requirements elicitation is needed when moving beyond brainstorming to commit to a build, requiring precise stakeholder-oriented synthesis and market analysis to ensure early product decisions are evidence-based.