git:20261009.7098595 to git:20261010.b64ecd9

---

description: Regenerate a render from its recipe in recipes/

argument-hint: "<recipe> [project-slug]"

disable-model-invocation: true

---

Role: renderer (what a render and a recipe are: CLAUDE.md, Document

chain, Renders). A render is regenerated only here, on the principal's

explicit command, or by `/release` (POS.0810); Claude never regenerates

on its own judgement — it reports a stale render and offers. Iterating the recipe is working conversation like any

other; generating the render is mechanical.

1. Infer the current project from context ($1, or ask if ambiguous) and

read `recipes/$0.md`. If it does not exist, offer to compose it

through `/recipe` (a genre where one fits, else bare from

`templates/recipe.md`) and stop.

2. Read the recipe's declared inputs at their current versions.

Every input, CLAUDE.md included, is read from disk in the run:

the copy of CLAUDE.md a subagent carries in its context is the

session's and may be older than the file (POS.0950).

3. Generate in isolation: spawn one subagent (Agent tool, type

`general-purpose`, session model — never a model override) whose

prompt names the project, the recipe path, the output path and the

render date, and instructs it to read the recipe and its declared

inputs, follow the Instructions and Template exactly, and write the

file — nothing else. The prompt carries the front-matter block of

step 5 verbatim, so the subagent never derives the provenance shape

from a previous render. The subagent sees only the recipe and its

inputs, never this conversation: a render is derived from the

previous render unless the recipe declares it among its inputs

(the release-notes genre does, for the released sections), and

must not touch the ledger. Prose is hard-wrapped as CLAUDE.md,

Document kinds, says for every document.

Content only, always Markdown: the render carries no instructions

for a conversion — the recipe's `## Format` section is never

copied into it.

4. The subagent writes to `renders/$0.md`, or to the recipe's

`output:` path if it declares one (e.g. the repository README).

Overwrite freely; history lives in git.

5. The render opens with YAML front-matter provenance, written by the

subagent:

```yaml

---

project: <slug>

render: <recipe>

generated: YYYY-MM-DD

recipe: recipes/<recipe>.md v<version>

inputs:

- <path> v<version>

---

```

Inputs without a version of their own (e.g. CLAUDE.md) are cited by

path alone. A render is **stale** when any version cited in this

front-matter differs from the current version of that file, or a

cited file no longer exists. This is the one definition; `/forge`

and `/check` cite it (POS.1070).

correct, write or update the render's row in the ledger's Renders

table (its shape: `templates/ledger.md`, Renders), and report

what was rendered

from what.

7. The plain file (CLAUDE.md, Document chain, Renders). Where the recipe

carries a `## Format` section, run the script of its format —

`python scripts/md2docx.py` or `python scripts/md2pptx.py` — on the

render with `--engine pandoc` and the reference document and page size

the section names; the file lands beside the render. Where pandoc

is missing, the render stands, the plain file is not made, and

that is said aloud. A recipe without the section ends at the

Markdown. The designed file is `/publish`'s, never made here.

8. Where the ledger's Published table carries a row of this recipe,

set its state to `stale` and say so: the published file is now

older than its render. Remake nothing.