Does it follow a specific naming convention?

Yes, it uses a 4-digit sequence followed by a short English summary, such as 0003-tts-engine-abstraction.md.

Can I include implementation details or code snippets?

The skill is designed to capture high-level architectural facts and decisions; it specifically avoids implementation details or code fragments to keep the documentation focused.

What sections are included in the generated ADR?

The generated Markdown includes sections for Title, Context (background/problems), Decision (chosen solution), Consequences (pros/cons), and Alternatives.

Where does this skill save the ADR files?

All ADR files are automatically saved to the docs/adr/ directory in your project repository for centralized access.

Does it handle existing ADRs?

Yes, the skill scans existing files to determine the next logical sequence number and checks for contradictions with previous decisions.

ADR Writer

Name: ADR Writer
Author: Hakuya5247

byHakuya5247

학습 및 문서화

Generates and manages Architecture Decision Records (ADRs) to track key design choices within a standardized documentation workflow.

소개

The adr-writer skill automates the process of documenting significant architectural decisions within a software project by enforcing a standardized format and storage location in the docs/adr/ directory. It ensures team alignment by capturing the context, decision rationale, and potential consequences of design choices, while maintaining a clear, chronological history through sequential file naming. This tool is essential for long-term project maintainability, helping teams understand the 'why' behind specific technical paths and preventing the loss of institutional knowledge as the codebase evolves.

주요 기능

Automatic sequential file numbering for chronological tracking
Standardized ADR creation using structured Markdown templates
Centralized storage management within docs/adr/
0 GitHub stars
Requirement-based sections for Context, Decision, and Consequences
Consistency validation against existing architectural records

사용 사례

Tracking historical context for major infrastructure or database changes
Recording the rationale for specific API design patterns
Documenting the transition to a new framework or library

소개

주요 기능

Automatic sequential file numbering for chronological tracking
Standardized ADR creation using structured Markdown templates
Centralized storage management within docs/adr/
0 GitHub stars
Requirement-based sections for Context, Decision, and Consequences
Consistency validation against existing architectural records

사용 사례

Tracking historical context for major infrastructure or database changes
Recording the rationale for specific API design patterns
Documenting the transition to a new framework or library