scenario-rehearsal

Simulates real usage scenarios to validate designs, requirements, skills, and code before execution.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/HACK-WU/skills --skill scenario-rehearsal-hack-wu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scenario-rehearsal
Source: https://github.com/HACK-WU/skills/tree/main/skills/scenario-rehearsal
Command: npx skills add https://github.com/HACK-WU/skills --skill scenario-rehearsal-hack-wu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Design flaws, requirement gaps, skill quality issues, and code defects are often discovered only after development or release, causing costly rework. This Skill catches them early by mentally rehearsing realistic scenarios against the artifact before anything is built or run. ## Core Features & Use Cases - Four Rehearsal Modes: Validates design documents (key design point feasibility), requirement documents (completeness, consistency, acceptance reachability), Agent Skills (trigger accuracy, instruction completeness), and code (desk-check tracing of state evolution with concrete scenario instances). - Strategy Profiles: Auto-enables focused validation dimensions for CRUD APIs, transactions/state machines, batch sync, realtime messaging, refactoring/migration, concurrency, bug fixes, new features, and optimizations. - Structured Findings: Produces severity-graded problem reports (blocker/warning/suggestion) with mermaid sequence diagrams, flowcharts, and optional persistence to requirement management via the req CLI. - Use Case: After finishing a technical design for an order system, ask for a rehearsal to discover that duplicate payment callbacks lack idempotency handling and that rejected reviews never notify users—before any code is written. ## Quick Start Ask the AI to rehearse your artifact, for example: walk through this design document and simulate the main user scenarios to find feasibility problems.

Frequently Asked Questions about scenario-rehearsal

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

FAQPage Schema
How do I validate a technical design before writing code?

Run a scenario rehearsal on the design document: it extracts roles and scenarios, builds a design-point coverage matrix, then walks each role through normal, exception, and edge paths. Findings are reported as blocker, warning, or suggestion with mermaid diagrams.

What is the difference between scenario rehearsal and code review?

Code review statically scans code across quality dimensions, while scenario rehearsal simulates execution along a timeline with concrete input values, tracking state evolution and comparing expected versus actual end states. Rehearsal catches issues like partial-failure dirty state that static review often misses.

Can scenario rehearsal validate requirement documents without a design?

Yes. When only a requirement document exists, it switches to requirement mode and checks scenario completeness, acceptance criteria reachability, requirement consistency, role-requirement alignment, boundary coverage, and terminology consistency.

Does scenario rehearsal actually execute the code?

No. It performs desk-check tracing based on static reasoning, and conclusions are always labeled as rehearsal results rather than executed verification. When behavior cannot be statically determined, it flags items for runtime verification via demo or e2e testing.

When should I use scenario rehearsal for an Agent Skill?

Use it after writing or updating a SKILL.md to verify trigger accuracy, instruction completeness, example quality, workflow soundness, and resource reference integrity before publishing the skill.