> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plannotator.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# BMad Method Framework Profile

> A source-backed profile of the BMad Method: adaptive delivery tracks, product briefs, PRDs, architecture, epics, stories, and sprint state.

The BMad Method is a role-oriented AI development method that can span discovery, product definition, architecture, epics, stories, implementation, and verification. It offers Quick Flow, BMad Method, and Enterprise tracks so the planning inventory can change with project scope.

**Source stamp:** [`bmad-code-org/BMAD-METHOD` at `717479bc`](https://github.com/bmad-code-org/BMAD-METHOD/tree/717479bc3f50f38119fd958b9e577a8bde2e0184), reviewed July 18, 2026. Repository license: MIT. BMad has separate trademark terms; this page uses the name only for identification.

## Representative artifact tree

```text theme={null}
_bmad-output/
  planning-artifacts/
    product-brief.md
    prd.md
    architecture.md
    epics.md
    project-context.md
  implementation-artifacts/
    stories/
    sprint-status.yaml
```

The official [getting-started tutorial](https://github.com/bmad-code-org/BMAD-METHOD/blob/717479bc3f50f38119fd958b9e577a8bde2e0184/docs/tutorials/getting-started.md) explains the tracks. The repository publishes source templates for the [product brief](https://github.com/bmad-code-org/BMAD-METHOD/blob/717479bc3f50f38119fd958b9e577a8bde2e0184/src/bmm-skills/1-analysis/bmad-product-brief/assets/brief-template.md), [PRD](https://github.com/bmad-code-org/BMAD-METHOD/blob/717479bc3f50f38119fd958b9e577a8bde2e0184/src/bmm-skills/2-plan-workflows/bmad-prd/assets/prd-template.md), architecture, epics, stories, and sprint status.

## Workflow and conventions

The method uses specialized roles and guided workflows. Its current PRD structure includes stable journey and functional-requirement IDs, glossary terms, non-goals, MVP boundaries, success metrics, counter-metrics, open questions, and assumptions. Architecture provides the solution spine; epics and stories turn the plan into delivery work. `project-context.md` can carry stack versions and implementation rules.

The result is broader than a feature specification or coding plan. Product, architecture, and delivery artifacts are separate objects, and the selected track determines how much of the method applies.

## Inspect the same-case output

Inspect the [generated BMad express technical specification and memory log for reliable webhook delivery](https://github.com/plannotator/spec-planning-frameworks/tree/main/examples/bmad-method/raw). The express specification flow completed. The run did not attempt BMad's full PRD, architecture, epics, and stories path.

## Choose BMad when

* the work begins before implementation planning and needs product discovery or a PRD;
* role-oriented workflows help the team divide analysis, product, architecture, and delivery;
* epics and stories are the preferred execution model; and
* the team wants the planning depth to change with the selected track.

Choose a smaller framework when the real job is one feature directory, one repository plan, or one architectural decision. The Plannotator-authored [PRD template](/templates/product-requirements-document) supplies one reusable artifact without adopting the full method, and [PRD vs technical specification vs implementation plan](/compare/prd-vs-technical-specification-vs-implementation-plan) explains the downstream boundary.

*Reviewed July 19, 2026. Researched and maintained by the Plannotator documentation team. BMad is named nominatively; Plannotator is not affiliated with or endorsed by BMad Code, LLC.*