The write-about prompt

The whole text of config/agent-prompts/write-about.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	write-about	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	util	the harness role the agent reading it runs under
stage	support	the stage of a run it is handed at
bundled at	config/agent-prompts/write-about.md	where the built-in copy sits in Gantry's own tree

pattern	role	stage
build	util	support

Where an override of it goes

tier	the file to write	what it is
run consulted 1st	`.gantry/<plan>/prompts/write-about.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>/write-about.md`	a per-run override an operator drops beside the run's other orchestration files
global consulted 3rd	`~/.config/gantry/agent-prompts/write-about.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/write-about.md`	the default compiled into the binary

The text

config/agent-prompts/write-about.md

You are naming and summarizing a software build for a status dashboard, and titling the sprint rows
the current build pass will show.

Below is the plan's slug and the ordered sprint outline for the current build pass (each is
`NN-slug: one-line intent`). In a default milestone run this may be one milestone's sprint set; in a
legacy resumed flat run it may be the whole run. From it, infer what the work *is* and write:

1. A **short project name** — a title, 2–5 words, Title Case, no trailing punctuation. Not the slug verbatim; a human-readable name for the work as a whole.
2. A **one-line description** — a single short, plain sentence in proper sentence case (aim for ~90 characters, never more than 140) saying what the project builds, at a glance. Start with a capital letter; do not return all-lowercase prose. No lists, no markdown, no line breaks.
3. For **every** sprint row, a **title** (2–5 words, Title Case, no trailing punctuation) and a
   **one-line blurb** (a short plain sentence in proper sentence case, aim for ~70 characters, never
   more than 140) saying what that sprint does. Start each blurb with a capital letter; do not return
   all-lowercase prose.

Plan slug: {{PLAN}}

Sprints:
{{SPRINTS}}

Output EXACTLY this form and nothing else — no preamble, no code fence. Reuse each sprint's exact `NN-slug` id as given, one `## sprint <id>` block per sprint, in order:

# <project name>

<one-line description>

## sprint <NN-slug>

<sprint title>

<sprint blurb>