sdd-adr

Generate MADR-standard Architecture Decision Records with rationale, alternatives, and consequences.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/taiyousan15/taisun_agent --skill sdd-adr-taiyousan15
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-adr
Source: https://github.com/taiyousan15/taisun_agent/tree/main/.claude/skills/sdd-adr
Command: npx skills add https://github.com/taiyousan15/taisun_agent --skill sdd-adr-taiyousan15

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of Architecture Decision Records (ADRs) in the standard MADR format, ensuring that all technical decisions are well-documented with their rationale, alternatives, and consequences.

Core Features & Use Cases

  • Generate ADRs: Create new ADRs based on a title, spec-slug, and optional target directory.
  • Enforce Standards: Ensures adherence to MADR format, requires at least three alternatives, and links to requirements.
  • Use Case: When deciding on a new authentication method for a project, use this skill to generate an ADR detailing the chosen method (e.g., JWT), the alternatives considered (e.g., OAuth, session cookies), and the reasons for the final decision.

Quick Start

Generate an Architecture Decision Record for adopting JWT as an authentication method for the 'google-ad-report' specification.

Frequently Asked Questions about sdd-adr

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

FAQPage Schema
How do I generate an Architecture Decision Record to document technical choices?

To generate an Architecture Decision Record, provide a title, spec-slug, and optional target directory. The skill outputs a MADR-formatted document that captures your technical choices, rationale, alternatives, and consequences automatically.

What is the MADR standard for writing architecture documentation?

MADR is a standard format for Architecture Decision Records that enforces best practices by requiring at least three alternatives and linking to relevant requirements. It structures technical decisions with clear rationale and consequences to manage technical debt effectively.

How do I enforce including alternatives and requirements in my decision records?

Enforce alternatives and requirements in decision records by using a MADR-compliant generation process. This skill automatically validates that at least three alternatives are documented and links each record to relevant requirements using the REQ-xxx naming convention.

Does this approach require linking decision records to specific requirement IDs?

Yes, linking decision records to specific requirement IDs is enforced. The generation process requires references to relevant requirements using the REQ-xxx format, ensuring every technical decision traces back to documented project requirements.

Can I automate ADR numbering and slug generation for a new documentation directory?

Automate ADR numbering and slug generation by running this skill when creating records. It handles automated sequential numbering, generates URL-friendly slugs from titles, and updates the README file in your ADR directory to maintain an index.

When should I not use MADR for documenting technical debt and decisions?

Avoid using MADR for technical debt tracking when a decision lacks at least three viable alternatives. The standard enforces comparing multiple options, so isolated or purely operational changes without architectural impact may not require a formal decision record.