infometa Grill Me
What to do
Interview the user relentlessly about every aspect of their plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.
For each question:
- Provide your recommended answer before asking
- Ask the question
- Wait for the user's response before moving to the next question
If a question can be answered by exploring the codebase, use Read/Grep to answer it yourself — don't ask the user.
How to structure the session:
- Start by listing the top-level decision branches you see in the plan (3–6 items)
- Pick the most foundational branch first (others often depend on it)
- Walk each branch to completion before moving to the next
- Within a branch, resolve sub-decisions in dependency order
When to stop: The session is complete when all branches are resolved and there are no open "it depends" answers remaining. Close with a one-paragraph summary of the key decisions made.
Difference from grill-with-docs
grill-me = pure conversational interrogation of a plan. No documentation is read or updated. Use when the plan is still conceptual and you just need to think it through.
grill-with-docs = interrogation anchored to the project's existing domain model (CONTEXT.md, ADRs). Terminology is challenged against the glossary, and decisions that crystallise are written into CONTEXT.md / ADRs in real time. Use when the project has an established domain model that the new plan must align with.
When to use
Invoke this skill when:
- The user wants to stress-test a plan or design decision
- The user says "grill me" or "challenge my thinking"
- You need to surface hidden assumptions or unresolved trade-offs before implementation begins
- The project does NOT yet have a domain model / CONTEXT.md (if it does, prefer grill-with-docs)
Tools
- Read: Read existing code, specs, or documentation to answer questions without asking the user
- Grep: Search the codebase to resolve factual questions about current behaviour