Why use the Nygard format for documentation?

The Michael Nygard format is a lightweight, industry-standard template that ensures all critical components of a decision are captured consistently and concisely.

What is an Architecture Decision Record (ADR)?

An ADR is a short text file that captures a significant architectural decision, including its context, the actual decision made, and the resulting consequences and trade-offs.

How does this skill handle decision status updates?

The skill tracks the lifecycle of decisions, allowing you to mark ADRs as Proposed, Accepted, Deprecated, or Superseded by newer records as the project evolves.

When should I use the develop-adr skill?

Use this skill whenever you make a technical choice that affects system architecture, technology selection, or development patterns that future team members will need to understand.

Architecture Decision Records (ADR)

Name: Architecture Decision Records (ADR)
Author: LuodashiV5

byLuodashiV5

•

학습 및 문서화

Generates structured documentation for significant technical decisions using the industry-standard Michael Nygard ADR format.

This skill empowers development teams to capture the underlying rationale behind critical architectural choices, technology selections, and system patterns. By automating the creation of Architecture Decision Records (ADRs) in the Nygard format, it ensures that institutional knowledge is preserved and that the 'why' behind complex technical trade-offs is clearly documented for current and future stakeholders. It is particularly useful when establishing system constraints, choosing frameworks, or defining development patterns that require team-wide alignment.

주요 기능

01Detailed analysis of positive and negative consequences

02Active voice decision articulation for clarity

03Standardized Nygard ADR format implementation

04Sequential numbering and lifecycle status tracking

05Comprehensive context and rationale capture

061 GitHub stars

사용 사례

01Documenting the selection of a primary database or cloud service provider

02Defining architectural patterns for microservices or frontend state management

03Capturing trade-offs when pivoting between different technology stacks

주요 기능

01Detailed analysis of positive and negative consequences

02Active voice decision articulation for clarity

03Standardized Nygard ADR format implementation

04Sequential numbering and lifecycle status tracking

05Comprehensive context and rationale capture

061 GitHub stars

사용 사례

01Documenting the selection of a primary database or cloud service provider

02Defining architectural patterns for microservices or frontend state management

03Capturing trade-offs when pivoting between different technology stacks