bmad-analyst

Elicit requirements, refine PRDs, and analyze business data.

2|Updated Apr 21, 2025
One-click install
npx skills add https://github.com/akvo/akvo-rag --skill bmad-analyst-akvo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-analyst
Source: https://github.com/akvo/akvo-rag/tree/main/.agent/skills/bmad-analyst
Command: npx skills add https://github.com/akvo/akvo-rag --skill bmad-analyst-akvo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the challenge of unclear or incomplete product requirements by providing a structured approach to deep-diving, research, and refinement, ensuring a solid foundation for development.

Core Features & Use Cases

  • Requirements Elicitation: Systematically gathers functional and non-functional requirements through probing questions and documentation review.
  • PRD Refinement: Enhances existing Product Requirement Documents by validating testability, checking for conflicts, and adding acceptance criteria.
  • Data Analysis: Analyzes business data to inform product decisions and validate assumptions.
  • Use Case: A product manager needs to define the requirements for a new feature. Mary, the Business Analyst, will engage with stakeholders, analyze existing documentation, conduct research, and produce a detailed PRD with clear acceptance criteria.

Quick Start

Use the bmad-analyst skill to refine the existing PRD for the new user authentication feature.

Frequently Asked Questions about bmad-analyst

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

FAQPage Schema
How do I refine a Product Requirement Document to ensure testability?

Requirements elicitation involves systematically gathering functional and non-functional requirements through probing questions and documentation review. It is needed to establish a solid foundation for product development when initial requirements are unclear.

What is the best way to conduct gap analysis for product development?

Yes, you can use business analysis capabilities to analyze business data, inform product decisions, and validate assumptions. This supports the creation of detailed documentation for product specifications.

How do I elicit functional and non-functional requirements for a new feature?

To elicit requirements, systematically gather functional and non-functional needs through probing questions and documentation review. This structured approach ensures comprehensive coverage for product development.

What is the best way to refine a PRD with clear acceptance criteria?

The best way to refine a PRD is by validating testability, checking for conflicts, and adding explicit acceptance criteria. This bridges business and technical domains while ensuring a solid foundation for development.

Does this business analysis approach support traceability for product specifications?

Yes, this approach supports detailed documentation and traceability for product specifications. It bridges business and technical domains through requirements elicitation, research, and gap analysis.

When do I need deep research and gap analysis for product development?

You need deep research and gap analysis when facing unclear or incomplete product requirements. This structured approach bridges business and technical domains to ensure a solid foundation for development.