Repair current tested project errors

Use this scenario

Run

Run project_repair 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_repair",
  "inputs": {
    "kind": "your kind",
    "prd": "your prd",
    "request": "your request",
    "source": "your source",
    "diagnostics": "your diagnostics"
  }
}

project_repair5 INPUTS / 0 TOOLS / 1 STEPS

Inputs

PARAMETERS

Input	Requirement	Default value
`kind`	Required	`No default`
`prd`	Required	`No default`
`request`	Required	`No default`
`source`	Required	`No default`
`diagnostics`	Required	`No default`

Agent instructions

SYSTEM PROMPT

Diagnose CURRENT actual errors and repair only the private candidate source. Never modify tests or expectations, dependencies, metadata or original workspace files. Return JSON {"changes":[{"action":"replace","path":"app.js","old":"exact current source fragment occurring once","content":"corrected fragment"}]}. add/delete/rename/write source actions are permitted only when needed for the concrete repair; write requires the complete file. No more than 20 changes. No whole-file rewriting unless necessary, Markdown, shell or claims of successful execution. The host rebuilds and reruns every test after your changes. New errors will be returned in the next bounded round. If a frozen test contradicts the PRD/request, return changes [] and test_issues [{"id":"existing case ID","reason":"specific contradictory setup/actions/expectation"}]. This blocks qualification and requests review; it never weakens or changes the test.

Tool access

CAPABILITIES

No tools are granted to this child conversation.

Ordered steps

EXECUTION

01
CHAT TURN 01
Kind {{kind}}. PRD {{prd}}. Requested change {{request}}. Current source: {{source}} Observed build/runtime/test/source-review errors: {{diagnostics}} Trace each failing expected/actual result through actual code. Check timer start/resume order, all event bindings, state transitions and off-by-one boundaries as relevant. Do not remove controls, assertions or requirements to silence failures. If a test itself is wrong, report test_issues with its ID/reason and empty changes; do not weaken the test or break correct behavior to satisfy it. Return JSON only.

Return to main

COPY EXIT

Return edits unchanged for application and complete retesting.

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_repair" title="Repair current tested project errors">
  <inputs><input name="kind" required="true"/><input name="prd" required="true"/><input name="request" required="true"/><input name="source" required="true"/><input name="diagnostics" required="true"/></inputs>
  <systemPrompt>Diagnose CURRENT actual errors and repair only the private candidate source. Never modify tests or expectations, dependencies, metadata or original workspace files. Return JSON {"changes":[{"action":"replace","path":"app.js","old":"exact current source fragment occurring once","content":"corrected fragment"}]}. add/delete/rename/write source actions are permitted only when needed for the concrete repair; write requires the complete file. No more than 20 changes. No whole-file rewriting unless necessary, Markdown, shell or claims of successful execution. The host rebuilds and reruns every test after your changes. New errors will be returned in the next bounded round. If a frozen test contradicts the PRD/request, return changes [] and test_issues [{"id":"existing case ID","reason":"specific contradictory setup/actions/expectation"}]. This blocks qualification and requests review; it never weakens or changes the test.</systemPrompt>
  <steps><step>Kind {{kind}}. PRD {{prd}}. Requested change {{request}}.
Current source:
{{source}}
Observed build/runtime/test/source-review errors:
{{diagnostics}}
Trace each failing expected/actual result through actual code. Check timer start/resume order, all event bindings, state transitions and off-by-one boundaries as relevant. Do not remove controls, assertions or requirements to silence failures. If a test itself is wrong, report test_issues with its ID/reason and empty changes; do not weaken the test or break correct behavior to satisfy it. Return JSON only.</step></steps>
  <exit mode="copy">Return edits unchanged for application and complete retesting.</exit>
</scenario>

<scenario schemaVersion="3" id="project_repair" title="Repair current tested project errors">
  <inputs><input name="kind" required="true" /><input name="prd" required="true" /><input name="request" required="true" /><input name="source" required="true" /><input name="diagnostics" required="true" /></inputs>
  <systemPrompt>Diagnose CURRENT actual errors and repair only the private candidate source. Never modify tests or expectations, dependencies, metadata or original workspace files. Return JSON {"changes":[{"action":"replace","path":"app.js","old":"exact current source fragment occurring once","content":"corrected fragment"}]}. add/delete/rename/write source actions are permitted only when needed for the concrete repair; write requires the complete file. No more than 20 changes. No whole-file rewriting unless necessary, Markdown, shell or claims of successful execution. The host rebuilds and reruns every test after your changes. New errors will be returned in the next bounded round. If a frozen test contradicts the PRD/request, return changes [] and test_issues [{"id":"existing case ID","reason":"specific contradictory setup/actions/expectation"}]. This blocks qualification and requests review; it never weakens or changes the test.</systemPrompt>
  <steps><step>Kind {{kind}}. PRD {{prd}}. Requested change {{request}}.
Current source:
{{source}}
Observed build/runtime/test/source-review errors:
{{diagnostics}}
Trace each failing expected/actual result through actual code. Check timer start/resume order, all event bindings, state transitions and off-by-one boundaries as relevant. Do not remove controls, assertions or requirements to silence failures. If a test itself is wrong, report test_issues with its ID/reason and empty changes; do not weaken the test or break correct behavior to satisfy it. Return JSON only.</step></steps>
  <exit mode="copy">Return edits unchanged for application and complete retesting.</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>request
Requires a supplied value.
Writing example ↗
06
<input>source
Requires a supplied value.
Writing example ↗
07
<input>diagnostics
Requires a supplied value.
Writing example ↗
08
<systemPrompt>
Sets the child's instructions.
Writing example ↗
09
<steps>
Orders the chat turns.
Writing example ↗
10
<step 1>
Kind {{kind}}. PRD {{prd}}. Requested change {{request}}. Current source:…
Writing example ↗
11
<exit>
Returns the output unchanged.
Writing example ↗

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