What does BMAD stand for?

BMAD stands for Business Model, Architecture, and Design, representing the three core pillars of comprehensive software planning addressed by this tool.

Is the epic breakdown manual or automatic?

The PM persona automatically analyzes the requirements and architecture generated in the first two phases to identify work streams and dependencies without extra user input.

How does this skill save tokens?

By generating static documentation files locally via a script, Claude can reference these files as context instead of having to regenerate the entire planning logic in its context window for every prompt.

Can I edit the generated documents?

Yes, the tool generates standard Markdown files in your repository's planning folder, allowing you to manually refine requirements or architecture after the Q&A session.

Do I need to be on a specific git branch?

The tool is designed to be used on a 'contrib' branch within the main repository to ensure planning documents are version-controlled before feature implementation begins.

BMAD Planning Assistant

Name: BMAD Planning Assistant
Author: stharrold

bystharrold

生产力与工作流

Generates comprehensive business, architecture, and design documentation through an interactive three-persona Q&A session.

关于

The BMAD (Business Model, Architecture, and Design) Planner is a specialized tool designed to streamline the project planning phase by generating detailed requirements, technical architecture, and epic breakdowns. By utilizing an interactive Q&A session led by distinct Analyst, Architect, and Project Manager personas, it captures critical project context and produces standardized Markdown documentation. This structured approach not only ensures professional-grade planning before feature development but also significantly optimizes token usage in Claude Code sessions by providing pre-defined context files that reduce repetitive reasoning overhead.

主要功能

High token efficiency saving ~2,300 tokens per feature compared to manual planning
Automated generation of requirements.md, architecture.md, and epics.md
Three-persona interactive Q&A workflow (Analyst, Architect, and PM)
Standardized directory structure compatible with SpecKit and workflow orchestrators
0 GitHub stars
Built-in git integration for automated committing of planning artifacts

使用场景

Initial feature planning and requirement gathering before starting development
Breaking down complex business requirements into manageable, prioritized epics
Technical architecture design and system component mapping for new modules

关于

主要功能

High token efficiency saving ~2,300 tokens per feature compared to manual planning
Automated generation of requirements.md, architecture.md, and epics.md
Three-persona interactive Q&A workflow (Analyst, Architect, and PM)
Standardized directory structure compatible with SpecKit and workflow orchestrators
0 GitHub stars
Built-in git integration for automated committing of planning artifacts

使用场景

Initial feature planning and requirement gathering before starting development
Breaking down complex business requirements into manageable, prioritized epics
Technical architecture design and system component mapping for new modules