Specs.

The problem.

An agent will fill a gap in intent. If the gap is a document anyone can mark approved, the target moves without anyone deciding.

What it is.

Work that needs a decision starts as a spec. The grill asks questions until every section is testable, and finishing the grill is what approves it. Nobody sets approved by hand. Then the spec splits into items, each carrying its section's framing, so the agent does not re-read the whole spec.

A change of scope reopens the grill. Closing a spec is final, and later work is a new spec.

The list in the product is also the preamble and the design-set documents, plus the folder they sync to. That lives on the spec page.

Example · project Core Platform

CORE-P3 · draft

Export traces

↓ /graphban-grill — questions until every section is testable

CORE-P3 · approved

The grill finished. That is the approval.

↓ three items, each in backlog, each with its section

CORE-15 · backlog

section of Export traces

CORE-16 · backlog

section of Export traces

CORE-17 · backlog

section of Export traces

request_rebaseline sends it back to the grill. The current baseline governs until a new one is approved.

What it isn't.

Not a document anyone can mark approved.

Spec to done