adr

Create MADR-formatted architectural decision records with structured sections.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/baldimir/bob-skills --skill adr-baldimir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/baldimir/bob-skills/tree/main/.bob/skills/adr
Command: npx skills add https://github.com/baldimir/bob-skills --skill adr-baldimir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures and communicates the rationale behind architectural decisions to guide future work and avoid repeating debates.

Core Features & Use Cases

  • MADR-compliant ADRs: Append-only records that document context, decisions, drivers, options, outcomes, and tradeoffs.
  • Lifecycle guidance: Step-by-step workflow from drafting to reviewing and superseding when needed.
  • Integration prompts: Triggers that align with dependency upgrades or design captures to generate relevant ADRs.

Quick Start

Draft an ADR that records the decision context and rationale using the MADR format.

Frequently Asked Questions about adr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is an architectural decision record and when do I need one?

An architectural decision record (ADR) captures the rationale behind software architecture decisions to guide future work and avoid repeating debates. You need one for tech selections, major design pivots, and decisions requiring documented context and tradeoffs.

How do I document architectural decisions using the MADR format?

Document architectural decisions by creating append-only MADR-formatted records with structured sections for context, drivers, options, decisions, consequences, and links to capture full decision rationale and lifecycle history.

How do I handle superseding an architectural decision when requirements change?

Supersede architectural decisions using an append-only workflow that preserves the original record and links to the new ADR, ensuring the decision lifecycle from drafting to reviewing remains traceable for future teams.

What should be included in the context and drivers sections of an ADR?

The context section should describe the architectural problem and background, while drivers should capture the forces and priorities influencing the decision. Together they establish why specific options were evaluated.

Can I generate ADRs automatically when doing dependency upgrades or design captures?

Yes, integration prompts trigger ADR generation aligned with dependency upgrades or design captures, allowing you to automatically draft relevant records that document the decision context and rationale using the MADR format.