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.

Informações da origem

Repositório
protosphinx/sphinxstack
Última atividade na origem
29 de julho de 2026 às 13:55
Idioma detectado do SKILL.md
inglês
Estrelas
3
Forks
0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos
2 arquivos

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
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 no GitHub