What does BMAD stand for?

BMAD stands for Business Model, Architecture, and Design, which is a framework for comprehensive feature planning and documentation.

Can I use this on any branch?

The tool is optimized for use in the main repository on a contribution branch (e.g., contrib/username) during the initial planning phase.

How does this skill save tokens in Claude Code?

By running an interactive script to generate local files, Claude Code only needs to reference the final documents as context rather than regenerating the planning logic manually every time.

Does it support custom architecture choices?

Yes, during the Architect persona phase, the tool asks interactive questions about your technology stack, frameworks, and database preferences.

Where are the planning documents stored?

Documents are stored in a feature-specific directory under planning/ /, including requirements, architecture, epics, and context files.

BMAD Planning Tool

Name: BMAD Planning Tool
Author: stharrold

bystharrold

Productivity & Workflow

Streamlines software development planning by generating comprehensive requirements, architecture, and epic documentation through an interactive Q&A workflow.

About

BMAD Planning Tool is an interactive utility for Claude Code designed to formalize the pre-development phase of software engineering. By utilizing a three-persona Q&A system—Analyst, Architect, and Project Manager—it guides developers through requirements gathering, technical design, and task breakdown. This skill generates standardized Markdown documentation (requirements, architecture, and epics) directly in your repository, ensuring project consistency while saving up to 92% in token usage by providing Claude with pre-structured context rather than requiring manual repetition of planning logic.

Key Features

0 GitHub stars
Standardized directory structure compatible with SpecKit and automated workflows
High-efficiency token usage saving ~2,300 tokens per feature planning session
Automated generation of standardized requirements.md, architecture.md, and epics.md
Interactive Q&A guided by Analyst, Architect, and PM personas
Seamless Git integration for automatic committing of planning documents

Use Cases

Breaking down complex features into prioritized epics and actionable tasks
Defining functional and non-functional requirements for new software features
Designing technical system architecture and data models before coding begins

About

Key Features

0 GitHub stars
Standardized directory structure compatible with SpecKit and automated workflows
High-efficiency token usage saving ~2,300 tokens per feature planning session
Automated generation of standardized requirements.md, architecture.md, and epics.md
Interactive Q&A guided by Analyst, Architect, and PM personas
Seamless Git integration for automatic committing of planning documents

Use Cases

Breaking down complex features into prioritized epics and actionable tasks
Defining functional and non-functional requirements for new software features
Designing technical system architecture and data models before coding begins