grill-me

Resolve unclear requirements through one-question-at-a-time interview workflows.

Updated May 13, 2026
One-click install
npx skills add https://github.com/usetheodev/theo-ui --skill grill-me-usetheodev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/usetheodev/theo-ui/tree/main/.claude/skills/grill-me
Command: npx skills add https://github.com/usetheodev/theo-ui --skill grill-me-usetheodev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grill-me provides a structured, interview-driven approach to gather precise requirements by guiding the user through a decision-tree workflow, reducing ambiguity before drafting a plan. It adheres to a codebase-first principle, performing repository lookups (grep/read) to answer questions whenever possible, and persists conversations to knowledge-base/grills/{slug}-grill.md for downstream planning.

Core Features & Use Cases

  • Codebase-first questioning: answers come from the repository when possible, minimizing unnecessary user prompts.
  • Branching decision tree: iteratively resolves topic scope and dependencies to reach a concrete plan.
  • Conversation persistence: stores the grill transcript to knowledge-base/grills/{slug}-grill.md for /to-plan consumption.
  • Safe, structured interactions: one-question-at-a-time prompts to avoid cognitive overload and ensure convergence.

Quick Start

Provide a topic slug or a one-sentence description to start grilling.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I resolve unclear product requirements before planning?▼

You can resolve unclear product requirements through interview-driven discovery, which uses a one-question-at-a-time workflow and a branching decision tree to reduce ambiguity before drafting a plan.

What is the best way to gather precise requirements for non-trivial design topics?▼

The best way to gather precise requirements for non-trivial design topics is using an interview-driven discovery process that iteratively resolves topic scope and dependencies to reach a concrete plan.

How do I start a discovery interview when I only have a one-sentence topic description?▼

To start a discovery interview, you simply provide a topic slug or a one-sentence description, and the system guides you through safe, structured interactions to avoid cognitive overload.

Does interview-driven requirement discovery check the codebase to answer questions?▼

Yes, interview-driven requirement discovery applies a codebase-first principle, performing repository lookups like grep and read to answer questions whenever possible and minimizing unnecessary user prompts.

Can I persist discovery interview conversations for downstream planning?▼

Yes, you can persist discovery interview conversations by storing the transcript as a markdown file in the knowledge-base directory, making it available as input for downstream planning tasks.