grill-me

Analyze design and implementation plans against code and documentation.

1|Updated Jan 17, 2026

Search Tags:#decision making #architectural review #stress testing #design evaluation #plan analysis

Ready to run

npx skills add https://github.com/alexandersumer/config --skill grill-me-alexandersumer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/alexandersumer/config/tree/main/.agents/skills/grill-me
Command: npx skills add https://github.com/alexandersumer/config --skill grill-me-alexandersumer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify potential flaws in design, proposal, implementation plans, and architectural choices by applying a structured questioning approach.

Core Features & Use Cases

Stress Testing: Analyze plans against code, domain language, and existing decisions.
Focus on Key Decisions: Uncover the most critical, architecture-altering decisions.
Challenge Vocabulary: Address discrepancies between the plan's terminology and established documentation.
Documentation Update: Suggest updates to CONTEXT.md or ADRs if needed.

Quick Start

Use the grill-me skill to grill a design plan on its potential vulnerabilities.

Frequently Asked Questions about grill-me

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

FAQPage Schema

What is stress testing a design plan and why do I need it?▼

Stress testing a design plan involves challenging its code, domain language alignment, and existing documentation to identify critical, architecture-altering decisions and potential vulnerabilities before implementation begins.

How do I evaluate architectural decisions in an implementation plan?▼

You evaluate architectural decisions by applying a structured questioning approach that targets vocabulary discrepancies and checks alignment with existing project documentation like CONTEXT.md and ADRs.

Can I use this to check if my proposal aligns with existing project documentation?▼

Yes, stress testing explicitly requires alignment with existing project documentation, identifying vocabulary discrepancies between your proposal's terminology and established decisions, and suggesting updates to CONTEXT.md or ADRs if needed.

What is the best way to uncover critical vulnerabilities in a software proposal?▼

The best way to uncover vulnerabilities is to grill the plan against code, domain language, and existing decisions to isolate the most critical, architecture-altering choices that require immediate attention.

Do I need existing ADRs to perform a design evaluation on my plan?▼

Existing ADRs are not strictly required to perform a design evaluation, but having them or a CONTEXT.md file allows the stress test to better identify vocabulary discrepancies and suggest accurate documentation updates.