adr-generation

Generate MADR-formatted Architecture Decision Records with at least three options.

Updated Dec 30, 2025

Search Tags:#adr #software-engineering #madr #decision-records #architectural-decisions #architecture-documentation

Ready to run

npx skills add https://github.com/henrybravo/developer-readiness-portal --skill adr-generation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adr-generation
Source: https://github.com/henrybravo/developer-readiness-portal/tree/main/.github/skills/adr-generation
Command: npx skills add https://github.com/henrybravo/developer-readiness-portal --skill adr-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decision records (ADRs) capture the rationale behind significant technical choices to ensure traceability and context for future maintenance.

Core Features & Use Cases

MADR-formatted ADRs: One ADR file per decision containing context, options, decision, and consequences.
Option comparison: Document at least three considered options with pros/cons to support transparent decision-making.
Guidance and templates: Standard MADR template and conventions to ensure consistency across projects.
Use Cases: Technology stack selections, deployment strategies, data modeling decisions, API design choices, and security/compliance considerations.

Quick Start

Invoke this skill to generate MADR-formatted ADRs for a given architectural decision.

Frequently Asked Questions about adr-generation

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

FAQPage Schema

How do I document architectural decisions for technology stack choices?▼

Document architectural decisions by generating MADR-formatted records that capture context, options, decision, and consequences for technology stack choices. The skill ensures at least three options are considered with pros and cons to support transparent decision-making.

What is the MADR format for architecture decision records?▼

The MADR format structures architecture decision records into context, options, decision, and consequences sections. It provides a standard template and conventions to ensure consistency across projects when documenting technical choices like deployment strategies and data models.

How do I compare deployment strategy options in an ADR?▼

Compare deployment strategy options in an ADR by documenting at least three considered options with their respective pros and cons. The generated record provides transparent rationale and trade-offs to support the final architectural decision.

Can I use this for data modeling and API design decisions?▼

Yes, you can use it for data modeling and API design decisions. It applies to technology stack selections, deployment strategies, data models, and integration patterns, generating one ADR file per decision to ensure traceability and context.

What's the best way to ensure rationale and trade-offs are captured in technical documentation?▼

Capture rationale and trade-offs by generating MADR-compliant architecture decision records. This approach standardizes technical documentation by explicitly comparing multiple options and detailing the consequences of the chosen integration patterns or security considerations.