Promotion Incident Runbook

Use this skill before a promotion when a team needs explicit escalation cards for inventory, support queue, fulfillment, or budget risks.

Prerequisites

• - Python 3.9 or newer
• Authorized, redacted scenario rules
• A threshold, owner role, escalation target, allowed human actions, and stop conditions for each scenario

Inputs and outputs

Input is JSON matching examples/input.json. Output is a JSON runbook with reviewable incident cards and forbidden automatic actions.

Procedure

1. 1. Copy the scenario rules and remove customer identifiers and credentials.
2. Run python scripts/build_incident_runbook.py INPUT OUTPUT.
3. Check each threshold against the current platform, warehouse, and service rules before human execution.

Recovery and acceptance

Missing scenario fields must produce HOLD_MISSING_DATA. A complete sample must preserve all three scenario cards, evidence requirements, stop conditions, human_approval_required=true, and external_action_executed=false.

Permissions and privacy

This skill never changes prices, inventory, ads, listings, delivery promises, refunds, or consumer messages. Those actions remain with authorized operators after evidence review.