document-a-design-decision
Record a design choice with context, evidence, alternatives, tradeoffs, and review triggers. Use when a consequential or recurring decision should remain understandable after people, constraints, or implementation change.
来源信息
- 仓库
- protosphinx/sphinxstack
- 最近来源活动
- 2026年7月29日 13:55
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 3
- Forks
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
2 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- document-a-design-decision
- category
- write
- description
- Record a design choice with context, evidence, alternatives, tradeoffs, and review triggers. Use when a consequential or recurring decision should remain understandable after people, constraints, or implementation change.
# document-a-design-decision
## Procedure
1. State the decision, date, status, owner, scope, and affected users or systems.
2. Describe the context, user need, constraints, risks, and evidence available at decision time.
3. List credible alternatives, including no change, and why each was accepted or rejected.
4. Record the chosen option and the reasoning without rewriting uncertainty.
5. Document accessibility, privacy, content, technical, operational, and business tradeoffs.
6. Link research, prototypes, tests, metrics, designs, and implementation references.
7. Record dissent, assumptions, dependencies, and evidence gaps.
8. Define success, guardrails, reversal cost, and review triggers.
9. Obtain accountable approval and update status when superseded.
## Guardrails
- Do not invent consensus or erase contributors' disagreement.
- Keep sensitive evidence in controlled sources rather than the broad record.
- A decision record explains a choice; it does not replace validation.
## Done
- A design decision record preserves context, alternatives, evidence, choice, and tradeoffs
- Approval, dissent, assumptions, and links are verified
- Success and review triggers are scheduled
在 GitHub 查看