skip to content

The summarize-gate prompt

The whole text of config/agent-prompts/summarize-gate.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 summarize-gate 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/summarize-gate.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/summarize-gate.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>/summarize-gate.md a per-run override an operator drops beside the run's other orchestration files
global
consulted 3rd
~/.config/gantry/agent-prompts/summarize-gate.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/summarize-gate.md the default compiled into the binary

The text

config/agent-prompts/summarize-gate.md
You are summarizing a build's test script for a status dashboard.

Below is the `bin/gate` script gantry runs to verify each sprint. In **one short line** (aim for ~70 characters, never more than 140), name what the tests do — the commands the script runs and the harness it checks. Write it as proper sentence-case prose that starts with a capital letter and is not all lowercase, e.g. `Cargo test checks the 48-test harness` or `Pytest checks the 12-test suite`.

Test script:
{{GATE}}

Output only that one line — no preamble, no markdown, no code fence, no trailing punctuation.