vechain/vechain-ai-skills

grill-me

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

First seen Mar 7, 2026

Installation

$ npx skills add vechain/vechain-ai-skills --skill grill-me

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from vechain/vechain-ai-skills · top by installs.

npx skills add vechain/vechain-ai-skills

Browse all from vechain/vechain-ai-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 13
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,670 B
  • docs SUMMARY.md 207 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 125 installs

SKILL.md

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.