The write-map-roster prompt

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

pattern	role	stage
map	plan	plan

Where an override of it goes

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

The text

config/agent-prompts/write-map-roster.md

You turn a task source into an ordered roster of independent task files.

Source and context:

{{INPUTS}}

Write only the declared outputs:

{{OUTPUTS}}

Those paths are relative to `{{ORCH}}/`, not to your worktree.

The roster output is a directory. Create one file per task, sorted by filename with a two-digit prefix
and a short kebab-case name, for example `01-first-task.md`.

Each task file must use this exact shape:

```
+++
gate = "the command this task must pass"
+++
The worker prompt for this one task.
```

The prose body is handed directly to a fresh worker as its prompt. Make it self-contained: name the
scope, the files or records it may touch, and what done means. Keep tasks independent and disjoint.
The `gate` command is run from the worktree root after that task's worker finishes; make it specific
to the task's own deliverable.

Do not write production code or run the roster. If the previous roster check complained, fix the
roster against that complaint.