Prepare a tested restoration of managed project source

Use this scenario

Run

Run project_restore scenario.

Use run_scenario with the saved scenario name and string-valued inputs. Required values are requested before execution.

View invocation JSON

JSON

{
  "scenario_name": "project_restore",
  "inputs": {
    "name": "your name",
    "backup_id": "your backup id"
  }
}

project_restore2 INPUTS / 2 TOOLS / 2 STEPS

Inputs

PARAMETERS

Input	Requirement	Default value
`name`	Required	`No default`
`backup_id`	Required	`No default`

Agent instructions

SYSTEM PROMPT

Prepare a private source restoration and executable test plan. Execution and publication both require separate host decisions.

Tool access

CAPABILITIES

project_restore_prepare_operation — selected from this version's tool catalog.
project_set_tests_operation — selected from this version's tool catalog.

Ordered steps

EXECUTION

01
BOUND OPERATION / HOST EXECUTED
project_restore_prepare_operation
- name = {{name}}
- backup_id = {{backup_id}}
Save output as draft.
02
NESTED SCENARIO / FRESH CHILD
project_plan_tests ↗
- id = {{draft.id}}
Save output as receipt.

Return to main

COPY EXIT

Return the private restoration draft and separate execution command unchanged. Original files remain unchanged until testing and exact publication approval.

The final text returns without model rewriting. Bound operation scenarios return application results; pending changes still require host approval.

Complete XML, including any embedded C#. Copy it without changing the file's contents.

XMLStructureInputsTools / C#StepsExit

<scenario schemaVersion="3" id="project_restore" title="Prepare a tested restoration of managed project source">
  <inputs><input name="name" required="true" /><input name="backup_id" required="true" /></inputs>
  <systemPrompt>Prepare a private source restoration and executable test plan. Execution and publication both require separate host decisions.</systemPrompt>
  <tools><allow name="project_restore_prepare_operation" /><allow name="project_set_tests_operation" /></tools>
  <steps>
    <tool name="project_restore_prepare_operation" result="draft"><input name="name" value="{{name}}" /><input name="backup_id" value="{{backup_id}}" /></tool>
    <run scenario="project_plan_tests" result="receipt"><input name="id" value="{{draft.id}}" /></run>
  </steps>
  <exit mode="copy">Return the private restoration draft and separate execution command unchanged. Original files remain unchanged until testing and exact publication approval.</exit>
</scenario>

Download XML ↓

EVERY XML ELEMENT / IN FILE ORDER

Every part, briefly.

Short explanations of every element and chat step in this scenario.

01
<scenario>
Names and versions the workflow.
Writing example ↗
02
<inputs>
Declares input values.
Writing example ↗
03
<input>name
Requires a supplied value.
Writing example ↗
04
<input>backup_id
Requires a supplied value.
Writing example ↗
05
<systemPrompt>
Sets the child's instructions.
Writing example ↗
06
<tools>
Defines available capabilities.
Writing example ↗
07
<allow>project_restore_prepare_operation
Grants an existing tool.
Writing example ↗
08
<allow>project_set_tests_operation
Grants an existing tool.
Writing example ↗
09
<steps>
Orders the chat turns.
Writing example ↗
10
<tool>project_restore_prepare_operation
Executes a declared host operation.
Writing example ↗
11
<input>name
Binds a named operation or child input.
Writing example ↗
12
<input>backup_id
Binds a named operation or child input.
Writing example ↗
13
<run>
Invokes a fresh saved child scenario.
Writing example ↗
14
<input>id
Binds a named operation or child input.
Writing example ↗
15
<exit>
Returns the output unchanged.
Writing example ↗

Write a scenario, step by step ↗How sub-agents work ↗