Use this scenario
Run
Run project_design 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_design",
"inputs": {
"name": "your name",
"kind": "your kind",
"prd": "your prd"
}
}Inputs
PARAMETERS| Input | Requirement | Default value |
|---|---|---|
name | Required | No default |
kind | Required | No default |
prd | Required | No default |
Agent instructions
SYSTEM PROMPTGet a proposed architecture and check its actual host contract. Give structural diagnostics to one fresh repair architect if needed. Never launch writers with an invalid plan.
Tool access
CAPABILITIESproject_check_architecture_operation— selected from this version's tool catalog.
Ordered steps
EXECUTION- 01NESTED SCENARIO / FRESH CHILD
kind= {{kind}}prd= {{prd}}
Save output as
architecture. - 02BOUND OPERATION / HOST EXECUTED
project_check_architecture_operationname= {{name}}kind= {{kind}}prd= {{prd}}architecture= {{architecture}}
Save output as
checked. - 03CONDITION / HOST EVALUATED
Input
checked.validequals falseTHEN
- 01NESTED SCENARIO / FRESH CHILD
kind= {{kind}}prd= {{prd}}previous= {{architecture}}diagnostics= {{checked.diagnostics}}
Save output as
repaired. - 02STRUCTURED RESULT / HOST COMPOSED
architecture= {{repaired}}
ELSE
- 01STRUCTURED RESULT / HOST COMPOSED
architecture= {{architecture}}
- 01
Return to main
COPY EXITReturn architecture data. Preparation will reject any remaining invalid contract.
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_design" title="Validate architecture before assigning implementation work">
<inputs><input name="name" required="true" /><input name="kind" required="true" /><input name="prd" required="true" /></inputs>
<systemPrompt>Get a proposed architecture and check its actual host contract. Give structural diagnostics to one fresh repair architect if needed. Never launch writers with an invalid plan.</systemPrompt>
<tools><allow name="project_check_architecture_operation" /></tools>
<steps>
<run scenario="project_architecture" result="architecture"><input name="kind" value="{{kind}}" /><input name="prd" value="{{prd}}" /></run>
<tool name="project_check_architecture_operation" result="checked"><input name="name" value="{{name}}" /><input name="kind" value="{{kind}}" /><input name="prd" value="{{prd}}" /><input name="architecture" value="{{architecture}}" /></tool>
<if input="checked.valid" equals="false">
<then>
<run scenario="project_architecture" result="repaired"><input name="kind" value="{{kind}}" /><input name="prd" value="{{prd}}" /><input name="previous" value="{{architecture}}" /><input name="diagnostics" value="{{checked.diagnostics}}" /></run>
<result><field name="architecture" value="{{repaired}}" /></result>
</then>
<else><result><field name="architecture" value="{{architecture}}" /></result></else>
</if>
</steps>
<exit mode="copy">Return architecture data. Preparation will reject any remaining invalid contract.</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>nameRequires a supplied value.
- 04Writing example ↗
<input>kindRequires a supplied value.
- 05Writing example ↗
<input>prdRequires a supplied value.
- 06Writing example ↗
<systemPrompt>Sets the child's instructions.
- 07Writing example ↗
<tools>Defines available capabilities.
- 08Writing example ↗
<allow>project_check_architecture_operationGrants an existing tool.
- 09Writing example ↗
<steps>Orders the chat turns.
- 10Writing example ↗
<run>Invokes a fresh saved child scenario.
- 11Writing example ↗
<input>kindBinds a named operation or child input.
- 12Writing example ↗
<input>prdBinds a named operation or child input.
- 13Writing example ↗
<tool>project_check_architecture_operationExecutes a declared host operation.
- 14Writing example ↗
<input>nameBinds a named operation or child input.
- 15Writing example ↗
<input>kindBinds a named operation or child input.
- 16Writing example ↗
<input>prdBinds a named operation or child input.
- 17Writing example ↗
<input>architectureBinds a named operation or child input.
- 18Writing example ↗
<if>Checks real workspace state or an input value.
- 19Writing example ↗
<then>Runs when the condition matches.
- 20Writing example ↗
<run>Invokes a fresh saved child scenario.
- 21Writing example ↗
<input>kindBinds a named operation or child input.
- 22Writing example ↗
<input>prdBinds a named operation or child input.
- 23Writing example ↗
<input>previousBinds a named operation or child input.
- 24Writing example ↗
<input>diagnosticsBinds a named operation or child input.
- 25Writing example ↗
<result>Returns structured JSON data.
- 26Writing example ↗
<field>architectureBinds one returned field.
- 27Writing example ↗
<else>Runs when the condition does not match.
- 28Writing example ↗
<result>Returns structured JSON data.
- 29Writing example ↗
<field>architectureBinds one returned field.
- 30Writing example ↗
<exit>Returns the output unchanged.