grill-me
Grill Me
Purpose
Rigorously interview the user on an idea, plan, or design until there is shared understanding. Walk each decision branch, resolve dependencies, and for each question present 2-3 trade-off scenarios plus a recommendation.
Interaction Contract
- Ask one question at a time.
- Keep the user involved at each branch decision.
- Every question must include a recommended answer and brief rationale.
Evidence-First Tie-Break Rule
When deciding whether to ask or inspect:
- If a codebase exists and a question is answerable with quick read-only checks, inspect first.
- Otherwise, ask the user directly.
- If evidence and user statement conflict, surface the conflict and ask for resolution.
Workflow
- Determine whether a codebase exists in the current workspace.
- Restate the idea/plan/design in one sentence.
- Identify the highest-risk unresolved decision.
- Either gather quick objective evidence (if available) or ask one question.
- Record answer, recommendation, and the dependency it unlocks.
- Repeat until no material branch remains unresolved.
- Present a "Decision Log Overview" (resolved decisions, open risks, final recommendations).
- Ask the user to confirm the overview or provide corrections.
- If the user requests a written artifact, save a concise specification to
docs/specs/YYYY-MM-DD-<topic>.md. - If a specification file was created, check it for placeholders, contradictions, ambiguity, or scope mismatch, then ask the user to review it.
Output
Maintain a running decision log with:
- Decision
- Current status (resolved or open)
- Recommendation
- Blocking dependencies
End with a "Decision Log Overview" that summarizes:
- Final resolved decisions
- Open risks accepted by the user
- Recommended next actions
If a specification is written, it must include at minimum:
- Problem
- Constraints
- Decisions (with rationale)
- Proposed approach
- Open risks (and mitigations)
- Next actions
Stop Condition
Stop when all material branches are resolved or explicitly accepted as open risks, and the user confirms the final decision log overview.
If the user asks to stop or pivot, summarize the current decision-log state and end the current grilling cycle.
More from goblindegook/skills
rca
Use when asked for RCA, 5-Whys, postmortem, causal-tree analysis, or help identifying root causes for incidents, defects, outages, delays, or quality regressions.
10tdd
Use when implementing behavior changes or bug fixes where automated tests can drive the implementation, or when asked to use TDD.
8roundtable
Review a project or feature from the point of view of a set of personas. Use this when the user asks for multi-perspective critique — "review from the POV of X, Y, Z", "what would a [role] think of this?", "roundtable review", "get different perspectives on this". Each persona reads the actual source code before commenting, then all personas discuss together to agree on a prioritised top 5 list. If no personas are provided, ask the user and offer suggestions.
4