grill-with-docs

Load and apply grill to settle decisions that materially affect the requested outcome, acceptance criteria, constraints, dependencies, or risk. Keep the user's requested outcome and accepted constraints as the boundary; leave optional enhancements out unless the user accepts them or they block delivery. Load and apply domain-modeling only when the agreed work changes domain terms or relationships, or makes a durable architectural trade-off. Existing vocabulary can be read without creating or editing domain records.

One observable outcome can span several files. Keep its interview focused and capture the agreed behavior in one executable issue or brief when no material contract or dependency graph needs a durable spec. For broader work, preserve the accepted scope and identify the first end-to-end tracer bullet through the critical path or a risky assumption before planning follow-on slices.