bmad-agent-analyst

Transforms vague product and business needs into actionable requirements and market insights.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-agent-analyst-amitmishra-byldd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-analyst
Source: https://github.com/amitmishra-byldd/Bmad-Note-Maker/tree/main/_bmad/bmm/1-analysis/bmad-agent-analyst
Command: npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-agent-analyst-amitmishra-byldd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams and stakeholders convert fuzzy business ideas, ambiguous requests, and fragmented market signals into clear, evidence-backed requirements and strategic insights that enable prioritized product decisions.

Core Features & Use Cases

  • Market & Competitive Analysis: Synthesize market trends, competitor positioning, and customer needs into actionable guidance.
  • Requirements Elicitation: Transform stakeholder interviews and nebulous product concepts into precise, implementable requirements and acceptance criteria.
  • Technical & Domain Translation: Bridge business goals and technical feasibility by outlining architecture considerations and constraints for engineering teams.
  • Use Case: Give Mary a product concept and receive a prioritized product brief with key market drivers, risks, and a requirements backlog.

Quick Start

Ask Mary to evaluate our product idea, summarize the target market and competitors, and produce a prioritized list of user-facing requirements.

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 product ideas into clear requirements for engineering?

To translate vague product ideas into clear requirements, you need structured requirements elicitation. This process transforms ambiguous business needs and fragmented market signals into precise, actionable requirements documentation with defined acceptance criteria.

What is the best way to structure stakeholder interviews for product discovery?

The best way to structure stakeholder interviews for product discovery is by applying a structured stakeholder mapping framework. This approach extracts nebulous product concepts and business goals, converting them into evidence-backed strategic insights for prioritized decisions.

How do I conduct competitive analysis and synthesize market trends for a product brief?

Conducting competitive analysis involves synthesizing competitor positioning and customer needs into actionable guidance. This market research yields a prioritized product brief highlighting key market drivers, competitive intelligence, and strategic risks for product initiatives.

Can I bridge business goals and technical feasibility when documenting product requirements?

You can bridge business goals and technical feasibility by outlining architecture considerations and constraints during requirements documentation. This technical and domain translation ensures engineering teams receive implementable requirements aligned with product strategy.

Does this approach to requirements elicitation work for early-stage product initiatives?

Yes, this requirements elicitation approach works for early-stage product initiatives. It provides structured frameworks to evaluate new product concepts, summarize target markets, and produce a prioritized list of user-facing requirements and a backlog.