grill-me

Ask one targeted question at a time to validate project plans and technical designs.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/a35506322/Lab.Todo --skill grill-me-a35506322
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/a35506322/Lab.Todo/tree/main/.cursor/skills/grill-me
Command: npx skills add https://github.com/a35506322/Lab.Todo --skill grill-me-a35506322

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of misalignment and hidden gaps in project plans and technical designs, which often lead to costly rework and failed implementations due to unspoken assumptions or unaddressed edge cases.

Core Features & Use Cases

  • Relentless Plan Interrogation: Asks targeted questions about every aspect of a plan or design to uncover unspoken assumptions and missing requirements.
  • Decision Tree Resolution: Walks through each branch of the design decision tree to resolve dependencies between choices one by one.
  • Context-Aware Questioning: Explores the codebase to answer questions that can be resolved with existing project context, rather than asking the user.
  • Use Case: For example, if you are designing a new todo app API, use this Skill to grill your plan for edge cases like invalid input handling, authentication flows, and rate limiting before writing any code.

Quick Start

Use the grill-me skill to stress-test my new todo app feature plan.

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 technical design plan to find hidden gaps?

To stress-test a technical design plan, you need relentless questioning that asks one targeted question at a time to uncover unspoken assumptions, missing requirements, and unaddressed edge cases before implementation begins.

What is decision tree resolution for project plan validation?

Decision tree resolution for plan validation involves walking through each branch of a design to resolve dependencies between choices one by one, ensuring shared understanding and eliminating misalignment before coding starts.

How do I perform a gap analysis on a software design before implementation?

Performing a gap analysis on a software design requires structured interrogation that explores the codebase for context and asks targeted questions about edge cases, authentication flows, and input handling to validate requirements.

Can I use automated requirement alignment to check my API design for edge cases?

Yes, automated requirement alignment checks your API design by applying context-aware questioning that resolves existing project context from the codebase first, then asks you about remaining unspoken assumptions like rate limiting.

What are the limitations of using relentless questioning for plan validation?

The limitation of relentless questioning for plan validation is that it resolves dependencies one question at a time, requiring sequential user interaction rather than batch processing, which may slow down rapid prototyping workflows.