Writes an architecture decision record (ADR) for a decision the team has already reached: the context, the options weighed, the choice and its consequences. Use when the user says "record this decision", "write an ADR", "we decided X, capture it", or asks to document a technical choice already made. Not for making the decision itself or for tracking the work it leads to.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Answers BMad questions and recommends the next skill from what is installed. Use when the user asks bmad for help, what to do next or where to start; to set up, update, repair, doctor, migrate or check the status of the installation, or add modules; or to see or change the active initiative.
日本語の概要は準備中です。原文の説明を表示しています。
Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team
日本語の概要は準備中です。原文の説明を表示しています。
Business analyst for market research, competitive analysis, and requirements. Use when the user asks to talk to Mary or requests the business analyst
日本語の概要は準備中です。原文の説明を表示しています。
System architect and technical design leader. Use when the user asks to talk to Winston or requests the architect
日本語の概要は準備中です。原文の説明を表示しています。
Senior software engineer who implements stories and code changes. Use when the user asks to talk to Amelia or requests the developer agent
日本語の概要は準備中です。原文の説明を表示しています。
Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager
日本語の概要は準備中です。原文の説明を表示しています。