grill-me

Interviews the user with sequential questions to refine vague plans into shared understanding.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/arndvs/ctrlshft --skill grill-me-arndvs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/arndvs/ctrlshft/tree/main/skills/grill-me
Command: npx skills add https://github.com/arndvs/ctrlshft --skill grill-me-arndvs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague ideas and fuzzy requirements lead to misaligned PRDs, wasted implementation effort, and designs that contradict the actual codebase. This Skill forces precision by interviewing you relentlessly about every aspect of a plan before any documentation or code is written. ## Core Features & Use Cases - Structured Interrogation: Walks down each branch of the design tree one question at a time, resolving dependencies between decisions and providing a recommended answer for each question. - Fuzzy Language Sharpening: Challenges vague or overloaded terms by proposing precise canonical definitions, and stress-tests domain flows with concrete edge-case scenarios. - Codebase Cross-Referencing: Verifies your claims against the actual code and surfaces contradictions between what you say and what the code does. - Use Case: Before writing a PRD for a new cancellation feature, run the interview to discover that your code cancels entire Orders while you assumed partial cancellation was possible, then resolve the discrepancy before committing to a design. ## Quick Start Ask the agent to grill you about your feature plan or design idea before writing a PRD.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I flesh out a vague feature idea before writing a PRD?▼

Run a structured interview that asks one question at a time about every aspect of the plan, walking each branch of the design tree. Each question comes with a recommended answer, and the session ends with a handoff to PRD writing, issue breakdown, or implementation.

How to validate that my design assumptions match the actual codebase?▼

Cross-reference each stated claim against the code during the interview. When a contradiction appears, such as code canceling entire Orders while you described partial cancellation, the conflict is surfaced explicitly so you can decide which is correct.

What happens after the requirements interview is complete?▼

After reaching shared understanding, you choose one of three handoff paths: write a formal PRD, break the decisions directly into GitHub issues, or start implementing immediately. The choice is left to the user.

What happens if context runs out during a long interview session?▼

The interview follows a standard handoff protocol that persists all decisions made so far to a working directory and provides a pickup command. A fresh conversation can then continue exactly where the previous one stopped.

When should I not use an interview-style requirements process?▼

Skip it when the requirement is already precise, fully documented, or trivially small, since the one-question-at-a-time format adds overhead. It is designed for vague or branching design spaces where decisions depend on each other.