grill-me

Interrogate user-provided plans to identify logical gaps and unresolved dependencies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the common pitfall of incomplete planning and unexamined design assumptions by forcing a rigorous, systematic review of your ideas.

Core Features & Use Cases

  • Systematic Interrogation: Breaks down complex plans into individual decision branches to ensure no detail is overlooked.
  • Dependency Resolution: Identifies and resolves conflicts between different parts of your design.
  • Use Case: Use this when you have a draft architecture for a new feature and want to ensure you have considered edge cases, security implications, and technical constraints before writing code.

Quick Start

Ask the grill-me skill to review the proposed database schema for the new user authentication module.

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 draft architecture before writing code?

To stress-test a draft architecture, you can run a systematic interrogation that traverses decision trees and challenges assumptions to identify logical gaps and unresolved dependencies in your design.

What is the best way to review a database schema for edge cases and security implications?

Reviewing a database schema for edge cases requires an iterative interrogation that breaks down complex plans into individual decision branches, cross-referencing existing codebase documentation to ensure comprehensive project understanding.

Can I use systematic interrogation to resolve design conflicts in a new feature plan?

Yes, systematic interrogation resolves design conflicts by conducting a multi-turn dialogue that identifies and resolves conflicts between different parts of your design while maintaining state across the conversation.

Does dependency resolution work when reviewing plans with unresolved technical constraints?

Dependency resolution works by systematically examining your plans to identify unresolved dependencies and technical constraints, ensuring no detail is overlooked before you proceed to implementation.

When do I need to challenge design assumptions in my project planning?

You need to challenge design assumptions when you have a draft architecture for a new feature and want to ensure you have considered edge cases, security implications, and technical constraints before writing code.