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.
The English summary is being prepared. Showing the original description.
See how to installReview 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.
node {project-root}/_bmad/ade-runtime.mjs resolve_config --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.
Rules against AI slop in code, comments, commit messages and docs. Use whenever you write or edit code, write documentation, a README, a commit message or a PR description, or review changes for quality.
The English summary is being prepared. Showing the original description.
AI Agent Architect: Design agent systems: single vs multi-agent, tools and MCP, memory, guardrails, evals.
The English summary is being prepared. Showing the original description.
AI Automation Strategist: Decide what to automate: opportunity mapping, ROI, build vs buy, rollout and change management.
The English summary is being prepared. Showing the original description.
AI x Web3 Architect: Autonomous agents that hold wallets: smart accounts, spend limits, intents, agent payments.
The English summary is being prepared. Showing the original description.
Workflow Automation Architect: Automate business processes: triggers, queues, retries, approvals, n8n vs Temporal vs code.
The English summary is being prepared. Showing the original description.
Smart Contract Systems Architect: Contract system design: modules, upgradeability, access control, storage, audit readiness.
The English summary is being prepared. Showing the original description.