Write an architecture decision record, a document explaining a team's design choice. Capture the context, rejected alternatives, and future costs so newcomers can understand the reasoning, then review the draft before saving it.
Writes an architecture decision record (ADR). Use when the user says "record this decision", "write an ADR" or "we decided X, capture it".
Review the instructions the agent will receive before you install.
You turn a decision the team has reached into a record a newcomer can read a year later and understand why the system is the way it is. That reader was not in the room, so the record names the forces, not just the outcome.
uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} --key core.output_folder --key core.active_initiative. Script not found: BMad is not set up here; offer the bmad skill's setup, installing bmad first if needed (npx skills add bmad-code-org/BMAD-METHOD --skill bmad), then run it again.{output_folder}/{active_initiative}/adr-{slug}/adr-{slug}.md, dropping /{active_initiative} when unset. {slug} is the decision in kebab-case.Mine the conversation first: the decision, the options and the reasons are usually already there. Ask only for what is missing, one question at a time: what was decided, what else was considered and why it lost, what this makes harder later.
Write four sections: Context, Decision, Options considered, Consequences. Each option gets one line on why it lost. A consequence is something that will cost effort or close a door, not a benefit restated.
Show the draft and wait. On approval, write the file and tell the user the path.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Get guidance on using installed BMad modules and choosing the next skill for a task. The skill also handles installation setup, updates, repairs, module additions, artifact migration, and selecting the active initiative being worked on.
Revisit a recent answer, plan, draft, or decision using selected critique methods. The skill offers relevant approaches, explains what they reveal, and proposes improvements that are applied only after the user accepts them.
Work with Mary, a business analyst persona, to research markets, examine competitors, and clarify requirements. Use evidence-based discussion to turn vague needs into concrete specifications that can guide the next steps of a project.
Turn product requirements and user experience plans into technical architecture with Winston, a system architect persona. Discuss technology choices and their trade-offs, with an emphasis on established tools, developer productivity, and designs that can be implemented.
Implement approved development stories and code changes with Amelia, a senior software engineer persona. Follow a test-first process: write a failing test, make it pass, then improve the code while checking every acceptance criterion.
Work with John, a product manager persona, to clarify requirements through user interviews and stakeholder alignment. Turn a product vision into a PRD, a product requirements document, and small, validated increments for development.