document-a-purchase-decision
Record a purchasing decision with alternatives, evidence, authority, and follow-up conditions. Use when a team needs a durable rationale for an award, renewal, exception, or no-buy decision.
来源信息
- 仓库
- protosphinx/sphinxstack
- 最近来源活动
- 2026年7月29日 13:55
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 3
- Forks
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
2 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- document-a-purchase-decision
- category
- write
- description
- Record a purchasing decision with alternatives, evidence, authority, and follow-up conditions. Use when a team needs a durable rationale for an award, renewal, exception, or no-buy decision.
# document-a-purchase-decision
## Procedure
1. Identify the decision, date, authority, participants, declared conflicts, and governing process.
2. Restate the need, scope, constraints, and mandatory requirements.
3. List viable options, including no purchase, extension, internal delivery, or phased action.
4. Summarize evaluation evidence, cost basis, risks, exceptions, and unresolved uncertainty.
5. Explain the selected option and why alternatives were rejected without inventing certainty.
6. Record conditions, approvals, dependencies, review dates, and implementation owners.
7. Link source artifacts while applying access and retention controls.
8. Obtain approval and preserve the decision as a versioned record.
## Guardrails
- Do not rewrite history after the outcome is known.
- Separate evaluator judgment, verified fact, supplier claim, and assumption.
- Exclude unnecessary personal, confidential, and legally privileged detail.
## Done
- A decision record traces the outcome to options, evidence, risks, and authority
- Conditions, exceptions, owners, and review triggers are explicit
- Approval and links to controlled source records are preserved
在 GitHub 查看