Verified:GitHub

bmad-agent-analyst

Translate strategic business questions into evidence-grounded requirements and analysis.

4|Updated Apr 26, 2026

Search Tags:#market research #business analysis #competitive landscape #evidence-based #requirements elicitation #PRFAQ #product briefs

Ready to run

npx skills add https://github.com/curdx/curdx-flow --skill bmad-agent-analyst-curdx

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts vague business goals into structured, evidence-grounded requirements that Claude Code can use to plan and execute safely instead of drifting or hallucinating.

Core Features & Use Cases

Strategic requirements elicitation: Translate user intent into actionable analysis and specifications for downstream specs and decisions.
Persona-driven discovery workflow: Operate as “Mary” to guide brainstorming, market research, domain deep-dives, technical feasibility, and product/PRFAQ documentation via a menu of specialist sub-skills.
Persistent, repo-scoped context loading: Load persistent facts from project context files and apply resolved configuration to keep answers consistent across a session.

Quick Start

Invoke bmad-agent-analyst and ask Mary to analyze what the business needs, including target customers, success criteria, constraints, and risks.

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 business goals into structured product requirements?▼

To convert messy needs into precise requirements, use a structured analyst workflow that translates strategic business questions into evidence-grounded specifications. This process guides brainstorming and domain deep-dives to prevent planning drift and hallucination in downstream execution.

What is evidence-based market research and when do I need it for product planning?▼

Evidence-based market research for product planning is the process of grounding competitive landscape analysis and domain terminology in verified facts rather than assumptions. You need it when translating strategic business questions into actionable specifications to prevent planning drift and hallucination.

How do I create a PRFAQ or product brief from unstructured business ideas?▼

To create a PRFAQ or product brief from unstructured ideas, use a persona-driven discovery workflow that routes your input through specialist sub-tasks. This process elicits strategic requirements and maps your target customers, constraints, and risks into structured documentation.

Can I maintain consistent business analysis context across a long working session?▼

Yes, you can maintain consistent business analysis context across a session by loading persistent, repo-scoped facts from project context files. Applying resolved configuration ensures your evidence-grounded requirements and competitive landscape analysis remain accurate throughout the workflow.

Does generating technical feasibility framing require prior project configuration?▼

Generating technical feasibility framing requires resolving agent configuration from a customize.toml file and executing activation steps. This setup ensures the specialist sub-skills can load persistent project facts before dispatching your market research or product brief tasks.

What is the best way to structure competitive landscape analysis for new product specs?▼

The best way to structure competitive landscape analysis for new product specs is through a routed sub-task workflow that enforces an evidence-grounded analyst persona. This approach systematically maps domain terminology and market research into precise requirements for downstream planning.