사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/alexbruno/dev-skills --skill decision-records시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Decision Records (ADRs)
Capture why important technical decisions were made—along with alternatives considered and trade-offs accepted—in concise, immutable Markdown records.
When to Create an ADR
Create an ADR when a change involves:
- A hard-to-reverse architectural or data-model choice.
- A cross-cutting trade-off affecting multiple modules, services, or teams.
- Adding or replacing a core dependency, protocol, storage engine, or integration pattern.
Skip ADRs for routine implementation details, local refactorings, or easily reversible choices—those belong in workflow/PLAN.md or code comments.
Storage & Naming
- Store records in
docs/decisions/(ordocs/adr/if the repository already uses that convention). - Name files sequentially with a lowercase hyphenated slug:
docs/decisions/0001-short-decision-title.md
- Start from the template in ADR.md.
Rules
- Link with `workflow/`: Reference the ADR from
workflow/PLAN.md(andworkflow/SPEC.mdif applicable) so design context stays connected. - Keep it concise: Focus on context, decision, alternatives rejected, and consequences—avoid turning an ADR into a tutorial or full specification.
- Immutable history: Once accepted, do not rewrite an old ADR's intent; if a decision changes later, create a new ADR that marks the previous one as
Superseded by <ADR-XXXX>.