write-adr

Create MADR-compliant Architecture Decision Records with structured sections.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/hpsgd/claude-marketplace --skill write-adr-hpsgd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-adr
Source: https://github.com/hpsgd/claude-marketplace/tree/main/plugins/engineering/architect/skills/write-adr
Command: npx skills add https://github.com/hpsgd/claude-marketplace --skill write-adr-hpsgd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions are often scattered, hard to audit, and difficult to revisit. This skill provides a standardized way to capture the rationale, constraints, and outcomes of architectural choices using the MADR template.

Core Features & Use Cases

  • MADR-compliant frontmatter: metadata such as status, date, decision-makers, consulted, and informed.
  • Structured narrative: sections for context, decision drivers, options considered, the chosen decision, consequences, and confirmation criteria.
  • Auditability and reuse: enables traceability across teams and versions, and easy linking to related ADRs.

Quick Start

Draft an ADR for a significant architectural decision using the MADR template and populate it with the decision context, options, and outcome.

Frequently Asked Questions about write-adr

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

FAQPage Schema
How do I document an architectural decision for traceability across teams?

To document an architectural decision, use a MADR-compliant ADR template to capture context, decision drivers, options, and outcomes. This standardizes rationale and ensures traceability across teams.

What is the MADR format for architecture decision records?

MADR is a structured Architecture Decision Record template featuring frontmatter metadata like status and decision-makers, plus narrative sections for context, options, consequences, and confirmation criteria.

When should I write an ADR for a software architecture choice?

Write an ADR for significant choices affecting system architecture, service boundaries, data flows, or technology across multiple teams, capturing the rationale and constraints for future reference.

What sections are required in a MADR architecture decision record?

A MADR record requires frontmatter metadata, context, decision drivers, considered options, decision outcome, consequences, and confirmation criteria to fully document an architectural choice.

Does this ADR template work for documenting service boundaries and data flows?

Yes, this ADR template applies to decisions affecting service boundaries and data flows, providing a standardized way to capture the rationale, constraints, and outcomes of these choices.