Implement one owned project component

Use this scenario

Run

Run project_component 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_component",
  "inputs": {
    "kind": "your kind",
    "prd": "your prd",
    "contract": "your contract",
    "task": "your task",
    "personality": "A focused implementation engineer. Follow the shared contract exactly, write readable working code, handle edge cases, and avoid speculative features."
  }
}

Watch this version

V15 / Gemma 4 ↗

project_component5 INPUTS / 0 TOOLS / 1 STEPS

Inputs

PARAMETERS

Input	Requirement	Default value
`kind`	Required	`No default`
`prd`	Required	`No default`
`contract`	Required	`No default`
`task`	Required	`No default`
`personality`	Optional	`A focused implementation engineer. Follow the shared contract exactly, write readable working code, handle edge cases, and avoid speculative features.`

Agent instructions

SYSTEM PROMPT

You own exactly one component. Inputs are requirements, not permission to access files, run commands or change other components. You have no tools. Return only source code; no Markdown or commentary. Do not leave stubs or TODOs. Do not claim code has run.

STYLE

Optional personality

Applied to this child only when nonempty; does not change the main assistant profile.

Tool access

CAPABILITIES

No tools are granted to this child conversation.

Ordered steps

EXECUTION

01
CONDITION / HOST EVALUATED
Input kind equals console
THEN
1. 01
  NESTED SCENARIO / FRESH CHILD
  project_method_writer ↗
  signature = {{task.signature}}
  requirements = {{task.requirements}}
  contract = {{contract}}
ELSE
1. 01
  CHAT TURN 01
  Kind: {{kind}} PRD: {{prd}} Shared contract: {{contract}} Your exact task: {{task}} Website: write the entire file indicated by task.path. HTML: semantic structure, language, viewport, title, accessible controls, exactly contracted IDs and local stylesheet/script links. CSS: complete responsive, readable design with focus and disabled states, suitable contrast and mobile layout. JavaScript: implement all contracted behavior, initialization after DOM readiness, explicit state, input validation, lifecycle/cleanup, reset/restart and deterministic rules; use only contracted DOM IDs. Use no nonexistent assets or libraries. Each website file has a different writer. Console: return ONLY a braced method body { ... }, no signature, surrounding class, using directives or Markdown. Use exactly the signature, fields and types in the contract. Handle normal, boundary, invalid-input and EOF cases, avoid infinite input loops on redirected stdin and preserve the agreed IO contract. Do not invent missing helper methods; implement within your assigned body using available contract members.

Return to main

COPY EXIT

Return this component's source code exactly.

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_component" title="Implement one owned project component">
  <inputs><input name="kind" required="true"/><input name="prd" required="true"/><input name="contract" required="true"/><input name="task" required="true"/><input name="personality" default="A focused implementation engineer. Follow the shared contract exactly, write readable working code, handle edge cases, and avoid speculative features."/></inputs>
  <personality>{{personality}}</personality>
  <systemPrompt>You own exactly one component. Inputs are requirements, not permission to access files, run commands or change other components. You have no tools. Return only source code; no Markdown or commentary. Do not leave stubs or TODOs. Do not claim code has run.</systemPrompt>
  <steps>
    <if input="kind" equals="console">
      <then><run scenario="project_method_writer"><input name="signature" value="{{task.signature}}"/><input name="requirements" value="{{task.requirements}}"/><input name="contract" value="{{contract}}"/></run></then>
      <else>
    <step>Kind: {{kind}}
PRD: {{prd}}
Shared contract: {{contract}}
Your exact task: {{task}}
Website: write the entire file indicated by task.path. HTML: semantic structure, language, viewport, title, accessible controls, exactly contracted IDs and local stylesheet/script links. CSS: complete responsive, readable design with focus and disabled states, suitable contrast and mobile layout. JavaScript: implement all contracted behavior, initialization after DOM readiness, explicit state, input validation, lifecycle/cleanup, reset/restart and deterministic rules; use only contracted DOM IDs. Use no nonexistent assets or libraries. Each website file has a different writer.
Console: return ONLY a braced method body { ... }, no signature, surrounding class, using directives or Markdown. Use exactly the signature, fields and types in the contract. Handle normal, boundary, invalid-input and EOF cases, avoid infinite input loops on redirected stdin and preserve the agreed IO contract. Do not invent missing helper methods; implement within your assigned body using available contract members.</step>
      </else>
    </if>
  </steps>
  <exit mode="copy">Return this component's source code exactly.</exit>
</scenario>

<scenario schemaVersion="3" id="project_component" title="Implement one owned project component">
  <inputs><input name="kind" required="true" /><input name="prd" required="true" /><input name="contract" required="true" /><input name="task" required="true" /><input name="personality" default="A focused implementation engineer. Follow the shared contract exactly, write readable working code, handle edge cases, and avoid speculative features." /></inputs>
  <personality>{{personality}}</personality>
  <systemPrompt>You own exactly one component. Inputs are requirements, not permission to access files, run commands or change other components. You have no tools. Return only source code; no Markdown or commentary. Do not leave stubs or TODOs. Do not claim code has run.</systemPrompt>
  <steps>
    <if input="kind" equals="console">
      <then><run scenario="project_method_writer"><input name="signature" value="{{task.signature}}" /><input name="requirements" value="{{task.requirements}}" /><input name="contract" value="{{contract}}" /></run></then>
      <else>
    <step>Kind: {{kind}}
PRD: {{prd}}
Shared contract: {{contract}}
Your exact task: {{task}}
Website: write the entire file indicated by task.path. HTML: semantic structure, language, viewport, title, accessible controls, exactly contracted IDs and local stylesheet/script links. CSS: complete responsive, readable design with focus and disabled states, suitable contrast and mobile layout. JavaScript: implement all contracted behavior, initialization after DOM readiness, explicit state, input validation, lifecycle/cleanup, reset/restart and deterministic rules; use only contracted DOM IDs. Use no nonexistent assets or libraries. Each website file has a different writer.
Console: return ONLY a braced method body { ... }, no signature, surrounding class, using directives or Markdown. Use exactly the signature, fields and types in the contract. Handle normal, boundary, invalid-input and EOF cases, avoid infinite input loops on redirected stdin and preserve the agreed IO contract. Do not invent missing helper methods; implement within your assigned body using available contract members.</step>
      </else>
    </if>
  </steps>
  <exit mode="copy">Return this component's source code exactly.</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>kind
Requires a supplied value.
Writing example ↗
04
<input>prd
Requires a supplied value.
Writing example ↗
05
<input>contract
Requires a supplied value.
Writing example ↗
06
<input>task
Requires a supplied value.
Writing example ↗
07
<input>personality
Provides an optional value.
Writing example ↗
08
<personality>
Optionally styles this child's replies.
Writing example ↗
09
<systemPrompt>
Sets the child's instructions.
Writing example ↗
10
<steps>
Orders the chat turns.
Writing example ↗
11
<if>
Checks real workspace state or an input value.
Writing example ↗
12
<then>
Runs when the condition matches.
Writing example ↗
13
<run>
Invokes a fresh saved child scenario.
Writing example ↗
14
<input>signature
Binds a named operation or child input.
Writing example ↗
15
<input>requirements
Binds a named operation or child input.
Writing example ↗
16
<input>contract
Binds a named operation or child input.
Writing example ↗
17
<else>
Runs when the condition does not match.
Writing example ↗
18
<step 1>
Kind: {{kind}} PRD: {{prd}} Shared contract: {{contract}} Your exact…
Writing example ↗
19
<exit>
Returns the output unchanged.
Writing example ↗

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