grill-me

Identify gaps and risks in product plans, specifications, and architecture.

8|Updated May 18, 2026
One-click install
npx skills add https://github.com/lalulali/vespyr --skill grill-me-lalulali
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/lalulali/vespyr/tree/main/.agents/skills/grill-me
Command: npx skills add https://github.com/lalulali/vespyr --skill grill-me-lalulali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you uncover weak assumptions, missing requirements, and risky architecture choices before implementation begins, reducing rework and misalignment.

Core Features & Use Cases

  • Requirements interrogation: Walk through product goals, success criteria, and constraints one question at a time.
  • Architecture and trade-off review: Pressure-test stack decisions, dependencies, edge cases, and codebase logic.
  • Decision capture: Consolidate the final agreed-upon choices into project memory for later execution.
  • Use case: Use it when you have a plan, design, or proposal and want a rigorous Socratic review before coding.

Quick Start

Ask the skill to grill your plan until the key assumptions, trade-offs, and decisions are fully resolved.

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 architecture decisions before implementation?

To stress-test architecture decisions before implementation, use a Socratic review process that inspects project documents to identify gaps, risks, and trade-offs through stepwise questioning and captures resolved decisions in artifacts memory.

What is the best way to uncover missing requirements during a design review?

The best way to uncover missing requirements during a design review is to interrogate product goals and constraints one question at a time, ensuring full alignment on technical trade-offs before coding begins.

Can I use Socratic questioning to pressure-test stack trade-offs and edge cases?

Yes, you can use Socratic questioning to pressure-test stack trade-offs and edge cases by walking through codebase constraints and dependencies stepwise, ensuring risky architecture choices are resolved before build.

Does pre-build alignment work for both discovery sessions and architecture reviews?

Pre-build alignment works for both discovery sessions and architecture reviews by applying stepwise questioning to requirements, codebase constraints, and technical trade-offs, consolidating agreed-upon choices into project memory.

When do I need a Socratic review of my product plan?

You need a Socratic review of your product plan when you have a design or proposal ready and want to rigorously uncover weak assumptions, missing requirements, and risky architecture choices before implementation begins.