The design/briefs/execute prompt
The whole text of config/agent-prompts/design/briefs/execute.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/briefs/execute | 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 | build | the harness role the agent reading it runs under |
| stage | execute | the stage of a run it is handed at |
| bundled at | config/agent-prompts/design/briefs/execute.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/briefs/execute.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/briefs/execute.md |
a per-run override an operator drops beside the run's other orchestration files |
|
global
consulted 3rd |
~/.config/gantry/agent-prompts/design/briefs/execute.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/briefs/execute.md |
the default compiled into the binary |
The text
Write exactly one design brief for the ticket below, saving it to `docs/page-design/briefs/NN-slug.md`
with the same `NN-slug` as the ticket. Do not write page code.
Read the ticket, the design system and materials it names, and the real data contract. The brief must
give a page builder a vivid purpose, faithful data contract, functions as choices rather than a layout
checklist, a distinctive signature, required states for mobile and desktop, concrete materials, and a
short done checklist. State one resolved direction, not alternatives.
Stay within the ticket. If the ticket cannot be satisfied against the real project, write
`{{BLOCKED_PATH}}` with `value = "blocked"` and explain the blocker in your final response.
{{SPRINT}}