scenario

Generates frontline operations scenario playbooks with three-tier contingency plans.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/natthasath/natthasath-marketplace --skill scenario-natthasath
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scenario
Source: https://github.com/natthasath/natthasath-marketplace/tree/main/plugins/productive/skills/scenario
Command: npx skills add https://github.com/natthasath/natthasath-marketplace --skill scenario-natthasath

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Frontline teams at events, retail stores, call centers, clinics, and warehouses often freeze when unexpected situations occur because no one prepared fallback plans. This Skill produces a printable scenario playbook covering 12 common operational failure categories with actionable Plan A/B/C responses. ## Core Features & Use Cases - 12 Scenario Categories: Systematically covers Capacity, Missing Information, Identity Verification, Duplicate, Registration/Record, Walk-in, Group, Wrong Target, Special Case, Timing, Queue/Crowd, and Manual Override situations. - Three-Tier Response Plans: Designs Plan A (standard), Plan B (backup), and Plan C (emergency escalation) for each scenario with measurable escalation triggers, responsible persons, and required tools. - Priority Ranking: Scores scenarios by Impact × Frequency to identify which plans to rehearse first, output as a printable markdown cheat sheet. - Use Case: Before a 500-person conference, invoke the skill to generate a registration-desk playbook covering forgotten QR codes, duplicate check-ins, walk-ins, and system outages with clear escalation criteria. ## Quick Start Invoke /scenario with a description of your operation, such as planning frontline contingency plans for a 300-person event registration desk with two staff and one check-in system.

Frequently Asked Questions about scenario

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a contingency plan for frontline event staff?▼

Invoke the skill with your event description, expected scale, and available systems. It generates a playbook covering 12 common scenario categories with Plan A/B/C responses, escalation criteria, and responsible persons for each situation.

What scenarios should a call center or retail store prepare for?▼

The framework covers 12 categories: capacity overload, missing documents, identity verification, duplicates, registration mismatches, walk-ins, group handling, wrong target, special cases, timing issues, queue control, and manual overrides.

How are scenario priorities calculated in the playbook?▼

Priority equals Impact multiplied by Frequency. High-impact scenarios like system outages get full plans even if rare, while low-impact frequent issues may only need a Plan A. Red and yellow scenarios require all three plan tiers.

Can I use my existing SOP or incident reports as input?▼

Yes, you can attach existing SOPs, floor plans, flowcharts, previous scenario tables, or incident reports. The skill uses them as a base and fills in Plan A/B/C responses rather than rebuilding from scratch.

Does the scenario skill trigger automatically during conversation?▼

No, it only runs when explicitly invoked via /scenario. The disable-model-invocation flag prevents automatic triggering, so you control exactly when the playbook generation starts.