grill-with-docs

Interrogates a plan or design and produces ADRs and a glossary.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/j172/bid --skill grill-with-docs-j172
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/j172/bid/tree/main/agent/skills/grill-with-docs
Command: npx skills add https://github.com/j172/bid --skill grill-with-docs-j172

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 runs a relentless structured interview (a "grilling") that stress-tests a plan while capturing the outcomes as durable documentation. ## Core Features & Use Cases - Adversarial Q&A: Challenges the design with probing questions to expose gaps, ambiguities, and weak assumptions. - Documentation as a byproduct: Writes Architecture Decision Records (ADRs) and a domain glossary as the session progresses. - Domain modeling integration: Builds on the /domain-modeling skill to ground the discussion in a shared model. - Use Case: Before implementing a new service, run a grilling session on the design proposal; walk away with a hardened plan plus ADRs and a glossary for the team. ## Quick Start Ask the assistant to run a grilling session on your current design document and generate ADRs and a glossary from the discussion.

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 that subjects the design to relentless probing questions about assumptions, edge cases, and trade-offs. Weak points surface through the interview, and the conclusions are captured as Architecture Decision Records for the team.

How to generate ADRs from a design discussion?

The grilling workflow writes Architecture Decision Records as the interview progresses, so each challenged decision is documented with its rationale. A domain glossary is produced alongside the ADRs to standardize terminology.

What is a grilling session in design review?

A grilling session is a structured, adversarial interview where an interviewer relentlessly questions a plan or design to expose hidden assumptions and gaps. This Skill combines that interview with automatic documentation of decisions and terms.

Does this skill work without the domain-modeling skill?

No, the instructions explicitly delegate to the /domain-modeling skill as the foundation of the session. The grilling builds on that shared domain model to keep questions and documentation grounded.

When should I not use an adversarial design interview?

Avoid it for trivial changes or fully settled designs where questioning adds no value. It is most useful early in planning, when assumptions are still cheap to challenge and decisions can still change.