adr-madr

Generate MADR-compliant architectural decision records from git logs, pull requests, or freeform text.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/c-tomioka/mbtorch --skill adr-madr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr-madr
Source: https://github.com/c-tomioka/mbtorch/tree/main/.claude/skills/adr-madr
Command: npx skills add https://github.com/c-tomioka/mbtorch --skill adr-madr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizes informal architecture decisions, PR/issue discussions, and git history into a consistent, MADR-compliant Architectural Decision Record so teams can track and communicate design choices reliably.

Core Features & Use Cases

  • Create MADR ADRs: Convert freeform decision notes, meeting outcomes, or PR descriptions into a structured MADR-format markdown file with metadata, context, drivers, options, outcome, pros/cons, and links.
  • Reverse-engineer from repository artifacts: Infer ADRs from git logs, commits, PRs, and issues while flagging assumptions when information is missing.
  • Update existing ADRs: Accept an existing ADR and a list of changes and regenerate a single, updated ADR file following the repository's naming and placement rules.
  • Use Case: When a design decision is reached in a PR discussion, run this skill to produce a one-file MADR ADR, propose a docs/adr filename, and surface any information gaps for follow-up.

Quick Start

Create a MADR ADR from the provided decision notes, git log excerpt, or PR text and suggest a docs/adr filename using the repository conventions.

Frequently Asked Questions about adr-madr

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

FAQPage Schema
How do I create an architectural decision record from git logs and PR discussions?

To create an architectural decision record from git logs and PR discussions, you can generate a structured MADR-format markdown file that captures metadata, context, decision drivers, considered options, and outcomes from those repository artifacts.

What is a MADR-format architectural decision record?

A MADR-format architectural decision record is a structured markdown document that standardizes architecture decisions by capturing metadata, context, problem statements, decision drivers, considered options, outcomes, pros and cons, and links.

Can I update existing ADR markdown files with new changes?

Yes, you can update existing ADR markdown files by accepting the current ADR and a list of changes to regenerate a single updated file following the repository's naming and placement conventions.

How do I document architecture decisions when information is missing from commit history?

When reverse-engineering architecture decisions from commit history with missing information, the process flags assumptions and surfaces information gaps for follow-up while producing a MADR-compliant markdown file.

Does this approach work for converting freeform meeting notes into decision records?

Yes, this approach works for converting freeform decision notes and meeting outcomes into a structured MADR-format markdown file, proposing a docs/adr filename using repository conventions.

What is the best way to reverse-engineer architectural decisions from repository artifacts?

The best way to reverse-engineer architectural decisions from repository artifacts like git logs, commits, PRs, and issues is to infer ADRs while flagging assumptions, producing a MADR-compliant markdown document with all standard decision sections.