bmad-agent-analyst

Clarify ambiguous product ideas into structured requirements and analysis outputs.

Updated May 23, 2026

Search Tags:#requirements #market research #competitive analysis #product brief #business analysis #stakeholder discovery

Ready to run

npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-agent-analyst-diegosanchespereira1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-agent-analyst
Source: https://github.com/diegosanchespereira1/lavarapido/tree/main/lava-rapido/.agents/skills/bmad-agent-analyst
Command: npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-agent-analyst-diegosanchespereira1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn ambiguous ideas, scattered stakeholder input, and early-stage project uncertainty into clear, evidence-based analysis and actionable requirements.

Core Features & Use Cases

Business Analysis Guidance: Structure discovery conversations, synthesize findings, and frame decisions with strategic rigor.
Research and Requirement Discovery: Support market research, competitive analysis, stakeholder needs mapping, and precise requirements elicitation.
Use Case: A founder has a rough SaaS concept and needs a crisp brief, so this Skill can help define the problem, identify users, and organize the scope before development starts.

Quick Start

Ask Mary to analyze your idea and turn it into a structured business brief with clear requirements, stakeholders, and next-step recommendations.

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 a vague SaaS idea into structured product requirements?▼

To turn a vague idea into structured product requirements, you need to clarify ambiguous concepts through stakeholder discovery and synthesize findings into an evidence-based business brief with clear scope.

What is the best way to conduct stakeholder discovery for early-stage project scoping?▼

Stakeholder discovery for early-stage scoping involves structuring discovery conversations to map stakeholder needs, synthesizing input, and framing decisions with strategic rigor to produce actionable analysis outputs.

How does competitive analysis work when defining a product brief?▼

Competitive analysis for a product brief works by researching market conditions, synthesizing evidence-based findings, and translating them into precise requirement capture and documentation for analysis workflows.

Can I use business analysis to map stakeholder needs before development starts?▼

Yes, you can use business analysis to map stakeholder needs before development by defining the problem, identifying users, and organizing the scope to frame decisions with strategic rigor.

Does this approach support market research for early-stage project scoping?▼

Yes, this approach supports market research for early-stage project scoping by clarifying ambiguous business ideas and synthesizing evidence into structured requirements and next-step recommendations.

What are the limitations of using business analysis for requirement capture?▼

Business analysis for requirement capture is limited to early-stage project scoping and documentation, focusing on structuring discovery rather than executing downstream development or technical implementation tasks.