to-spec

Turn a grilled conversation into a destination spec and vertical-slice tickets that each fit one smart-zone session (~150,000-token working budget).

A goal loop on a whole spec is a trap. Vertical tickets, not horizontal.

When

A feature will take more than one session (or survive an auto-compact).
A grilled conversation needs to become a durable plan.
Tempted to point a goal loop at the whole spec in one long window.

Pipeline

Grill (shared understanding; say "zoom out" when questions drown in jargon)
Write the destination spec — run the grill mechanics from grill-execute-clear first; grilling produces the shared understanding the spec records. The destination spec is cross-session shared truth (binding until archived); the grill mini-spec is in-session confirmation (disposable).
Split into tickets in the same conversation while smart-zone remains — push back until slices are vertical (DB+API+UI end-to-end), not horizontal layers
Implement one ticket per focused session (optional TDD only at pre-agreed seams; reject tautological tests)
Review on two axes: standards sub-agent + spec sub-agent