skills.rest
tmalcolm-0607
tmalcolm-0607COMMUNITY
Explore all skills by this author →
WebsiteGitHub

mad-adr

Create Architecture Decision Records compliant with MADR 4.0 format and manage their lifecycle statuses.

Updated May 7, 2026
Search Tags:#adr#governance#technical-documentation#software-architecture#architecture-decisions#madr#decision-tracking
One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill mad-adr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mad-adr
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/mad-adr
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill mad-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of losing critical context and rationale for significant technical decisions, ensuring teams can easily reference past choices, avoid repeating work, and maintain a clear audit trail of architectural choices.

Core Features & Use Cases

  • MADR 4.0 Compliant ADR Management: Create, list, and update Architecture Decision Records that follow the industry-standard MADR 4.0 format, including mandatory context, decision, and consequences sections plus optional RACI metadata for stakeholder tracking.
  • Decision Lifecycle Tracking: Manage full ADR status transitions (Proposed → Accepted → Rejected → Deprecated → Superseded) to keep decision records accurate as projects evolve and requirements change.
  • Use Case: When your engineering team is selecting a new inter-service messaging tool, use this Skill to document the decision rationale, alternatives evaluated, and team stakeholders consulted, so future team members can understand the choice without digging through old chat logs or meeting notes.

Quick Start

Use the mad-adr skill to create a new Architecture Decision Record for the decision to adopt EventBridge for inter-service messaging in your project.

Frequently Asked Questions about mad-adr

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

FAQPage Schema
What is an Architecture Decision Record and when do I need to document one?▼

An Architecture Decision Record captures significant technical architecture choices with full context, rationale, and consequences to prevent organizational knowledge loss. You need ADRs when evaluating technology selections, architectural patterns, or breaking system contract changes during software development.

How do I create a MADR 4.0 compliant Architecture Decision Record?▼

Create a MADR 4.0 compliant Architecture Decision Record by documenting mandatory context, decision, and consequences sections, plus optional RACI metadata for stakeholder tracking. This Skill applies sequential numbering and standard formatting to maintain consistent, auditable decision records.

Can I track the lifecycle status of architecture decisions as project requirements change?▼

Architecture decision lifecycle tracking manages full ADR status transitions from Proposed through Accepted, Rejected, Deprecated, and Superseded. This keeps decision records accurate as projects evolve and maintains clear superseding logic for auditable architectural choices.

What's the best way to document technology selection rationale for future engineering teams?▼

Document technology selection rationale by capturing alternatives evaluated, team stakeholders consulted, and decision consequences in a structured ADR. This prevents future engineers from digging through chat logs or meeting notes to understand why a specific architectural choice was made.

Does this Architecture Decision Record format support stakeholder accountability tracking?▼

MADR 4.0 Architecture Decision Records support stakeholder accountability tracking through optional RACI metadata. This allows engineering teams to record who is responsible, accountable, consulted, and informed for each significant technical decision.

How does superseding logic work when an architecture decision is replaced by a new one?▼

Superseding logic links a deprecated Architecture Decision Record to its replacement, transitioning the old record's status to Superseded while the new ADR is marked Accepted. This maintains a consistent, auditable chain of architectural choices as system requirements evolve.

Related Skills

Explore More Software Engineering Skills→
abdullah1854abdullah1854
1

algorithmic-art

Generate dated Markdown ADRs with Context, Decision, Consequences, Alternatives, and References.

Community
Intermediate
oiagorodriguesoiagorodrigues

create-adr

Generate a MADR-style Architecture Decision Record template with decision, context, drivers, options, and consequences.

Community
Intermediate
thincellerthinceller
4

write-adr

Creates ARC/ADR-style decision records documenting rationale, alternatives, statuses, and tradeoffs for technical choices in software projects.

Community
Intermediate
adolfoaranaes12adolfoaranaes12
2

sample-adr-poor

Translate requirements into architecture documentation with ADR creation and project-type detection.

Community
Basic