Skip to main content

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.

Informations de source

Dépôt
protosphinx/sphinxstack
Dernière activité de la source
29 juillet 2026 à 13:55
Langue détectée de SKILL.md
anglais
Étoiles
3
Forks
0

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Explorateur de fichiers
2 fichiers

Affichage de SKILL.md

SKILL.md
Instructions source · Aperçu en lecture seule
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
Voir sur GitHub