Use this scenario
Run
Run project_architecture scenario.
Use run_scenario with the saved scenario name and string-valued inputs. Required values are requested before execution.
View invocation JSON
{
"scenario_name": "project_architecture",
"inputs": {
"kind": "your kind",
"prd": "your prd",
"previous": "No previous plan.",
"diagnostics": "No host diagnostics yet."
}
}Inputs
PARAMETERS| Input | Requirement | Default value |
|---|---|---|
kind | Required | No default |
prd | Required | No default |
previous | Optional | No previous plan. |
diagnostics | Optional | No host diagnostics yet. |
Agent instructions
SYSTEM PROMPTUse a dedicated website or C# architect. Do not mix the website file contract with the C# method contract.
Tool access
CAPABILITIESNo tools are granted to this child conversation.
Ordered steps
EXECUTION- 01CONDITION / HOST EVALUATED
Input
kindequals websiteTHEN
- 01NESTED SCENARIO / FRESH CHILD
prd= {{prd}}previous= {{previous}}diagnostics= {{diagnostics}}
ELSE
- 01NESTED SCENARIO / FRESH CHILD
kind= {{kind}}prd= {{prd}}previous= {{previous}}diagnostics= {{diagnostics}}
- 01
Return to main
COPY EXITReturn the specialist's architecture unchanged.
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.
<scenario schemaVersion="3" id="project_architecture" title="Select the project architecture specialist">
<inputs><input name="kind" required="true" /><input name="prd" required="true" /><input name="previous" default="No previous plan." /><input name="diagnostics" default="No host diagnostics yet." /></inputs>
<systemPrompt>Use a dedicated website or C# architect. Do not mix the website file contract with the C# method contract.</systemPrompt>
<steps>
<if input="kind" equals="website">
<then><run scenario="project_architect_website"><input name="prd" value="{{prd}}" /><input name="previous" value="{{previous}}" /><input name="diagnostics" value="{{diagnostics}}" /></run></then>
<else><run scenario="project_architect"><input name="kind" value="{{kind}}" /><input name="prd" value="{{prd}}" /><input name="previous" value="{{previous}}" /><input name="diagnostics" value="{{diagnostics}}" /></run></else>
</if>
</steps>
<exit mode="copy">Return the specialist's architecture unchanged.</exit>
</scenario>
Every part, briefly.
Short explanations of every element and chat step in this scenario.
- 01Writing example ↗
<scenario>Names and versions the workflow.
- 02Writing example ↗
<inputs>Declares input values.
- 03Writing example ↗
<input>kindRequires a supplied value.
- 04Writing example ↗
<input>prdRequires a supplied value.
- 05Writing example ↗
<input>previousProvides an optional value.
- 06Writing example ↗
<input>diagnosticsProvides an optional value.
- 07Writing example ↗
<systemPrompt>Sets the child's instructions.
- 08Writing example ↗
<steps>Orders the chat turns.
- 09Writing example ↗
<if>Checks real workspace state or an input value.
- 10Writing example ↗
<then>Runs when the condition matches.
- 11Writing example ↗
<run>Invokes a fresh saved child scenario.
- 12Writing example ↗
<input>prdBinds a named operation or child input.
- 13Writing example ↗
<input>previousBinds a named operation or child input.
- 14Writing example ↗
<input>diagnosticsBinds a named operation or child input.
- 15Writing example ↗
<else>Runs when the condition does not match.
- 16Writing example ↗
<run>Invokes a fresh saved child scenario.
- 17Writing example ↗
<input>kindBinds a named operation or child input.
- 18Writing example ↗
<input>prdBinds a named operation or child input.
- 19Writing example ↗
<input>previousBinds a named operation or child input.
- 20Writing example ↗
<input>diagnosticsBinds a named operation or child input.
- 21Writing example ↗
<exit>Returns the output unchanged.