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.

Datos de origen

Repositorio
protosphinx/sphinxstack
Última actividad en el origen
29 de julio de 2026 a las 13:55
Idioma detectado de SKILL.md
inglés
Estrellas
3
Forks
0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos
2 archivos

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
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
Ver en GitHub