grilling
Use when the user explicitly requests a grilling interview to resolve or challenge material decisions. For a written critique, review the artifact directly.
SKILL.md.claude/skills/grilling/SKILL.md
GitHubGrilling
Interview the user about a plan, decision or idea when they explicitly request that interaction. A request for written critique does not itself request an interview.
Map material decisions and their prerequisites. Ask a manageable batch of independent questions whose prerequisites are settled; defer dependent questions until their answers can use the earlier decisions. Include a recommendation and its assumptions where useful, allowing the user to disagree.
Look up available facts yourself. Ordinary local or documentation lookups stay inline; delegate only bounded work that benefits from it. Decisions requiring a live participant remain pending; do not answer on that participant's behalf.
Recompute the unresolved choices after each answer. Stop when the decisions needed for the requested outcome are settled, explicitly deferred or identified as blocked. Do not exhaust every imaginable branch. Summarize material agreements and remaining uncertainty; carry authorization forward for any next step already requested, without treating the interview itself as implementation authority.
If the necessary respondent is absent, prepare a questionnaire for their role and knowledge gap. Ask the present user only for missing recipient context and desired outcome; do not force two exchanges when these were supplied. Drafting a questionnaire does not authorize sending it.
Documentation is optional. When requested, use domain-modeling for settled terms and qualifying ADRs; a repository's existence alone does not authorize these writes.