adr

You document architectural decisions using Architecture Decision Records (ADRs) to ensure clarity, traceability, and shared understanding of project evolution. This skill systematically records problems, considered options, final decisions, and rationales in a standardized template.

Creating an Architecture Decision Record from conversation context involves parsing user input and tagged files to inform the ADR content. This skill generates records in the docs/decisions/ directory, following specific numbering and content guidelines.

Managing superseded ADRs and preventing duplicates involves scanning existing records to avoid redundancy and updating statuses for superseded decisions. This skill supports cross-linking and status updates to maintain accurate architectural documentation.

You need to write an Architecture Decision Record when a significant change to the system's architecture is proposed. Use this skill to create an ADR documenting the problem, considered options, the final decision, and its rationale.

Yes, this Architecture Decision Record generation skill works without external dependencies. It operates independently to parse conversation context and user input, generating structured ADRs in Korean within the docs/decisions/ directory.

The limitation of using standardized templates for architecture decision records is that output is constrained to specific numbering and content guidelines. This skill generates ADRs in Korean, which may require translation for non-Korean speaking teams.