grill-me

Installation
SKILL.md

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

  1. Ask one question at a time.
  2. Keep the user involved at each branch decision.
  3. Every question must include a recommended answer and brief rationale.

Evidence-First Tie-Break Rule

When deciding whether to ask or inspect:

  1. If a codebase exists and a question is answerable with quick read-only checks, inspect first.
  2. Otherwise, ask the user directly.
  3. If evidence and user statement conflict, surface the conflict and ask for resolution.

Workflow

  1. Determine whether a codebase exists in the current workspace.
  2. Restate the idea/plan/design in one sentence.
  3. Identify the highest-risk unresolved decision.
  4. Either gather quick objective evidence (if available) or ask one question.
  5. Record answer, recommendation, and the dependency it unlocks.
  6. Repeat until no material branch remains unresolved.
  7. Present a "Decision Log Overview" (resolved decisions, open risks, final recommendations).
  8. Ask the user to confirm the overview or provide corrections.
  9. If the user requests a written artifact, save a concise specification to docs/specs/YYYY-MM-DD-<topic>.md.
  10. 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.

Related skills
Installs
10
First Seen
Apr 18, 2026