Roleplay Scenario Builder

Design scenario packs that produce measurable behavior change, not scripted theater.

Confirm Inputs First

• If a current revenue-enablement-context exists, use it first for ICP, persona, stage, and messaging constraints. If not, ask for only the highest-impact missing context.
• Confirm target role: SDR, AE, SE, AM, or manager.
• Confirm capability focus: discovery, demo, commercial conversation, or objection handling.
• Confirm scenario context: segment, buyer persona, and deal stage.
• Confirm difficulty level: baseline, stretch, or advanced.
• Confirm scoring expectations: pass/fail, numeric rubric, or qualitative feedback.

If inputs are incomplete, ask only for missing essentials. If needed, proceed with labeled assumptions.

Read The Right Reference

• Read references/roleplay-scenario-framework.md before generating scenarios.

Default Workflow

1. Define the behavior target and anti-patterns to avoid.
2. Choose scenario archetypes and difficulty progression from the reference.
3. If real call or objection evidence is available, ground scenarios in anonymized field patterns.
4. Create scenario brief for participant, buyer persona, and facilitator.
5. Add realistic tension points, curveballs, and decision moments.
6. Provide scoring prompts aligned to observable behaviors.
7. Add debrief prompts that convert outcomes into next-practice actions.

Tool Notes

• Keep scenario generation tool-agnostic by default.
• If LMS or coaching platforms exist, format outputs to their schema only when requested.

Output Contract

• Scenario Set: 3-5 scenarios with increasing difficulty.
• Participant Brief: context, objective, constraints, and success criteria.
• Facilitator Guide: timing, escalation cues, and prompts.
• Buyer Persona Script: likely questions, concerns, and pushback.
• Scoring Prompts: observable pass/fail markers or numeric criteria.
• Debrief Guide: reflection questions and next-practice actions.

Quality Bar

• Keep scenarios commercially realistic and stage-appropriate.
• Test for behavior change, not memorized scripts.
• Ensure scoring is observable and consistent across reviewers.
• Include at least one unexpected turn to test adaptation.
• When evidence-derived scenarios are used, preserve realism while removing identifying details.