What is the difference between Traditional ADRs and Y-statements?

Traditional ADRs are detailed, individual files used for major architectural decisions, whereas Y-statements are concise, single-sentence entries optimized for lightweight decision logging in a single file.

Can this skill detect my existing documentation format?

Yes, on its first use, the skill automatically scans your repository for existing ADR folders or decision logs to determine whether to use the Traditional or Y-statement format.

How does it handle superseded decisions?

The skill automates the process of marking old decisions as 'Superseded', adding links to the new decision, and ensuring the new record references the documentation it replaces.

An Architecture Decision Record (ADR) is a document that captures an important architectural decision, including the context in which it was made, the rationale behind it, and the resulting consequences.

Architecture Decision Records (ADR) Manager

Name: Architecture Decision Records (ADR) Manager
Author: lhohan

bylhohan

•

学習とドキュメンテーション

Documents and manages architectural decisions using standardized ADR and Y-statement formats to maintain a clear technical history.

This skill empowers developers and AI agents to systematically document complex architectural choices using either comprehensive Traditional ADRs or lightweight Y-statement formats. It streamlines the documentation process by auto-detecting existing repository conventions, providing standardized templates, and managing the entire lifecycle of a decision—from proposal to supersession. By capturing the 'why' behind technical choices, it ensures that trade-offs, context, and consequences are preserved for future reference, making it an essential tool for maintaining long-term project health and facilitating developer onboarding.

主な機能

01Guided creation of traditional multi-file ADRs with status and rationale sections

02Automatic detection of project-specific ADR or Y-statement formats

03Intelligent search and retrieval of past architectural reasoning and trade-offs

04Automated linking and status management when superseding old decisions

05Standardized templates for initializing new decision logs and individual records

063 GitHub stars

ユースケース

01Maintaining a lightweight, single-file log of tactical technical decisions using Y-statements

02Auditing historical architectural context to understand why specific system boundaries were established

03Documenting the rationale and trade-offs for choosing specific technology stacks or frameworks

主な機能

01Guided creation of traditional multi-file ADRs with status and rationale sections

02Automatic detection of project-specific ADR or Y-statement formats

03Intelligent search and retrieval of past architectural reasoning and trade-offs

04Automated linking and status management when superseding old decisions

05Standardized templates for initializing new decision logs and individual records

063 GitHub stars

ユースケース

01Maintaining a lightweight, single-file log of tactical technical decisions using Y-statements

02Auditing historical architectural context to understand why specific system boundaries were established

03Documenting the rationale and trade-offs for choosing specific technology stacks or frameworks