adr-creation

Create MADR-based ADR documents with constraints from AGENTS.md.

4|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/d-o-hub/chaotic_semantic_memory --skill adr-creation-d-o-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr-creation
Source: https://github.com/d-o-hub/chaotic_semantic_memory/tree/main/.agents/skills/adr-creation
Command: npx skills add https://github.com/d-o-hub/chaotic_semantic_memory --skill adr-creation-d-o-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps software teams document architecture decisions by creating durable ADRs that capture scope, tradeoffs, and rationale for architecture-impacting changes.

Core Features & Use Cases

  • Structured ADRs: Create consistent ADR documents using the MADR template.
  • Traceability: Pull constraints from AGENTS.md and reuse templates to ensure completeness.
  • Lifecycle: Save ADRs under plans/adr/NNNN-short-title.md to maintain versioned records.

Quick Start

Draft an ADR by outlining scope, pulling constraints from AGENTS.md, drafting with references/madr-template.md, checking with references/review-checklist.md, and saving as plans/adr/NNNN-short-title.md.

Frequently Asked Questions about adr-creation

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

FAQPage Schema
How do I create an architecture decision record that captures tradeoffs and constraints?

To create an architecture decision record, draft the scope, pull constraints from AGENTS.md, draft with the MADR template, verify with a review checklist, and save as a versioned file. This ensures your ADR captures tradeoffs and rationale.

What is the MADR workflow for documenting architectural decisions?

The MADR workflow for architectural decisions involves pulling constraints from AGENTS.md, drafting with a MADR template, checking against a review checklist, and saving to a versioned plans directory. It enforces structured documentation of tradeoffs.

When do I need to write an ADR for software architecture changes?

You need to write an ADR when making architecture-impacting changes that require documented scope, tradeoffs, and rationale. It is applied across requirements gathering, architecture review, and governance workflows to maintain durable records.

How should I structure ADR documents for consistent governance and traceability?

Structure ADR documents using the MADR template to ensure consistency and traceability. Save them under plans/adr/NNNN-short-title.md to maintain versioned records that pull constraints from AGENTS.md for completeness.

Does this ADR creation process require specific environment files to function?

Yes, the ADR creation process requires AGENTS.md to pull constraints, a MADR template for drafting, and a review checklist for validation. These references ensure the architectural decision record captures all necessary governance information.

What is the best way to maintain versioned records of architectural decisions?

The best way to maintain versioned records of architectural decisions is to save ADRs under plans/adr/NNNN-short-title.md. This lifecycle approach ensures consistent governance and traceability using the MADR workflow.