Grill

Turn fuzzy or contradictory plans into shared understanding and authoritative planning artifacts. Grill owns clarification, not tickets or implementation.

Inputs

• An idea, plan, question, PRD, ADR set, or existing spec to challenge.
• The current repo, caller context, and workflow config when available.

Invocation Threshold

Explicit invocation always starts. Invoke implicitly only when an unresolved product, domain, scope, or architecture decision could change behavior, ticket boundaries, risk, dependencies, or required proof after available evidence is checked. Say what ambiguity caused the pause. Do not invoke for routine details, harmless preferences, or discoverable facts.

Context