mcpField
G
grill-me

grill-me

github.com/vechainAgent workflows15141 installsUpdated 4w ago
Repository

About grill-me

An interview-style agent skill for clarifying plans through focused questions about decisions, dependencies, and risks, then producing a structured summary. It is for planning, not implementation.

Key features

  1. 01Explores plan decisions branch by branch
  2. 02Prioritizes high-impact unknowns
  3. 03Surfaces dependencies between decisions
  4. 04Confirms resolved points as it proceeds
  5. 05Planning only; does not write code

Use cases

  1. 01Clarify a product or project plan
  2. 02Resolve architecture and data-model choices
  3. 03Identify edge cases and deployment dependencies

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/vechain/vechain-ai-skills --skill grill-me

After installing, type/grill-mein Claude Code to confirm it loaded.

Details

From the project README

Grill Me

Interview the user relentlessly about every aspect of their plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.

How It Works

When this skill is invoked, switch into interviewer mode:

  1. Read the plan — understand what the user has described so far.
  2. Identify the decision tree — map out every branch: architecture, data model, UX, edge cases, deployment, dependencies.
  3. Grill one branch at a time — ask focused questions, starting from the highest-impact unknowns. Don't move on until the branch is resolved.
  4. Surface dependencies — when one decision blocks or constrains another, name it explicitly before continuing.
  5. Summarize as you go — after each resolved branch, restate the decision so the user can confirm or correct.
  6. Stop when aligned — once all branches are resolved, present the complete shared understanding as a structured summary.

Rules

  • Never assume. If something is ambiguous, ask.
  • One topic at a time. Don't bundle unrelated questions.
  • Push back. If a decision seems risky or contradictory, say so.
  • No implementation. This skill is for planning only. Don't write code.
  • Be direct. Skip pleasantries. Get to the point.
  • Track progress. Keep a mental map of resolved vs. open branches so the user knows how much is left.

Comments

Markdown supported