bmad-evo

Analyze fuzzy requirements into structured specs, constraints, and task decompositions.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Lizhiyu-foshan/Multi-Agent-Pipeline --skill bmad-evo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-evo
Source: https://github.com/Lizhiyu-foshan/Multi-Agent-Pipeline/tree/main/.skills/bmad-evo
Command: npx skills add https://github.com/Lizhiyu-foshan/Multi-Agent-Pipeline --skill bmad-evo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BMAD-EVO provides deep requirement analysis through multi-agent collaboration. It clarifies fuzzy requirements through multi-round Q&A, generates clear requirement docs, architecture design, and task decomposition. It handles new user stories and bug feedback with analysis updates and spec evolution, grounding analyses with spec context.

Core Features & Use Cases

  • Multi-agent requirement analysis and clarification via Q&A to converge on goals and constraints.
  • Constraint generation and spec evolution to feed into spec-kit for reliable implementation.
  • Spec-context integration and comprehensive reporting (analysis, reports, and evolution suggestions) to guide architecture and planning.

Quick Start

Load your project and run the BMAD-EVO adapter to analyze a simple requirement, for example 'Build a REST API for a product catalog'.

Frequently Asked Questions about bmad-evo

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

FAQPage Schema
How do I analyze fuzzy requirements to produce structured specs and task decompositions?

Multi-agent requirement analysis clarifies fuzzy requirements through multi-round Q&A, generating structured specs, constraints, architecture design, and task decompositions. It uses spec context and interactive collaboration to converge on clear goals.

What is spec evolution and when do I need it for requirement updates?

Spec evolution updates existing requirement docs to handle new user stories or bug feedback. You need it when initial specs must adapt to changing constraints, grounding the updates with spec context for reliable implementation.

How do I start a multi-agent requirement analysis for a REST API project?

Load your project and run the BMAD-EVO adapter to analyze a simple requirement, such as building a REST API for a product catalog. The runtime uses the opencode prompt-passing protocol for interactive analysis.

Does multi-agent requirement analysis work without the opencode prompt-passing protocol?

No, the analysis requires the BMAD-EVO runtime and the opencode prompt-passing protocol. These dependencies are necessary to facilitate multi-agent collaboration, interactive Q&A, and context integration.

What is the best way to handle bug feedback and update specifications during development?

Applying spec evolution to bug feedback analyzes the issue and updates the specification context. This generates comprehensive reports and evolution suggestions to guide architecture adjustments and planning.

Can I use this for system design and architecture planning across the development lifecycle?

Yes, the analysis applies to requirements engineering, system design, and spec evolution tasks across the development lifecycle. It generates constraint documentation and architecture design to guide planning.