grill

name	grill
position	both
description	Cut one REALIZED slice into user-testable delivery epics — the handoff from the product model to the delivery pipeline. /roadmap says which slice to build; the seven realize lenses have solved its design and /measure has stamped it realized — the marker /grill requires before it cuts. Each epic is a meaningful increment a user can open, exercise, and verify when delivered (the user-testability grain — never internal-only work), self-contained, referencing the slice's intent and lenses, never copying them. The cut is GRILLED before it is written — grilling draws the box from realized slice to delivery epics so nothing drifts outside the declared intents: every challenge cites a specific declared item (never taste), questions are asked plainly ONE AT A TIME with no recommendations attached, a tension closes only on the typed human answer (the record carries the push-back shown, the human's words, and the human-derived directive or reason — the agent never self-resolves), and an unresolved delivery-method choice becomes a cited decision question, never an assumption. Lens defects route back to their lens play. Ordered, every functionality covered or explicitly deferred. Direct-model-write (ADR 026, write-then-review): the cut is written to the live model first (each epic.md by author-epics, the spine epics index by the keyed persist), guarded once, then reviewed — nothing is COMMITTED before the checkpoint resolves, and cancel reverts the written tree. Writes only epics; opens no implementation issue — /start picks epics up one at a time. Position BOTH (#437, decision 24): /grill is self-contained — start-change opens its own branch at the head, the approved cut is committed as a feat(model) model delta, and the standard end sequence (commit-change → propose-change → review-change → merge-change) raises, reviews, and lands it — no manual /commit-change.
user-invocable	true

grill

Take one realized slice — a vertical product increment whose design the seven realize lenses (quality → ux → agentic → arch → measure → run) have already solved, stamped status: realized by /run — and cut it into epics: the ordered, user-testable delivery increments the delivery pipeline picks up. /grill sits below /roadmap (which says which slice to build next) and above /start (which opens one issue per epic). Epics are permanent: kept on the slice, stamped delivered on merge and kept in place as the product model's as-delivered record (ADR 019).

The grain of an epic is user-testability, not the functionality: when an epic is delivered, a user can open the product, do something, and see it work. An epic may thread several of the slice's functionalities; a functionality may yield several epics; internal machinery rides inside the epic that surfaces it, never alone. Every epic is self-contained — context (persona, systems, scope), acceptance criteria naming observable user behavior, and the one-line user_check — and references the slice's intent records and lenses, never copies them.

The cut is grilled, not relayed — and grilling is drawing the box: going from A (the realized slice — its declared intents, lenses, profile) to B (delivery epics) must have no drift, and the declared intents are the box the cut cannot step outside. The play pushes back steelman-hard — thin acceptance, untestable increments, tensions between the cut and what the slice declared — and every push-back cites the specific declared item it defends. A tension is resolved in the cut or explicitly accepted with a recorded reason; a defect in a lens itself is recorded and routed back to that lens's play, never patched here. The full cut persists atomically, only after the human approves it.

The grilling is a conversation with the human, and the record proves it (#436). The play builds its question list for the round — push-backs and open delivery-method questions — and asks one question at a time, simply stated: the citation and the question, nothing else. No recommendations, no option menus. A tension leaves live only on the typed answer; the round record carries the push-back actually shown, the human's own words, and the directive or reason derived from them. The agent revising the draft on its own never closes a tension. And where the box has no wall — an epic's user check depending on a delivery method the lenses never decided — the play asks a cited decision question; only the human draws that wall.

Pipeline position: both (#437, decision 24; confirmed by Kapil). /grill is SELF-CONTAINED: it opens and closes its own branch, like fix-bug. The realize work lands through its own three pipes — the FUNCTIONAL pipe (ux start → agentic → marketing end), the NON-FUNCTIONAL pipe (architecture start → quality → run end), and the DELIVER pipe (measure), each merging to main — so /grill no longer rides a branch another play opened. The D2 pipeline-position rule injects at the head (resolve or create the grill issue, cut the branch off fresh main, optional worktree, init STM) and keeps the close sequence at the tail: after the epics are persisted and verified, the locked cut is committed, raised, reviewed, and merged without the human having to remember . The bracketed change is the MODEL change only; /grill still opens no implementation issue and cuts no branch for an epic's delivery work — picking up an epic remains /start's job, one epic at a time. /grill works on one slice and remains the slice's end conceptually: nothing about a slice is finished until grill is.