Business Analyst

Translate stakeholder needs into clear product requirements and product briefs.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/coco-de/bmad --skill business-analyst-coco-de
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Business Analyst
Source: https://github.com/coco-de/bmad/tree/main/skills/bmad/bmm/analyst
Command: npx skills add https://github.com/coco-de/bmad --skill business-analyst-coco-de

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to translate vague stakeholder needs into concrete, testable requirements, leading to scope creep and misaligned outcomes.

Core Features & Use Cases

  • Structured discovery workflows: guides through problem framing, stakeholder interviews, and competitive research to produce a coherent product brief.
  • Requirements synthesis: converts insights into clear, testable requirements and success criteria.
  • Collaboration-ready outputs: generates artifacts suitable for handoff to PRD, design, and engineering.

Quick Start

Describe the product problem and goals to start a discovery brief.

Frequently Asked Questions about Business Analyst

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

FAQPage Schema
How do I translate stakeholder needs into clear product requirements?

To translate stakeholder needs into clear product requirements, use structured discovery workflows that guide problem framing, stakeholder interviews, and market research to synthesize insights into testable requirements and success criteria.

What is the best way to structure product discovery for a product brief?

The best way to structure product discovery is to apply a structured workflow covering problem framing, stakeholder interviews, and competitive research, ensuring you produce a coherent, collaboration-ready product brief for downstream teams.

How do I turn vague stakeholder needs into testable requirements?

Turn vague stakeholder needs into testable requirements by synthesizing insights gathered during stakeholder interviews and market research, converting them into concrete success criteria that prevent scope creep and misaligned outcomes.

Can I use this workflow for early phase product discovery and competitive research?

Yes, this workflow supports Phase 1 product discovery by guiding competitive research and stakeholder interviews, allowing you to load context, apply templates, collect inputs, and generate traceable discovery artifacts.

Do I need to prepare stakeholder interview inputs before generating a product brief?

You need to describe the product problem and goals to start the discovery brief, which then structures the stakeholder interview process and context loading to ensure your final product requirements are traceable and accurate.

How does requirements synthesis prevent scope creep in product management?

Requirements synthesis prevents scope creep by converting raw stakeholder insights into clear, testable requirements and success criteria, ensuring all downstream PRD, design, and engineering handoffs remain aligned with the original discovery outcomes.