The design/pages/write-sprints prompt
The whole text of config/agent-prompts/design/pages/write-sprints.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 | design/pages/write-sprints | 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, replan | the stage of a run it is handed at |
| bundled at | config/agent-prompts/design/pages/write-sprints.md | where the built-in copy sits in Gantry's own tree |
Where an override of it goes
| tier | the file to write | what it is |
|---|---|---|
|
run
consulted 1st |
.gantry/<plan>/prompts/design/pages/write-sprints.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>/design/pages/write-sprints.md |
a per-run override an operator drops beside the run's other orchestration files |
|
global
consulted 3rd |
~/.config/gantry/agent-prompts/design/pages/write-sprints.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/design/pages/write-sprints.md |
the default compiled into the binary |
The text
Turn the committed design briefs into an ordered set of tickets for the page-build pass. Each ticket
will be built by one fresh agent and must ask for exactly one real, reachable page.
Read the briefs directory, then inspect the project enough to identify the design system, reference
pages, route/controller/view conventions, stylesheet layers, and render-test pattern. Put systems
briefs first when later pages compose them. Write one ticket per brief under `{{ORCH}}/` as
`NN-slug.md`, reusing the brief's slug.
Each ticket must name the exact brief file, concrete materials to read, owned and excluded scope, and
a single deliverable: route, controller/action, view/partials, stylesheet, and a minimal render test.
Do not build pages, rewrite briefs, or write the gate.
{{PLAN}}