skills.rest
wilfoz
wilfozCOMMUNITY
Explore all skills by this author →
GitHub

create-adr

Create architecture decision records in MADR, Nygard, or Y-Statement formats.

Updated May 6, 2026
Search Tags:#architecture#documentation#software design#decision record#system architecture
One-click install
npx skills add https://github.com/wilfoz/plan_game --skill create-adr-wilfoz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-adr
Source: https://github.com/wilfoz/plan_game/tree/main/.claude/skills/create-adr
Command: npx skills add https://github.com/wilfoz/plan_game --skill create-adr-wilfoz

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the process of recording and managing architectural decisions, ensuring that teams can quickly create clear, consistent, and traceable ADRs.

Core Features & Use Cases

  • Automated ADR Creation: Generate well-structured architecture decision records based on user input or existing context.
  • Supports Multiple Formats: Produce MADR, Nygard, or Y-Statement formats to suit team preferences.
  • Use Case: A team deciding on a database technology can quickly document their choice, including alternatives and consequences, following best practices without manual formatting.

Quick Start

Ask the AI to create an ADR for choosing Kubernetes for container orchestration and specify your preferred format and decision status.

Frequently Asked Questions about create-adr

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

FAQPage Schema
How do I create an architecture decision record for my software design choices?▼

You can create an architecture decision record by asking the AI to document a specific technical choice, such as selecting Kubernetes for container orchestration. It automatically structures the decision context, options considered, and outcomes into a consistent template.

What formats are supported for documenting system architecture decisions?▼

When documenting system architecture decisions, you can choose between MADR, Nygard, or Y-Statement formats. This allows teams to adopt the documentation style that best fits their existing software design conventions and preferences.

When do I need to document technical choices using an architecture decision record?▼

You need an architecture decision record when your team makes significant technical choices regarding infrastructure, technical libraries, or design patterns. It ensures the decision context, alternatives, and consequences are well-documented and traceable for future reference.

Can I link and version architecture decision records for future reference?▼

Yes, architecture decision records are properly versioned and linked for future reference. This ensures that as your system architecture evolves, the history of technical choices and their outcomes remains traceable and accessible to the team.

What is the best way to maintain consistent style across multiple architecture decision records?▼

The best way to maintain consistent style across multiple architecture decision records is to use structured templates. This Skill enforces consistent formatting for decision context, options, and outcomes, eliminating manual formatting errors and ensuring traceable documentation.

Related Skills

Explore More Software Engineering Skills→
0xrafasec0xrafasec
9

adr

Create Architecture Decision Records as markdown files with context and rationale.

Community
Intermediate
EnigmaWUEnigmaWU
1

document-architectural-decisions

Write structured 12-field Architectural Decision Records using Kruchten's decision ontology.

Community
Advanced
1479089714790897
7

kwp-engineering-architecture

Create and evaluate Architecture Decision Records documenting technical trade-offs.

Community
Intermediate
bybren-llcbybren-llc
395

confluence-docs

Create standardized ADR, runbook, and architecture documentation templates.

Official
Intermediate