| name | grill-me |
| description | Interview engine that grills the user about a requirement, plan, or design through relentless, structured questioning, asking 1-2 focused questions per turn until every branch of the decision tree is resolved. Use directly when the user explicitly asks to be grilled without Wiki lookup. |
Grill Me
Challenge the user's plan or design through relentless questioning.
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.
Questions drawn only from what the plan states or what the user flags as undecided will miss two blind spots that live outside the text:
- Unknown knowns — standards the user holds but never wrote down because they feel obvious; they surface as "that's not what I meant" only after the build. Restate the plan's implicit assumptions as concrete claims for the user to veto now.
- Unknown unknowns — alternatives, risks, and ripple effects the user never considered. Surface what the plan silently excluded.
Rules:
- Before the first question, read
.superharness/spec/learnings/index.md and any topic page relevant to the plan; recorded learnings are settled decisions — do not re-ask what they already answer.
- If a question can be answered from the codebase or from the information sources the caller has put in play, get the answer there instead of asking the user. Only questions no available source can answer deserve the user's time.
- Ask 1-2 focused questions per turn. Do not dump all questions at once.
- For each question, state your recommended answer and reasoning, then ask if I agree or have a different take.
- When a branch is resolved, explicitly mark it done and move to the next.
- Keep going until all branches are resolved. Do not stop early or summarize prematurely.