# Clarify the training problem before designing the experience Give Plan Agent your material and training situation. It clarifies the important details, organizes the requirements, and proposes an interactive design you can review. ## See what a finished experience feels like The factory safety demo below is a separate completed example. Play it to see how learners make decisions in a situation. This chapter uses a customer-service returns scenario to practise planning. A plan still needs assets, an interactive flow, assembly, playtesting, and publication before it becomes playable material. [](https://example-safety.speedl.ai/) ## Try it: a factory emergency An emergency unfolds at the factory. What would you do? Enter the scene, follow the prompts, and see what happens after your decisions. [Play the demo](https://example-safety.speedl.ai/) [Explore more demos](https://speedl.ai/home) The demo opens in a new tab. Return here afterward to plan the customer-service returns scenario. ## Describe the goal, confirm requirements, and review the plan Start with the learners, the decisions they need to practise, and any reference material. Answer questions, review the requirements and concept, then check the resulting plan before preparing assets and the interactive flow. 01 ### Describe the learners and training goal 1. In the open Doc2Sim project, select Plan. This tutorial uses a customer refund scenario. 2. Select Upload File and choose your actual refund policy, then send the example below in the message box. 3. Without a document, supply the verified rules in the message; do not ask the system to guess company policy. Example input: “For new support agents, practice checking facts before responding to a return request that conflicts with policy, and escalate when needed. Exclude refund-system operations. Use the attached policy and ask about uncertainties.” **Why this matters**“Make support training” is too vague to determine the exercise and assessment. **Check the result**The requirement summary reflects your intended audience and problem. Not the expected result? Correct an off-target summary and add evidence before confirming it. 02 ### Review and confirm the requirements 1. In the Requirements card below, check Audience, Intent, In scope, and Out of scope. The card may also list Deferred items and show Uses the submitted documents or No source documents. 2. Include checking facts and explaining policy; exclude back-office refund processing. 3. If the card lists Open questions, answer them first and confirm only after the updated card has no open questions. 4. To change something, select Request Changes, enter the change, and select Submit Changes. This is sent to the AI like a normal message; read the updated card. 5. Select Confirm requirements when correct. The card shows Confirmed. The next planning step has been queued., and the conversation keeps “✅ Confirm Requirements”. Then read the concept proposal. **Why this matters**An engaging story is not necessarily a useful exercise. The learner needs an opportunity to make the target decision. **Check the result**The card shows Confirmed. The next planning step has been queued., and the conversation keeps “✅ Confirm Requirements”. Continue to the concept proposal. Not the expected result? Answer any Open questions first and confirm once the updated card has none. For incorrect scope, select Request Changes, enter the change, and Submit Changes. This example does not submit changes; do that in your own project. 03 ### Review what the learner will experience 1. When the progress bar shows Review the direction, select Review proposal to return to the proposal card. 2. Read the duration, orientation, and story. 3. Check that fact-checking and promising an immediate refund lead to different consequences. 4. Select Confirm & Generate when the direction is correct, or Request Changes and Submit Changes to adjust it. The confirmed direction becomes the basis for reviewing the plan. Not the expected result? If the proposal needs changes, select Request Changes, enter the change, and Submit Changes. Read the new proposal before confirming. Check unfamiliar rules against the source document instead of treating unverified content as company policy. 04 ### Check the plan before production 1. After Confirm & Generate, the progress bar shows Generating your plan. If reviewers find issues, it may show an automatic revision round; wait for it to finish. 2. When it shows Your plan is ready and the conversation says The plan is ready. Open the file to review it., select the 📂 file button in the conversation or the View Output icon in the header to open the plan.txt plan. 3. The plan has four parts: 1. Overview, 2. Scene-by-scene script (key decisions labeled D1, D2… with options and any correct answer), 3. Endings, 4. Characters, scenes, and music (at least one background track). 4. Check the characters, scene, two responses, endings, and music. 5. For small edits, select Edit in the viewer, then Apply to draft, then Save. Revision requested. The published file has not been changed. means the request was sent and the published file is not yet changed. For larger changes, we suggest describing them in the same planning conversation. 6. Select Assets when ready. **Why this matters**Confirming a card does not prove the complete plan file exists. **Check the result**The plan exists and describes a complete practice scenario. Not the expected result? If something is missing, name the missing scene or ending in the same planning conversation and complete the plan first; do not hide teaching problems with later assets. Not getting the expected result? - The progress bar shows a revision round: the plan is being revised automatically based on review findings and will be reviewed again. Just wait. - The progress bar shows Your decision is needed: review issues remain after automatic revision. Read Remaining issues, then choose Continue revising or Publish as is. - A message says a task did not finish: Retry this task redoes only that task; other completed work is kept. - The progress bar shows Planning stopped because of an error: read the error in the conversation, then select Continue to resume from where it stopped. If it shows A review could not be completed, select Continue on the review message in the conversation to retry. - The conversation shows reviewer suggestions: they do not block publishing. To adopt one, tell the AI in the conversation. - The progress bar shows Progress updates interrupted: the latest status is temporarily unavailable; generation has not necessarily stopped. Reload the conversation. ## Recognize the planning review screens Use the requirements and concept screens to check the training scope and design direction, then review the resulting plan.  The real Plan workspace: upload material or start by describing the training situation in the message box. ## Check that the plan is ready for the next step Before preparing assets, you should be able to explain whom the learner meets, what choices they make, and what consequences they see. ### Clarify the real training problem Start from the problem, participant, and decision pressure so an abstract goal becomes a concrete situation. ### Choose a fitting interaction Use branching, text input, multiple choice, ordering, loops, or another structure that fits the problem. ### Organize the complete design Bring together the story, characters, scenes, flow, choices, consequences, endings, and feedback; asset needs include characters, scenes, and at least one background music track. [Prepare usable, consistent assets](doc2sim-assets.md)