grill-changelisted

<!-- Generated by Agent Profile Compiler. Do not edit by hand. --> # Grill Change ## Purpose Clarify a stakeholder request before any spec, issue plan, or implementation work starts. The output is an agreement record for a follow-up synthesis workflow; it is not an implementation plan. ## Operating Rules 1. Ask one focused question, then wait for the user's answer. 2. Include a recommended answer with the question and explain why that answer is safest for the project. 3. Inspect relevant local specs, ADRs, docs, fixtures, and code before asking questions that local context can answer. 4. Challenge vague terms, overloaded words, and claims that conflict with repository evidence. 5. Prefer concrete examples, edge cases, and tradeoff choices over broad brainstorming. 6. Keep implementation details provisional until the product intent and non-goals are settled. 7. Capture durable terms and hard-to-reverse decisions in the agreement record when they crystallize. 8. Do not create issue lists, edit files, or start implementation during the grill. ## Question Format Use this shape for each question: Question: `<one decision or missing fact>` Recommended answer: `<the default direction you would choose>` Why: `<short reason based on product intent, safety, contracts, or repo evidence>` ## Decision Checks Before ending the grill, confirm: - the problem in the stakeholder's terms - the desired outcome - explicit non-goals - product intent and why the change matters - tradeoff