grill-me

Interview users one question at a time to resolve ambiguous plans.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/vh2224/forge-executor --skill grill-me-vh2224
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/vh2224/forge-executor/tree/main/src/resources/skills/grill-me
Command: npx skills add https://github.com/vh2224/forge-executor --skill grill-me-vh2224

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps turn a vague or underspecified plan into a fully aligned decision path by interviewing the user one question at a time. It is useful when important choices are still fuzzy, dependent branches are unresolved, or hidden assumptions could derail execution later.

Core Features & Use Cases

  • Sequential interrogation: Asks one question at a time in dependency order so each answer informs the next.
  • Recommendation-led prompts: Includes a suggested answer and short rationale so the user can confirm or redirect quickly.
  • Codebase-aware grounding: Checks existing repository conventions and prior decisions before asking questions already answered by the code.
  • Use case: Use this skill to stress-test a product plan, resolve architecture tradeoffs, or clarify milestone scope before writing implementation context.

Quick Start

Ask the assistant to grill your plan and resolve every material decision branch before execution.

Frequently Asked Questions about grill-me

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve ambiguous plan gaps before starting implementation?

Resolve ambiguous plan gaps by interviewing stakeholders one question at a time in dependency order, surfacing hidden assumptions and tradeoffs until all material decision branches are closed before execution.

What is sequential interrogation for design review and how does it work?

Sequential interrogation for design review works by asking one question at a time, using your previous answers to inform the next prompt until unresolved tradeoffs and dependency orders are fully aligned.

How do I stress-test a product plan to expose hidden assumptions?

Stress-test a product plan by applying recommendation-led questions that suggest an answer with a short rationale, allowing you to quickly confirm or redirect the decision path to expose hidden assumptions.

Can I use codebase-aware grounding to avoid asking questions already answered by the code?

Yes, codebase-aware grounding checks existing repository conventions and prior decisions before asking questions, ensuring the interrogation focuses only on unresolved gaps not already answered by the code.

What is the best way to capture durable decision context for architecture tradeoffs?

Capture durable decision context for architecture tradeoffs by running a structured interview that closes all material decision branches and records the alignment context for future reference.

When should I not use an interrogation approach for planning conversations?

Avoid using an interrogation approach for planning conversations when there are no hidden assumptions, dependency orders, or unresolved tradeoffs to surface, or when execution can proceed without aligned decision branches.