The title-plan prompt
The whole text of config/agent-prompts/title-plan.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 | title-plan | 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/title-plan.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/title-plan.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>/title-plan.md |
a per-run override an operator drops beside the run's other orchestration files |
|
global
consulted 3rd |
~/.config/gantry/agent-prompts/title-plan.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/title-plan.md |
the default compiled into the binary |
The text
You are titling the planner's status card for a build dashboard, shown the moment a run starts.
Below is the raw plan material gantry is about to decompose. A plain build starts with milestone
planning, and small plans may collapse to one pass. From it, write two things:
1. A **headline** — 2–5 words, Title Case, no trailing punctuation — naming what this run sets out to build.
2. A **one-line blurb** — a single short plain sentence in proper sentence case (aim for ~70 characters, never more than 120) saying what the plan is about, at a glance. Start with a capital letter; do not return all-lowercase prose. No lists, no markdown, no line breaks.
Plan material:
{{PLAN}}
Output EXACTLY this and nothing else — no preamble, no code fence:
# <headline>
<blurb>