grill-me

Interrogates design plans through structured Q&A and updates CONTEXT.md glossaries and ADRs inline.

138|5|Updated Sep 19, 2024
One-click install
npx skills add https://github.com/macalbert/envilder --skill grill-me-macalbert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/macalbert/envilder/tree/main/.github/skills/grill-me
Command: npx skills add https://github.com/macalbert/envilder --skill grill-me-macalbert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design plans often contain fuzzy terminology, hidden contradictions with existing code, and undocumented decisions that cause confusion later. This Skill stress-tests a plan through relentless one-at-a-time questioning, sharpening domain language and recording decisions as they crystallize. ## Core Features & Use Cases - Socratic Plan Interrogation: Walks each branch of the design tree, asking one question at a time with a recommended answer and rationale. - Domain Glossary Maintenance: Detects terminology conflicts and updates CONTEXT.md inline using a strict glossary format, keeping it free of implementation details. - ADR Capture: Offers Architecture Decision Records only when a decision is hard to reverse, surprising, and the result of a real trade-off, following a minimal ADR template. - Use Case: Before implementing a new feature, run a grilling session to validate the design against existing ADRs, resolve ambiguous terms like "account" vs "customer", and record the key architectural decisions in docs/adr/. ## Quick Start Ask the assistant to grill you on your implementation plan for a new feature and update the project glossary and ADRs as decisions are made.

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 software design plan before implementation?

Run a grilling session that interviews you about every branch of the design tree, one question at a time, with a recommended answer for each. It explores the codebase to answer questions itself and stops when all branches are resolved or you say enough.

How to maintain a domain glossary in CONTEXT.md?

Define each term with a one or two sentence definition, list avoided synonyms, and keep the file free of implementation details. The skill updates CONTEXT.md inline whenever a term is resolved during discussion, creating the file lazily if it does not exist.

When should I write an Architecture Decision Record?

Write an ADR only when a decision is hard to reverse, surprising without context, and the result of a genuine trade-off between alternatives. If any of these three conditions is missing, skip the ADR to avoid documentation noise.

Does this work with multi-context or monorepo codebases?

Yes. If a CONTEXT-MAP.md exists at the repo root, the skill reads it to locate each context's CONTEXT.md and context-specific ADR directories. Single-context repos use one root CONTEXT.md and a shared docs/adr/ folder.

What happens when a new decision contradicts an existing ADR?

The skill references existing ADRs in docs/adr/ to avoid re-litigating settled decisions. When a new decision contradicts one, it flags the conflict explicitly so you can consciously supersede the old record.