The stop-summary prompt
The whole text of config/agent-prompts/stop-summary.md, as an agent is handed it.
Bundled agent prompts — one row of 30, exported from
config/agent-prompts
· every prompt
· the resolution order
What this prompt is
| id | stop-summary | the key every tier, every pattern step and every override spells it by |
| kind | not a stage instruction | whether any bundled pattern hands it to an agent step |
| role | — | the harness role the agent reading it runs under |
| stage | — | the stage of a run it is handed at |
| bundled at | config/agent-prompts/stop-summary.md | where the built-in copy sits in Gantry's own tree |
No bundled pattern hands this file to an agent step. That is one honest answer to three different questions — a template the engine wraps other instructions in, a standing brief for something that is not a pipeline stage, or a file that is not a prompt at all — so the row says what the code can be asked rather than inventing a role for it.
Where an override of it goes
| tier | the file to write | what it is |
|---|---|---|
|
run
consulted 1st |
.gantry/<plan>/prompts/stop-summary.md |
the run's own frozen copy, written when the run started and read by every agent it launches; edit it to change what a run's remaining agents are told |
|
project
consulted 2nd |
.gantry/<plan>/stop-summary.md |
a per-run override an operator drops beside the run's other orchestration files |
|
global
consulted 3rd |
~/.config/gantry/agent-prompts/stop-summary.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/stop-summary.md |
the default compiled into the binary |
The text
{{READER_PREAMBLE}}
You are writing a generated stop card for Gantry's run dashboard.
Below is the complete stop bundle. Use only this bundle. Do not invent commands, files, causes,
actors, or provenance that the bundle does not support.
Stop bundle:
{{STOP_BUNDLE}}
Write a two-part card:
1. A **short title** — one line, 2-7 words, Title Case, no trailing punctuation. Lead with the cause.
2. A **brief body** — one concise paragraph, 1-2 sentences, no more than 260 characters. Lead with
the cause, name exactly one next action, and cite provenance only when the bundle gives it. Use
careful wording for uncertain provenance such as "reported by" or "from the log"; do not state an
inference as fact.
Output EXACTLY this form and nothing else — no preamble, no markdown headings, no bullets, no code
fence:
<title>
<body>