Back to Details

spec-loop-write-adr

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Use this skill for ADR writing only.
Before doing that work, read adr-format.md and apply it.
Read and apply project instructions such as 
AGENTS.md
when present.
This skill writes ADRs. It does not decide whether an ADR is required. Routing belongs to 
../spec-loop-plan-task/SKILL.md
.
The ADR being drafted or updated is the governing artifact for this skill.
Use the same ADR format whether or not a task artifact also exists.
本技能仅用于ADR撰写。
开展工作前，请阅读adr-format.md并遵循其规范。
若项目中存在
AGENTS.md
等说明文档，请阅读并遵循相关要求。
本技能负责撰写ADR，但不负责判断是否需要创建ADR。路由判断属于
../spec-loop-plan-task/SKILL.md
的职责范围。
正在起草或更新的ADR是本技能的核心管控工件。
无论是否存在任务工件，均需使用相同的ADR格式。

Mandatory clarification gate

强制澄清环节

Before drafting or revising the ADR as current truth, check whether any material unresolved question remains about the decision, decision criteria, trade-offs, credible options, or governing boundaries.
If yes, create only enough ADR structure to hold the topic and current evidence safely, then use 
../spec-loop-clarify-task/SKILL.md
before continuing. Do not wait for the user to ask for clarification explicitly.
Re-run this gate whenever later ADR drafting exposes a new material unresolved branch.
Before writing or revising, classify each input item into its proper section:
  • Context
    = pre-decision facts that would still be true under another credible alternative, such as requirements, constraints, current-state findings, scope boundaries, and explicit deferrals;
  • Alternatives
    = credible competing options;
  • Analysis
    = the clarified reasoning, accepted criteria, trade-offs, option comparisons, and brief reasons the chosen option won; and
  • Decision
    = the chosen outcome as a concise TL;DR, including any explicit deferrals or major retained boundaries that are part of the outcome.
Treat 
Analysis
as the ADR's authoritative decision-and-reason ledger. Do not repeat an 
Analysis
point elsewhere in decision-and-reason form.
When a task artifact exists, use its 
Research
, 
Analysis
, and other ADR-relevant sections such as 
Constraints
, 
Design
, and, when relevant, 
Scenario
as the primary ADR inputs. Otherwise use confirmed chat clarification and other current evidence.
在将ADR起草或修订为当前权威版本之前，请检查关于决策内容、决策标准、权衡因素、可行备选方案或管控边界是否存在任何未解决的实质性问题。
如果存在此类问题，请仅创建足够容纳主题和现有证据的ADR结构，然后使用
../spec-loop-clarify-task/SKILL.md
进行澄清，之后再继续。无需等待用户明确要求澄清。
后续ADR起草过程中若发现新的未解决实质性分支问题，请再次执行此环节。
在撰写或修订之前，请将每个输入项归类到对应的章节：
  • Context
    （背景）= 即使选择其他可行方案仍成立的决策前事实，例如需求、约束条件、当前状态调研结果、范围边界以及明确的延迟事项；
  • Alternatives
    （备选方案）= 可行的竞争选项；
  • Analysis
    （分析）= 明确的推理过程、已接受的标准、权衡因素、选项对比，以及所选方案胜出的简要理由；
  • Decision
    （决策）= 简洁的最终选择结论（TL;DR），包括作为决策结果一部分的任何明确延迟事项或主要保留边界。
将
Analysis
视为ADR中权威的决策与理由记录。 请勿在ADR的其他决策与理由部分重复
Analysis
中的内容。
若存在任务工件，请使用其
Research
（调研）、
Analysis
（分析）以及其他与ADR相关的章节（如
Constraints
（约束）、
Design
（设计），以及相关的
Scenario
（场景））作为ADR的主要输入。否则，请使用已确认的对话澄清内容和其他现有证据。