Plan a project as a persistent Kanban workflow

Use this scenario

Run

Run kanban_project 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": "kanban_project",
  "inputs": {
    "name": "your name",
    "kind": "your kind",
    "prd": "your prd",
    "repair_limit": "25"
  }
}

kanban_project4 INPUTS / 1 TOOLS / 2 STEPS

Inputs

PARAMETERS

Input	Requirement	Default value
`name`	Required	`No default`
`kind`	Required	`No default`
`prd`	Required	`No default`
`repair_limit`	Optional	`25`

Agent instructions

SYSTEM PROMPT

Use the approved-scope PRD to delegate architecture to fresh saved subagents. Host code turns the validated component contracts into detailed dependent cards and enforces plan approval, sequential work, repair bounds and separate execution/publication decisions. Never claim tests or publication from a plan receipt. A changed scope requires a new plan and host decision.

Tool access

CAPABILITIES

kanban_prepare_operation — selected from this version's tool catalog.

Ordered steps

EXECUTION

01
NESTED SCENARIO / FRESH CHILD
project_design ↗
- name = {{name}}
- kind = {{kind}}
- prd = {{prd}}
Save output as design.
02
BOUND OPERATION / HOST EXECUTED
kanban_prepare_operation
- name = {{name}}
- kind = {{kind}}
- prd = {{prd}}
- architecture = {{design.architecture}}
- repair_limit = {{repair_limit}}
Save output as board.

Return to main

COPY EXIT

Return the real board receipt and next host decision 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.

XMLStructureInputsTools / C#StepsExit

<scenario schemaVersion="3" id="kanban_project" title="Plan a project as a persistent Kanban workflow">
  <inputs><input name="name" required="true"/><input name="kind" required="true"/><input name="prd" required="true"/><input name="repair_limit" default="25"/></inputs>
  <systemPrompt>Use the approved-scope PRD to delegate architecture to fresh saved subagents. Host code turns the validated component contracts into detailed dependent cards and enforces plan approval, sequential work, repair bounds and separate execution/publication decisions. Never claim tests or publication from a plan receipt. A changed scope requires a new plan and host decision.</systemPrompt>
  <tools><allow name="kanban_prepare_operation"/></tools>
  <steps>
    <run scenario="project_design" result="design"><input name="name" value="{{name}}"/><input name="kind" value="{{kind}}"/><input name="prd" value="{{prd}}"/></run>
    <tool name="kanban_prepare_operation" result="board"><input name="name" value="{{name}}"/><input name="kind" value="{{kind}}"/><input name="prd" value="{{prd}}"/><input name="architecture" value="{{design.architecture}}"/><input name="repair_limit" value="{{repair_limit}}"/></tool>
  </steps>
  <exit mode="copy">Return the real board receipt and next host decision unchanged.</exit>
</scenario>

<scenario schemaVersion="3" id="kanban_project" title="Plan a project as a persistent Kanban workflow">
  <inputs><input name="name" required="true" /><input name="kind" required="true" /><input name="prd" required="true" /><input name="repair_limit" default="25" /></inputs>
  <systemPrompt>Use the approved-scope PRD to delegate architecture to fresh saved subagents. Host code turns the validated component contracts into detailed dependent cards and enforces plan approval, sequential work, repair bounds and separate execution/publication decisions. Never claim tests or publication from a plan receipt. A changed scope requires a new plan and host decision.</systemPrompt>
  <tools><allow name="kanban_prepare_operation" /></tools>
  <steps>
    <run scenario="project_design" result="design"><input name="name" value="{{name}}" /><input name="kind" value="{{kind}}" /><input name="prd" value="{{prd}}" /></run>
    <tool name="kanban_prepare_operation" result="board"><input name="name" value="{{name}}" /><input name="kind" value="{{kind}}" /><input name="prd" value="{{prd}}" /><input name="architecture" value="{{design.architecture}}" /><input name="repair_limit" value="{{repair_limit}}" /></tool>
  </steps>
  <exit mode="copy">Return the real board receipt and next host decision unchanged.</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>kind
Requires a supplied value.
Writing example ↗
05
<input>prd
Requires a supplied value.
Writing example ↗
06
<input>repair_limit
Provides an optional value.
Writing example ↗
07
<systemPrompt>
Sets the child's instructions.
Writing example ↗
08
<tools>
Defines available capabilities.
Writing example ↗
09
<allow>kanban_prepare_operation
Grants an existing tool.
Writing example ↗
10
<steps>
Orders the chat turns.
Writing example ↗
11
<run>
Invokes a fresh saved child scenario.
Writing example ↗
12
<input>name
Binds a named operation or child input.
Writing example ↗
13
<input>kind
Binds a named operation or child input.
Writing example ↗
14
<input>prd
Binds a named operation or child input.
Writing example ↗
15
<tool>kanban_prepare_operation
Executes a declared host operation.
Writing example ↗
16
<input>name
Binds a named operation or child input.
Writing example ↗
17
<input>kind
Binds a named operation or child input.
Writing example ↗
18
<input>prd
Binds a named operation or child input.
Writing example ↗
19
<input>architecture
Binds a named operation or child input.
Writing example ↗
20
<input>repair_limit
Binds a named operation or child input.
Writing example ↗
21
<exit>
Returns the output unchanged.
Writing example ↗

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