Verified:GitHub

grill-with-docs

Runs a structured interview to refine plans while generating ADRs and a glossary.

Updated Jul 16, 2026

Search Tags:#domain modeling #adr #glossary #interview #design review #plan validation #architecture decision record

One-click install

npx skills add https://github.com/MaksymilianCzadowski/skills --skill grill-with-docs-maksymilianczadowski

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/MaksymilianCzadowski/skills/tree/main/skills/engineering/grill-with-docs
Command: npx skills add https://github.com/MaksymilianCzadowski/skills --skill grill-with-docs-maksymilianczadowski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions, vague terms, and unexamined trade-offs that surface too late. This Skill stress-tests a plan through a relentless question-and-answer session while capturing the decisions and terminology it uncovers as durable documentation. ## Core Features & Use Cases - Adversarial plan review: Runs a grilling session that challenges assumptions, scope, and design choices in a plan or design. - Documentation as a byproduct: Produces Architecture Decision Records (ADRs) and a glossary as the interview progresses, so reasoning is preserved. - Domain modeling integration: Builds on the /domain-modeling skill to ground questions in the problem domain. - Use Case: Before starting implementation of a new service, run a grilling session on your design doc to expose weak spots and walk away with ADRs and a shared glossary for the team. ## Quick Start Ask the assistant to run a grilling session on your current plan or design document and record the decisions as ADRs and a glossary.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema

How do I stress-test a software design before implementation?▼

Run a grilling session on your plan or design document. The skill asks relentless questions about assumptions, scope, and trade-offs, and records the outcomes as ADRs and a glossary so the reasoning is preserved.

What is an ADR and when should I write one?▼

An ADR (Architecture Decision Record) documents a significant design decision, its context, and its consequences. Write one whenever a non-obvious trade-off is made; this skill generates ADRs automatically during the interview.

Does this skill work with domain modeling?▼

Yes, the grilling session explicitly builds on the /domain-modeling skill. It uses domain modeling concepts to ground its questions in the problem domain and to build a shared glossary of terms.

When should I not use an adversarial plan review?▼

Avoid it for trivial or well-understood tasks where the overhead of a full interview and documentation outweighs the benefit. It is best suited to plans with meaningful ambiguity, risk, or cross-team impact.