bmad-agent-analyst

Analyze business needs and translate vague requirements into concrete specifications.

3|2|Updated Mar 29, 2024
One-click install
npx skills add https://github.com/josemariafs/MVTools --skill bmad-agent-analyst-josemariafs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-analyst
Source: https://github.com/josemariafs/MVTools/tree/main/.cursor/skills/bmad-agent-analyst
Command: npx skills add https://github.com/josemariafs/MVTools --skill bmad-agent-analyst-josemariafs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mary helps teams transform vague business needs into precise, actionable specifications, reducing back-and-forth and aligning stakeholders.

Core Features & Use Cases

  • Requirements elicitation: capture stakeholder needs and translate them into clear requirements.
  • Market research & analysis: synthesize competitive and market data to inform product decisions.
  • Documentation & briefs: produce structured product briefs and decision records for teams.

Quick Start

Ask Mary to become your business analyst and start eliciting requirements for your project.

Frequently Asked Questions about bmad-agent-analyst

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

FAQPage Schema
How do I translate vague business needs into concrete product specifications?

To translate vague business needs into concrete product specifications, you need structured requirements elicitation and stakeholder alignment to capture needs and produce clear, actionable specs.

What is the best way to structure product briefs and decision records for teams?

The best way to structure product briefs and decision records is through structured documentation that synthesizes market research and stakeholder needs into precise, actionable specifications for team alignment.

How does market research inform product decisions and stakeholder alignment?

Market research informs product decisions by synthesizing competitive and market data into structured product briefs, ensuring stakeholder alignment and reducing back-and-forth communication.

Can I use a persona-driven approach for business analysis and requirements elicitation?

Yes, you can use a persona-driven approach for business analysis that applies structured expertise to requirements elicitation, loading configuration and persistent facts to produce evidence-based outputs.

Do I need configuration files to perform evidence-based business analysis?

Yes, evidence-based business analysis requires loading configuration and persistent facts from customize.toml and project files to apply structured persona-driven analysis and generate accurate outputs.

Why does stakeholder alignment fail when translating vague requirements?

Stakeholder alignment fails when vague requirements lack precise, actionable specifications, causing back-and-forth communication that structured requirements elicitation and clear documentation are designed to resolve.