roomi-fields/roomis-grillhouse

An elephant–goldfish framework for building with Claude Code agents. You create a project, open Claude Code
in it, and the session grills you on what the project must be — its goals, the mature products it
should measure itself against, its components and their interfaces. It then writes the project's
charter and reference documents, opens the first tickets, and runs the work through a supervisor
and fresh developer agents, each ticket reviewed before it closes.
The skills speak French.
## The elephant and the goldfish
Grillhouse implements the Elephant–Goldfish Model: an agent that holds the context writes, agents that hold
none review, and a human settles the trade-offs. Dave Rensin
describes the model,
and Google open-sourced its own plugin for it,
EGM, in October 2026. Grillhouse was built on the same
principle independently, with its first public commit on 2026-10-07, and applies it to every ticket, from its
design to its merge.
| Elephant–Goldfish | Grillhouse |
| The elephant holds the context and drafts | The supervisor, and the explorer, which writes the plan of a ticket |
| Goldfish: fresh, read-only reviewers | The questioner (the plan), the reviewer (the lot), each a fresh sub-agent |
| The human approves the design before code | The grill; the owner validates architecture, frame and interfaces |
| Design before implementation | A decision is taken and written in the ticket before any code |
| Not for a small, clear fix | A gesture without new behaviour leaves the circuit of code |
| A drift report between documents and code | Guards hold interfaces and languages against the code at every pass |
Grillhouse carries the model past the design. A fresh agent, the testwriter, writes the tests from the
specification before any code. The developer works under write locks, and only on the packages of the plan.
The reviewer returns one conformity line per element that the lot adds, changes or removes.
Two practices of EGM are not in Grillhouse yet:
a design review by several fresh lenses, before the owner validates the design;
a drift report on the architecture's prose.
Both are planned.
## 1. What it does
| Moment | What happens |
| npx @roomi-fields/grillhouse init [prefix] | Creates a project from the template of a project, templates/projet/ (as create-turbo creates one from its example): the example application and its tests, its configurations, its charter and its settings, gitignore and npmignore named .gitignore and .npmignore; declares @roomi-fields/grillhouse in its devDependencies; prepares it (git, Beads and its ticket store, CodeGraph and its index, Beads' hooks folder, the plugins its settings declare, npm install, whose prepare places the git hooks); writes what the update writes (its turbo.json, the status line of its settings, the frame's version) and the generated files; ends on one commit. A directory that is not empty is refused. |
| Every session start | A hook lists the key elements still empty (arbitration criteria, charter fields, architecture, frame, interfaces, lexicon) and the session proposes to grill them, each with its recommendation. It keeps proposing until they are filled. |