decision-records
适用于任何项目的轻量级决策记录：记录那些难以撤销或重新争论的决策——决策内容、备选方案、原因和可逆性——仅追加，不重写而是以新记录取代，保存在项目所在的位置，让下一次会话继承决策依据，而不仅是结论。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:ChenneyZhuang/decision-records#a50510efae648021d5e0cf74f0a86a68df65a8eeDecision Records 以 decision-records 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Decisions without recorded reasons get re-litigated forever — every few weeks someone reopens the same question because nobody remembers why it was closed.
没有记录理由的决策会被反复重新争论——每隔几周就有人重开同一个问题，因为没人记得它当初为什么被关掉。
"Use X" is a fact that goes stale. "Use X because Y; we rejected Z" is a decision the next person can respect — or consciously revisit with full information. The expensive decisions are the ones that are expensive to reverse or expensive to re-argue; those are the ones worth one short record.
"用 X"是一个会过期的事实。"用 X，因为 Y；否决了 Z"是一个下个人可以尊重的决策——或者带着完整信息有意识地重开。昂贵的决策是那些难以回退或难以重新争论的决策——它们才值得一条简短的记录。
### 2026-09-14 — Use plan B for syncing
- Decision: sync via UUID, not timestamps
- Alternatives: timestamps (rejected: clock skew across devices)
- Why: IDs survive offline edits; timestamps silently drop concurrent rows
- Reversible? yes — migration script exists
No template ceremony, no approval workflow. One file (decisions.md) or one section in the project's existing doc, next to the work it governs.
不要模板仪式，不要审批流程。一个文件（decisions.md）或项目现有文档里的一节，放在它治理的工作旁边。
git clone https://github.com/ChenneyZhuang/decision-records ~/.claude/skills/decision-records
One SKILL.md, zero dependencies. MIT. v0.1.0.
单个 SKILL.md，零依赖。MIT 许可，v0.1.0。