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
- 포크
- 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에서 보기