ad

Create numbered Architecture Decision Records in the Michael Nygard format.

2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/stratus/my-claude --skill ad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ad
Source: https://github.com/stratus/my-claude/tree/main/skills/ad
Command: npx skills add https://github.com/stratus/my-claude --skill ad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffold standardized Architecture Decision Records (ADRs) to capture rationale, context, and outcomes for architectural choices.

Core Features & Use Cases

  • Create ADRs in the Michael Nygard format to document decisions
  • Automatically assign numbering and file structure under docs/decisions
  • Cross-reference and supersede previous ADRs to maintain traceability

Quick Start

Create a new ADR by answering the prompts; the system will scaffold docs/decisions/ with a properly numbered file.

Frequently Asked Questions about ad

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 (ADR) documents the rationale, context, and outcomes of a software architecture choice. You need to create an ADR when selecting new technologies, making design trade-offs, or establishing cross-project architectural standards.

How do I scaffold a new Architecture Decision Record under my project directory?

To scaffold an Architecture Decision Record, answer the interactive prompts to automatically generate a properly numbered file in the docs/decisions directory using the standard Michael Nygard format, complete with required frontmatter and naming conventions.

Does this ADR scaffolding process use the Michael Nygard format for documentation?

Yes, the ADR scaffolding process uses the Michael Nygard format to structure your architecture documentation. This standardizes the rationale, context, and outcomes for each design choice across projects and teams.

Can I supersede and cross-reference previous architectural decisions to maintain traceability?

Yes, you can cross-reference and supersede previous architectural decisions to maintain traceability. The system automatically assigns numbering to link new ADRs with prior technology selections and design trade-offs.

What is the best way to standardize architecture rationale across multiple development teams?

The best way to standardize architecture rationale across teams is to scaffold ADRs in a shared docs/decisions directory. This enforces consistent file structures, numbering, and frontmatter for all design trade-offs and technology selections.