grill-with-change

Interrogate an OpenSpec change until its requirements, design, specs, and tasks tell one coherent story. Challenge terminology against project docs and code, sharpen vague language, and probe boundaries with concrete scenarios.

Hard Rules

• Ask exactly one user-facing question at a time and wait for the answer. State why the decision matters and recommend an answer when one is defensible.
• Inspect local evidence instead of asking questions it can answer.
• Only user-confirmed decisions may become normative. Repository facts provide context; assistant recommendations remain OPEN until confirmed.
• During a phase, update only working state. Batch-write formal artifacts after the user confirms that the phase can close.
• Do not implement application code or edit CONTEXT.md or ADRs. Edit only the target change's OpenSpec artifacts.
• Answer side questions directly, then return to the current branch unless the answer changes the decision tree.

Locate And Inspect The Change