run-a-procurement-tabletop
Rehearse a procurement failure to expose decision, authority, evidence, and continuity gaps. Use when teams need to test plans for supplier, payment, integrity, or service disruption without causing live harm.
ソース情報
- リポジトリ
- protosphinx/sphinxstack
- ソースの最終更新活動
- 2026年7月29日 13:55
- 検出された SKILL.md の言語
- 英語
- スター
- 3
- フォーク
- 0
インストール方法
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
ソースファイルを確認
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
ファイルエクスプローラー
2 ファイルSKILL.md を表示中
SKILL.md
ソースの指示 · 読み取り専用プレビュー- name
- run-a-procurement-tabletop
- category
- start
- description
- Rehearse a procurement failure to expose decision, authority, evidence, and continuity gaps. Use when teams need to test plans for supplier, payment, integrity, or service disruption without causing live harm.
# run-a-procurement-tabletop
## Procedure
1. Define objectives, scope, scenario, participants, authority, safety boundary, and evidence to collect.
2. Invite procurement, finance, operations, security, legal, communications, and service owners as relevant.
3. Establish the known starting state, assumptions, time compression, and no-fault learning rule.
4. Deliver injects covering incomplete evidence, supplier pressure, conflicts, payment change, service failure, and executive escalation.
5. Ask participants to state decisions, authority, information needs, actions, and communications at each point.
6. Record gaps in policy, ownership, data, contracts, alternatives, controls, and recovery.
7. Debrief immediately and distinguish validated strengths from untested or failed assumptions.
8. Assign corrective actions and schedule targeted retests.
## Guardrails
- Do not contact real suppliers, move money, change access, or trigger production actions.
- Never use the exercise to evaluate or embarrass individual performance.
- Protect sensitive scenarios, personal data, security weaknesses, and allegations.
## Done
- An exercise report and record capture scenario, decisions, authority, evidence, and observed gaps
- A corrective-action register names owners, due dates, priority, and acceptance checks
- Retest scope and approval are scheduled
GitHubで見る