recipeslisted

# Recipes — codify a proven flow as a checklist, don't re-derive it A **recipe** is a committed markdown checklist that captures a *proven sequence of EXISTING actions* (commands, tool calls, gate steps) so the agent **replays a known-good path** instead of reasoning it out again. It is the safe, auditable Tier-1 of codified flows. It is **prose** — it references existing commands; it **never embeds a script the AI wrote** (that boundary is the shelved capsule tier below). Adapted clean-room from the "skillify" idea in gstack (MIT) — no gstack code was copied. ## Fits in the pipeline - A **Stage 6 (Build) accelerator** and a home for any recurring operational flow (release, no-orphans sweep, the QA-gate dispatch). Surfaced by the SessionStart **recipe index** (below). - Owned by the agent that runs the flow (the `owner`); **checked by `code-quality-reviewer`** before a recipe is trusted (maker–checker). Replaying a recipe is **GUIDED** (model-followed); the **lint** and the **index bound/sanitization** are **MECHANICAL**. ## Where recipes live `<project>/.vibegod/recipes/<slug>.md`, **committed** (diffable in PRs, shared with the team). ## The format Use the template at `${CLAUDE_PLUGIN_ROOT}/skills/recipes/templates/recipe.template.md`. Frontmatter + four sections: - **frontmatter:** `name`, `trigger` (phrases that should surface it), `owner` (a real vibegod agent), `created`, `last-verified` (date a human/green run last confirmed it), `proven-runs` (integer), an