원클릭으로
adr-writer
Use when writing or updating an ADR for a specific technical decision.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when writing or updating an ADR for a specific technical decision.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when creating, reviewing, or restructuring AGENTS.md, CLAUDE.md, or scoped instruction files for a project, including root, feature, service, backend, or domain-level guidance.
Use when a new app plan already exists and needs an interactive kickoff into setup decisions and first tasks.
Use at task handoff, milestone review, or after implementation when project lessons may be reusable for future apps, toolkit docs, AGENTS/CLAUDE instructions, skills, or templates.
Use when a greenfield app needs a mature foundation plan before implementation.
Use when explicitly defining MVP scope, exclusions, beta screens, states, or success metrics.
Use when drafting pull request descriptions, end-of-session handoffs, reviewer notes, verification summaries, or stop-start task updates.
| name | adr-writer |
| description | Use when writing or updating an ADR for a specific technical decision. |
Use this skill to create concise architecture decision records.
references/adr-templates.md; fall back to docs/foundation/adr-templates.md or templates/adr-template.md when installed.docs/adr/, use the next available ADR number.# ADR NNNN: Title
Date:
Status: Proposed | Accepted | Superseded
## Context
## Decision
## Consequences
- Positive:
- Negative:
- Follow-up:
## Revisit When
-
Do not invent certainty. Label assumptions and missing expert review.