Deal-cycle decision rehearsal
Walk reps through pricing pushback, multi-thread navigation, and exec-level objections. Different paths model different deal outcomes.
Coming soon
Build LMS-ready branching scenario training with Claude or ChatGPT.
Build decision-tree training in plain language. Describe the scenario, the choice points, and the consequences, your coding agent produces a SCORM-ready branching scenario for any LMS.
What is it?
What is a branching scenario?
A decision-tree training activity where the learner makes choices that change what happens next. Different paths lead to different outcomes, different feedback, and different scores, so the same scenario teaches different lessons depending on how the learner navigates it.
-
Decision-tree scenarios where each choice leads to a different next scene -
Multiple endings with different scores so learners can pass or fail in many distinct ways -
Plain-language authoring, describe choices and consequences in a paragraph, not in a flowchart tool -
Per-path feedback that explains why each choice mattered in context -
Exports as a SCORM 1.2 package for Cornerstone, Moodle, Canvas, TalentLMS, Docebo, Brightspace, and every LMS -
Same bundle runs standalone in any browser, no LMS required for non-graded use
How it works
How to build a branching scenario
in four steps.
From a plain-English scenario description to a SCORM-ready branching simulation. No flowchart software, no XML, no scripting language.
01
Describe the situation in plain English
Tell your coding agent the setup, the stakeholder, and the moment of decision. Your tools generate a coherent first draft of the tree instead of forcing you into a templating UI.
02
Define the choice points and outcomes
Name the decisions that matter and the consequences of each path. The tool fills in plausible distractor branches and dead-ends so the learner faces real ambiguity.
03
Refine the tree in chat
"Add a stakeholder who pushes back at the midpoint." "Make the easy path more tempting." Iterate by talking with your coding agent, not by clicking through a graph editor.
04
Export as a SCORM 1.2 package
One command produces a SCORM 1.2 zip. Upload to Cornerstone, Moodle, Canvas, TalentLMS, or any SCORM LMS. Path-level scores post back to the gradebook automatically.
Use cases by role
Branching scenarios
for every high-stakes decision.
The same toolchain powers sales-decision rehearsal, manager judgment training, compliance dilemmas, clinical decision-making, and ethics scenarios. Describe the choice, the tree builds itself.
Manager judgment training
Performance conversations, layoffs, conflict resolution, the cases without a single right answer. Branching scenarios let managers practice the tradeoffs safely.
Compliance dilemmas
Conflict-of-interest moments, gifts-and-entertainment edge cases, data-handling decisions. The branching format forces learners to commit to a choice and see consequences.
Clinical decision pathways
Practice triage and treatment-selection decisions with branching consequences, grounded in your clinical guidelines.
Case-based learning
Bring history, civics, or biology cases to life as branching choices. Learners discover that the same facts can lead to different defensible decisions.
Incident-response drills
Simulate outages, recalls, or PR incidents. Branching paths force learners to commit to a sequence and see how early choices compound.
Path-graded branching
Every path graded against your rubric, choice by choice.
When the scenario ends, the AI scores the path the learner took against the consequence weights you set. Each checkpoint comes back with a justification, evidence pulled from the choice, and a specific tip the learner can act on next time.
Update consequences or weights any time. Re-export the SCORM package and the next attempt grades against the new tree.
Per-path scoring
Each branch carries its own consequence weight. Learners' total score reflects the path they took, not just whether they reached the end.
Replay with consequences
Learners can replay to explore alternative paths. Scores from each attempt persist so they can compare outcomes side-by-side.
Auditor view
Reviewers can walk every path without grading. Critical for compliance sign-off, instructional-design QA, and SME review.
Session complete
Your Debrief
9/10
★★★★★★★★★☆
Total 9 / 10
Picked a defensible path through checkpoint 2 instead of taking the easy-but-wrong shortcut.
Recovered after the surprise pushback at checkpoint 3 without abandoning the original plan.
Reached an ending consistent with the stated values, not just one that maximized short-term outcome.
Plain-English authoring
Author branching scenarios in plain English. No flowchart required.
Tweak a checkpoint, swap an ending, raise the stakes, or rewrite the consequence rubric, just describe the change in your own words. Your coding agent rebuilds the tree and re-exports the SCORM package without you ever touching a graph editor.
When you're happy, export as a SCORM 1.2 package for your LMS, or use the same HTML bundle standalone.
Make checkpoint 2 harder, the easy path should feel more tempting.
Updated. Easy path now carries a 'looks fine, blows up later' twist at checkpoint 3.
Add an ending where the learner did the right thing but it still goes badly.
Added ending
right-thing-bad-outcome. Tree now has 5 reachable endings.Export as SCORM.
✓ branching-scenarios.zip ready (SCORM 1.2, 14 KB)
Scenario Library
Start from real high-stakes
decisions.
Paste any prompt into your coding agent to get a complete branching scenario as a single self-contained HTML file. Adjust the choices, consequences, or rubric in plain language.
Sales
Late-quarter discount request
A rep faces a 30% discount ask from a champion on the last day of the quarter. The tree branches on hold-the-line, partial-discount, and creative-terms paths.
Prompt
Using /branching-scenarios, build a 5-checkpoint scenario: rep facing 30% discount ask on quarter-end. Score on margin, deal close, and CEO sign-off.
Management
Underperforming senior IC
A manager has to decide how to handle a senior IC who's missed two quarters of goals but is technically irreplaceable on the current project.
Prompt
Using /branching-scenarios, build a 6-checkpoint scenario: manager handling senior IC who's missed 2Q goals. Score on candor, project risk, and retention.
Compliance
Gifts-and-entertainment edge case
A regional director is offered a vendor's box at a major sporting event. The tree branches on accept, decline, escalate-to-legal paths.
Prompt
Using /branching-scenarios, build a 4-checkpoint G&E scenario: director offered vendor sport-suite. Score on policy, disclosure, and vendor relationship.
Healthcare
Mid-shift escalation decision
A charge nurse decides whether to escalate a borderline-stable patient at shift change. The tree branches on hand-off-as-is, page-attending, transfer-to-step-down.
Prompt
Using /branching-scenarios, build a 5-checkpoint scenario: charge nurse mid-shift escalation. Score on assessment, handoff quality, and patient safety.
Engineering
Production deploy on a Friday
An engineer has a critical bug fix ready at 5pm Friday. The tree branches on deploy-now, deploy-Monday, feature-flag rollout, with cascading consequences.
Prompt
Using /branching-scenarios, build a 4-checkpoint scenario: critical fix at 5pm Friday. Score on customer impact, on-call burden, and process integrity.
Leadership
Layoff selection criteria
A director has to cut 15% of a team. The tree branches on tenure-based, performance-based, and strategic-skills-based selection paths, each with downstream consequences.
Prompt
Using /branching-scenarios, build a 7-checkpoint scenario: director picking layoff criteria. Score on fairness, business continuity, and team trust.
SCORM & LMS
SCORM 1.2 branching-scenario activities for any LMS.
Every branching scenario exports as a standards-compliant SCORM 1.2 package. Upload the zip, assign it like any other course activity, and completion plus path-level scores flow back to the gradebook automatically.
-
Single SCORM 1.2 zip, upload to your LMS, no integration work, API keys, or custom JavaScript -
Completion, score, and time-on-task post back via cmi.core.score.rawandcmi.core.lesson_status -
Tested with Cornerstone OnDemand, Moodle, Canvas LMS, TalentLMS, Docebo, Brightspace, Absorb, 360Learning, SuccessFactors, and Workday Learning -
Same self-contained HTML bundle runs standalone on a public page, an intranet, or as an embedded iframe -
Auditor mode lets reviewers walk every path without grading, ideal for SME and compliance review -
Grading runs inside the bundle, no middleware, no data warehouse, no analytics SDK required
FAQ
Frequently asked questions about
branching scenarios.
Authoring, path grading, LMS compatibility, replayability, model choice, answered directly.
A branching scenario is a decision-tree training activity where the learner's choices change what happens next. Different paths lead to different outcomes, scores, and feedback, so the same scenario teaches different lessons depending on the route a learner takes.
A branching scenario gives learners discrete pre-authored choices at each step, so the tree is fixed and reviewable. A role-play is an open conversation with an AI character that can go anywhere. Branching scenarios are better for compliance-grade auditability; role-plays are better for free-form practice.
You author the scenario in plain language with your coding agent, not by clicking nodes in a graph editor. The tree is stored as a readable text document you can diff and version-control. The AI fills in plausible distractor paths so you don't have to author every dead-end yourself.
Yes. Every scenario exports as a SCORM 1.2 package, which works in Cornerstone, Moodle, Canvas, TalentLMS, Docebo, Brightspace, Absorb, Litmos, and every other SCORM-compliant LMS.
Each branch carries a weight reflecting the consequence of that choice. The learner's total score is the sum of weights along the path they took. Some scenarios use a single pass/fail/partial outcome; others use a richer per-objective rubric.
Yes, that's the point. A well-built scenario has several distinct endings reflecting different decision paths, with explicit per-ending feedback that explains why that path produced that outcome.
The bundles run on whichever frontier model you configure, Claude, GPT, Gemini, or a self-hosted model. Pre-authored choice text is model-independent; only AI-generated distractor branches use the model.
Branching Scenarios is in active development. It will install via your coding agent with a single command, the same way the existing role-play skill works today. Add your email below and we'll let you know the day it ships.