bmad-create-adr

To create an Architecture Decision Record, this workflow automates evidence-based investigation through context analysis, options discovery, trade-off evaluation, and decision formulation using step-by-step prompts and frontmatter templates. It enforces a disciplined process from problem framing to final publication with integrated validation checks.

Managing the ADR lifecycle requires tracking supersession to update prior records while preserving traceability and rationale. This workflow supports supersession natively, linking new decisions to outdated ones and maintaining a clear historical context for engineering teams without losing the original justification.

Yes, architecture decision records can be embedded directly into larger processes. This workflow operates standalone or triggers as a sub-workflow from spec and dev workflows, allowing engineering and product teams to capture architectural decisions seamlessly within active development cycles.

No specific framework is required to enforce evidence-based decision-making for ADRs. This workflow provides a self-contained, step-file driven process with integrated self-checks, evidence gathering, and decision rationale controls, ensuring disciplined documentation without external dependencies.

A guided workflow for architecture decision records is necessary when teams require a disciplined, evidence-based process with traceability. Use it to enforce consistent structure, validate trade-off evaluations, and manage supersession retrospectively, avoiding the gaps common in manual documentation approaches.