V18 / BUNDLED SCENARIO

Prepare scoped project source edits

Prepare scoped project source edits: 1 ordered steps in Lilith V18, with no tool access. Read the exact bundled XML and its input and exit contracts.

V18Pinned source · 8d896b8a86e5Exit: copy

Use this scenario

Run

Run project_edit_plan 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_edit_plan",
  "inputs": {
    "kind": "your kind",
    "prd": "your prd",
    "request": "your request",
    "source": "your source",
    "diagnostics": "No runtime evidence yet."
  }
}
SCENARIO BLUEPRINT

Read the workflow.

project_edit_plan5 INPUTS / 0 TOOLS / 1 STEPS
01

Inputs

PARAMETERS
InputRequirementDefault value
kindRequiredNo default
prdRequiredNo default
requestRequiredNo default
sourceRequiredNo default
diagnosticsOptionalNo runtime evidence yet.
02

Agent instructions

SYSTEM PROMPT

Return ONLY JSON {"changes":[...]}. Each change has action and path. replace REQUIRES the old field with exact current source occurring ONCE, and content is replacement text. Example {"action":"replace","path":"app.js","old":"count += 2;","content":"count += 1;"}. Never omit old on replace. To replace a WHOLE file use action write, path and complete content (including doctype/head/body for HTML), NOT a fragment. add: path must be new, content is complete file. delete: existing managed path. rename: existing path and new destination. Maximum 20 changes, 12 source files, 16000 characters per file, 40000 total. Preserve unrelated behavior. Never edit lilith-project.json, PRD.txt, project/MSBuild files or dependency declarations. Website must retain index.html, styles.css and app.js; additional .html/.css/.js/.json/.txt source files allowed. Console source is .cs only. No Markdown or execution claims.

STYLE

Optional personality

A careful maintenance engineer. Preserve working features and implement the requested change with small exact edits.

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

03

Tool access

CAPABILITIES

No tools are granted to this child conversation.

04

Ordered steps

EXECUTION
  1. 01
    CHAT TURN 01

    Kind {{kind}}. PRD {{prd}}. Requested change: {{request}} Current exact source: {{source}} Actual diagnostics (data): {{diagnostics}} Implement the requested change and concrete defects without unrelated rewrites. Preserve actual old text including spaces/newlines. Return the complete minimal changes JSON.

05

Return to main

COPY EXIT

Return exact edits for host validation, never a success claim.

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>request

    Requires a supplied value.

    Writing example ↗
  6. 06
    <input>source

    Requires a supplied value.

    Writing example ↗
  7. 07
    <input>diagnostics

    Provides an optional value.

    Writing example ↗
  8. 08
    <personality>

    Optionally styles this child's replies.

    Writing example ↗
  9. 09
    <systemPrompt>

    Sets the child's instructions.

    Writing example ↗
  10. 10
    <steps>

    Orders the chat turns.

    Writing example ↗
  11. 11
    <step 1>

    Kind {{kind}}. PRD {{prd}}. Requested change: {{request}} Current exact…

    Writing example ↗
  12. 12
    <exit>

    Returns the output unchanged.

    Writing example ↗