Where does the write_adr skill save documentation?

This skill is configured to fill and maintain a DECISIONS.md file located within your project repository.

Why should I use this skill instead of writing ADRs manually?

The write_adr skill ensures a consistent format and prompts the AI to consider and document alternatives and consequences that might be overlooked during manual documentation.

Does this skill link ADRs to other documentation?

Yes, the skill includes a step to link newly created ADRs into other relevant documentation to ensure they are discoverable by the team.

What is an ADR in software development?

An ADR (Architectural Decision Record) is a short text file that captures a significant architectural decision, the context in which it was made, and the consequences it has for the project.

ADR Architect

Name: ADR Architect
Author: CheekyCodexConjurer

byCheekyCodexConjurer

コンテンツ管理

Documents architectural decisions with context, alternatives, and consequences to maintain a clear record of technical evolution.

概要

The write_adr skill streamlines the creation of Architectural Decision Records (ADRs) within your project repository. It helps engineering teams capture the 'why' behind technical choices by populating a structured DECISIONS.md file with essential metadata, including the problem context, chosen solution, alternatives considered, and long-term consequences. This skill is invaluable for maintaining project transparency, simplifying developer onboarding, and providing an audit trail for complex system designs.

主な機能

Alternative analysis tracking for decision transparency
Automated cross-linking of decisions in project documentation
Standardized formatting for technical decision histories
Structured ADR template generation in DECISIONS.md
0 GitHub stars
Comprehensive capture of context, rationale, and consequences

ユースケース

Capturing the rationale for database schema changes or infrastructure migrations
Onboarding new developers by providing a clear history of technical design choices
Documenting the transition between different frameworks or architectural patterns

概要

主な機能

Alternative analysis tracking for decision transparency
Automated cross-linking of decisions in project documentation
Standardized formatting for technical decision histories
Structured ADR template generation in DECISIONS.md
0 GitHub stars
Comprehensive capture of context, rationale, and consequences

ユースケース

Capturing the rationale for database schema changes or infrastructure migrations
Onboarding new developers by providing a clear history of technical design choices
Documenting the transition between different frameworks or architectural patterns