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.

소스 정보

저장소
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에서 보기