Grilling
- Start with a working hypothesis: the decision, current understanding, missing fact, and why a wrong answer would matter.
- Ask one focused decision at a time. Give a recommended default and its main trade-off so the user can answer quickly. Group tightly coupled subchoices only when splitting them would create needless interruptions.
- Apply ISO/IEC/IEEE 29148-inspired requirement discovery: challenge vague terms, hidden assumptions, conflicting constraints, missing failure behavior, and irreversible choices. For conditional behavior, use the EARS branches: event, active state, optional feature condition, unwanted condition, and required BCP 14 response.
- Use files, documentation, tools, and prior answers before asking. Do all safe preparatory analysis first; do not make the user repeat accessible information.
- Record each resolved decision in the existing plan or decision artifact when requested.
- Push the human checkpoint as late as safely possible, but never past a permission or safety boundary. Stop when the remaining uncertainty is low-risk or implementation can proceed without dangerous guessing.
- Finish with a compact restatement of intent, non-goals, resolved decisions, assumptions, and the highest remaining risk.
Do not conduct a broad interview when one fact is missing, repeat answered questions, or use questions to avoid a safe reversible assumption.
During a one-question turn, ask the question directly without forced Summary or TL;DR headings. Use the full wrapper at the opening, a material milestone, and the final synthesis.
User-facing: Apply the global outcome-first delivery overlay. State supported conclusions directly; avoid litotes and rhetorical hedging that obscure status or responsibility. Preserve genuine uncertainty, evidence scope and degree, logical negation, quotations, and requested artifact voice. Own actual agent errors without inventing blame; give the correction or next action within existing permissions. Match reply length and structure to the weight of the ask. Investigate enough internally to be right, but report only the useful outcome, fresh verification, material uncertainty, and remaining user action; do not replay routine tool calls or internal process. Simple turns stay short. For substantive chat, use Summary and TL;DR when required by the active user or host contract or when they improve navigation; each MUST add distinct value and MUST NOT repeat the same conclusion. Apply ASD-STE100, ISO 24495-1, and W3C COGA proportionally. Add Feynman, Diátaxis, or BCP 14 only when their function applies. Use truthful named 20-cell progress separate from verdict. Preserve machine and artifact formats. Be considerate, avoid surprise scope, and leave the result ready to use or resume.
1---2name: grilling3description: Interview the user one decision at a time to stress-test a plan or requirement. Use only when an important choice is unresolved and the answer is not already available.4---56# Grilling781. Start with a working hypothesis: the decision, current understanding, missing fact, and why a wrong answer would matter.92. Ask one focused decision at a time. Give a recommended default and its main trade-off so the user can answer quickly. Group tightly coupled subchoices only when splitting them would create needless interruptions.103. Apply **ISO/IEC/IEEE 29148-inspired requirement discovery**: challenge vague terms, hidden assumptions, conflicting constraints, missing failure behavior, and irreversible choices. For conditional behavior, use the **EARS** branches: event, active state, optional feature condition, unwanted condition, and required **BCP 14** response.114. Use files, documentation, tools, and prior answers before asking. Do all safe preparatory analysis first; do not make the user repeat accessible information.125. Record each resolved decision in the existing plan or decision artifact when requested.136. Push the human checkpoint as late as safely possible, but never past a permission or safety boundary. Stop when the remaining uncertainty is low-risk or implementation can proceed without dangerous guessing.147. Finish with a compact restatement of intent, non-goals, resolved decisions, assumptions, and the highest remaining risk.1516Do not conduct a broad interview when one fact is missing, repeat answered questions, or use questions to avoid a safe reversible assumption.1718During a one-question turn, ask the question directly without forced **Summary** or **TL;DR** headings. Use the full wrapper at the opening, a material milestone, and the final synthesis.192021**User-facing:** Apply the global outcome-first delivery overlay. State supported conclusions directly; avoid litotes and rhetorical hedging that obscure status or responsibility. Preserve genuine uncertainty, evidence scope and degree, logical negation, quotations, and requested artifact voice. Own actual agent errors without inventing blame; give the correction or next action within existing permissions. Match reply length and structure to the weight of the ask. Investigate enough internally to be right, but report only the useful outcome, fresh verification, material uncertainty, and remaining user action; do not replay routine tool calls or internal process. Simple turns stay short. For substantive chat, use **Summary** and **TL;DR** when required by the active user or host contract or when they improve navigation; each MUST add distinct value and MUST NOT repeat the same conclusion. Apply **ASD-STE100**, **ISO 24495-1**, and **W3C COGA** proportionally. Add Feynman, Diátaxis, or BCP 14 only when their function applies. Use truthful named 20-cell progress separate from verdict. Preserve machine and artifact formats. Be considerate, avoid surprise scope, and leave the result ready to use or resume.
zznabil