One-click install
npx skills add https://github.com/sethvoltz/dotfiles --skill grill-me-sethvoltz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/sethvoltz/dotfiles/tree/main/claude/claude/skills/grill-me
Command: npx skills add https://github.com/sethvoltz/dotfiles --skill grill-me-sethvoltz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you pressure-test a plan or design before you commit, uncovering hidden assumptions, missing dependencies, and weak decisions early.

Core Features & Use Cases

  • Relentless Interrogation: Asks one question at a time to systematically explore every branch of a decision tree.
  • Decision Support: Provides a recommended answer for each question so you can move faster while still thinking rigorously.
  • Codebase-Aware Review: When an answer can be determined from the repository, it checks the codebase instead of guessing.
  • Use Case: Great for design reviews, architecture discussions, and product planning sessions where you want a thorough challenge rather than a quick summary.

Quick Start

Use the grill-me skill to interrogate my plan one question at a time and recommend the best answer for each branch.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I stress-test a product plan before committing to development?

To stress-test a product plan, interrogate it one question at a time to surface hidden assumptions, missing dependencies, and weak decisions. This rigorous review applies decision tree questioning to product proposals, technical designs, and architecture discussions to uncover gaps before commitment.

How does codebase exploration work during a design review?

Codebase exploration during a design review checks the repository context to derive answers instead of guessing. When a question about the plan can be resolved from repository context, the review examines the codebase to validate assumptions and resolve architecture or technical design questions.

What's the best way to identify gaps and assumptions in an architecture proposal?

The best way to identify gaps and assumptions in an architecture proposal is branch-by-branch interrogation that asks one question at a time. This systematically explores every decision tree branch while providing recommended answers for each branch to ensure rigorous thinking.

Can I use decision tree questioning for interviewing and requirements gathering?

Yes, decision tree questioning can be applied to interviewing and requirements gathering. By asking one question at a time with recommended answers for each branch, you systematically explore requirements, surface unresolved decisions, and apply rigorous review to product planning sessions.

Does this approach work for technical designs that require repository context?

Yes, this approach works for technical designs requiring repository context. When an answer can be derived from the codebase, it checks the repository instead of guessing, making it suitable for codebase-aware design reviews and architecture discussions that depend on existing code.