菜单
Use when a hard-to-reverse architectural decision is made — during plan-writer, a refactor, a doubt-driven trade-off, or a handoff PAUSE — to write it as an immutable ADR in docs/architecture/adr/ from the ADR template, or to supersede an existing one.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/CaioWF/keel --skill adr-writer命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when designing the structure of a feature or module (in the plan phase, or when refactoring) to apply language-agnostic engineering principles — Clean Architecture, SOLID, testing strategy, and tactical DDD. Container of guides; each concept is a companion.
Use when implementation is complete, gates pass, and you need to decide how to integrate the work — presents structured options (merge, PR, keep, discard) and handles the chosen workflow, including worktree cleanup. Closes the SDD cycle after review-and-simplify.
Use when PAUSING/ending a session (writes the current state to docs/STATE.md to resume later) or when RESUMING (reads docs/STATE.md and the active spec, recomposes context, and proposes the next step). Maintains continuity across human and agent sessions.
基于 SOC 职业分类
正在显示 SKILL.md
| name | adr-writer |
| description | Use when a hard-to-reverse architectural decision is made — during plan-writer, a refactor, a doubt-driven trade-off, or a handoff PAUSE — to write it as an immutable ADR in docs/architecture/adr/ from the ADR template, or to supersede an existing one. |
When: a decision that is hard to reverse has been made (or is about to be). ADRs are durable; docs/STATE.md is volatile. Never let a structural decision live only in STATE, a commit message, or the chat.
Template: docs/architecture/adr/_template.md.
Output: docs/architecture/adr/NNNN-kebab-case-title.md.
Write one when the decision is hard to reverse AND has consequences beyond the current feature:
Skip it for reversible or local choices (a variable name, a helper's location, a one-file refactor). Those belong in the code and, if in flight, in STATE. When unsure, ask the user rather than growing the ADR log with noise.
NNNN = highest existing ADR in docs/architecture/adr/ + 1, zero-padded to 4 digits, sequential and never reused. _template.md and index.md are not ADRs._template.md and fill every section against what was actually decided:
proposed while the user has not agreed; accepted once they have.YYYY-MM-DD).type: adr, title, and a one-sentence description, so the SessionStart okf-index hook surfaces it. Cross-link related concepts with relative markdown links ([Title](../../design-notes/XXXX.md)), and link back from the spec/plan that motivated it.node .specify/gates/okf-build-index.mjs build docs — otherwise the freshness gate blocks the commit.ADRs are append-only. An accepted ADR is a historical record of what was decided and why, at that time — editing it destroys the reasoning trail that makes it worth keeping.
To change a decision:
Context states what changed since the old one (new constraint, new evidence, the trade-off went bad).Status line only: superseded by ADR-XXXX. Touch nothing else in it.The single exception: an ADR still in proposed status has not been agreed to yet, so it may be edited freely until it becomes accepted.
Fixing a typo or a broken link is not "changing a decision" — that is fine.
handoff — writes the volatile STATE; delegates durable decisions here.architecture — the agnostic principles behind most decisions worth recording.plan-writer — the phase where boundary/dependency decisions usually surface.doubt-driven-development — a legitimate trade-off found there gets recorded as an ADR.