skip to content

The review-plan-change prompt

The whole text of config/agent-prompts/review-plan-change.md, as an agent is handed it.

Bundled agent prompts — one row of 23, exported from config/agent-prompts · every prompt · the resolution order

What this prompt is

id review-plan-change the key every tier, every pattern step and every override spells it by
kind stage instruction whether any bundled pattern hands it to an agent step
role review the harness role the agent reading it runs under
stage review the stage of a run it is handed at
bundled at config/agent-prompts/review-plan-change.md where the built-in copy sits in Gantry's own tree

Where an override of it goes

tier the file to write what it is
run
consulted 1st
.gantry/<plan>/prompts/review-plan-change.md the run's own frozen copy, written when the run started and read by every agent it launches; editing it changes what a run's remaining agents are told
project
consulted 2nd
.gantry/<plan>/review-plan-change.md a per-run override an operator places beside the run's other orchestration files
global
consulted 3rd
~/.config/gantry/agent-prompts/review-plan-change.md the materialized global mirror; it overrides the built-in once its bytes differ from the built-in's
built-in
consulted 4th
config/agent-prompts/review-plan-change.md the default compiled into the binary

The text

config/agent-prompts/review-plan-change.md
A plan-file diff from this run is below. Judge only the plan change: whether the changed run-plan
files still carry the immutable source plan's requirements coherently. This is not a code review,
and `{{PLAN_CHANGE_DIFF}}` is the subject; do not infer from the implementation diff.

Compare the changed briefs against the source plan and the current run-plan context. Accept a change
only when the plan still preserves required coverage, ordering, and contracts between tasks. Reject
it when the change drops, weakens, overgrows, reorders, duplicates, or contradicts required plan
coverage.

Source plan:
{{SOURCE_PLAN}}

Plan files in scope:
{{SCOPED_PLAN_FILES}}

Plan-file diff:
{{PLAN_CHANGE_DIFF}}

Record the judgment in the declared outputs below. Write the verdict output as exactly one of its
declared raw values, with no TOML wrapper. A missing, malformed, or out-of-vocabulary verdict fails
the review; prose in your final response is not a verdict.

{{OUTPUTS}}