V12 / BUNDLED SCENARIO

Select the project architecture specialist

Select the project architecture specialist: 1 ordered steps in Lilith V12, with no tool access. Read the exact bundled XML and its input and exit contracts.

V12Pinned source · ea1357ad1734Exit: copy

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
JSON
{
  "scenario_name": "project_architecture",
  "inputs": {
    "kind": "your kind",
    "prd": "your prd",
    "previous": "No previous plan.",
    "diagnostics": "No host diagnostics yet."
  }
}
SCENARIO BLUEPRINT

Read the workflow.

project_architecture4 INPUTS / 0 TOOLS / 1 STEPS
01

Inputs

PARAMETERS
InputRequirementDefault value
kindRequiredNo default
prdRequiredNo default
previousOptionalNo previous plan.
diagnosticsOptionalNo host diagnostics yet.
02

Agent instructions

SYSTEM PROMPT

Use a dedicated website or C# architect. Do not mix the website file contract with the C# method contract.

03

Tool access

CAPABILITIES

No tools are granted to this child conversation.

04

Ordered steps

EXECUTION
  1. 01
    CONDITION / HOST EVALUATED

    Input kind equals website

    THEN

    1. 01
      NESTED SCENARIO / FRESH CHILD

      project_architect_website ↗

      • prd = {{prd}}
      • previous = {{previous}}
      • diagnostics = {{diagnostics}}

    ELSE

    1. 01
      NESTED SCENARIO / FRESH CHILD

      project_architect ↗

      • kind = {{kind}}
      • prd = {{prd}}
      • previous = {{previous}}
      • diagnostics = {{diagnostics}}
05

Return to main

COPY EXIT

Return the specialist's architecture unchanged.

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

EVERY XML ELEMENT / IN FILE ORDER

Every part, briefly.

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

  1. 01
    <scenario>

    Names and versions the workflow.

    Writing example ↗
  2. 02
    <inputs>

    Declares input values.

    Writing example ↗
  3. 03
    <input>kind

    Requires a supplied value.

    Writing example ↗
  4. 04
    <input>prd

    Requires a supplied value.

    Writing example ↗
  5. 05
    <input>previous

    Provides an optional value.

    Writing example ↗
  6. 06
    <input>diagnostics

    Provides an optional value.

    Writing example ↗
  7. 07
    <systemPrompt>

    Sets the child's instructions.

    Writing example ↗
  8. 08
    <steps>

    Orders the chat turns.

    Writing example ↗
  9. 09
    <if>

    Checks real workspace state or an input value.

    Writing example ↗
  10. 10
    <then>

    Runs when the condition matches.

    Writing example ↗
  11. 11
    <run>

    Invokes a fresh saved child scenario.

    Writing example ↗
  12. 12
    <input>prd

    Binds a named operation or child input.

    Writing example ↗
  13. 13
    <input>previous

    Binds a named operation or child input.

    Writing example ↗
  14. 14
    <input>diagnostics

    Binds a named operation or child input.

    Writing example ↗
  15. 15
    <else>

    Runs when the condition does not match.

    Writing example ↗
  16. 16
    <run>

    Invokes a fresh saved child scenario.

    Writing example ↗
  17. 17
    <input>kind

    Binds a named operation or child input.

    Writing example ↗
  18. 18
    <input>prd

    Binds a named operation or child input.

    Writing example ↗
  19. 19
    <input>previous

    Binds a named operation or child input.

    Writing example ↗
  20. 20
    <input>diagnostics

    Binds a named operation or child input.

    Writing example ↗
  21. 21
    <exit>

    Returns the output unchanged.

    Writing example ↗