What does BMAD stand for?

BMAD stands for Business Model, Architecture, and Design. It is a structured planning framework used to define project requirements and technical implementation details.

Where are the planning documents stored?

Documents are generated within a 'planning/ /' directory in your main repository, typically on a 'contrib/' branch.

How does this skill save tokens?

By offloading the generation of large document templates to an external Python script, the tool avoids having Claude manually output hundreds of lines of text, reducing prompt usage by over 2,000 tokens.

Which personas are involved in the planning?

The tool uses three personas: the BMAD Analyst (Requirements Gathering), the BMAD Architect (Technical Design), and the BMAD PM (Epic Breakdown).

BMAD Project Planner

Name: BMAD Project Planner
Author: stharrold

bystharrold

•

Productividad y Flujo de Trabajo

Generates comprehensive project planning documentation through an interactive three-persona Q&A system for requirements, architecture, and epics.

Acerca de

BMAD Planner (Business Model, Architecture, and Design) is a high-efficiency tool for Claude Code designed to formalize the software planning phase. It utilizes an interactive Python script to guide users through structured sessions with three distinct personas: a Business Analyst for requirements, an Architect for technical design, and a Project Manager for epic breakdowns. By automating the generation of standardized markdown documents, it ensures project consistency while achieving up to 92% token savings compared to manual prompting, making it an essential utility for developers using SpecKit or complex workflow orchestrators.

Características Principales

Interactive Q&A sessions with specialized Analyst and Architect personas
Automatic generation of requirements.md, architecture.md, and epics.md files
Programmatic token optimization saving 2,000-2,700 tokens per feature
Structured epic breakdown including priorities, complexity, and dependencies
Integrated Git commit workflow for planning documentation
1 GitHub stars

Casos de Uso

Reducing LLM token overhead when generating long-form architectural documentation
Standardizing the project planning process across a development team
Defining detailed business requirements and technical specs before starting a new feature

Acerca de

Características Principales

Interactive Q&A sessions with specialized Analyst and Architect personas
Automatic generation of requirements.md, architecture.md, and epics.md files
Programmatic token optimization saving 2,000-2,700 tokens per feature
Structured epic breakdown including priorities, complexity, and dependencies
Integrated Git commit workflow for planning documentation
1 GitHub stars

Casos de Uso

Reducing LLM token overhead when generating long-form architectural documentation
Standardizing the project planning process across a development team
Defining detailed business requirements and technical specs before starting a new feature