grill-with-docs

Interrogates a plan or design through structured questioning while generating ADRs and a glossary.

1|Updated Oct 29, 2025

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

Ready to run

npx skills add https://github.com/jwh3times/holland-vip --skill grill-with-docs-jwh3times

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/jwh3times/holland-vip/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/jwh3times/holland-vip --skill grill-with-docs-jwh3times

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designs and plans often contain hidden assumptions, vague terms, and unexamined trade-offs that surface too late. This Skill runs a relentless interview session that stress-tests a plan or design and captures the outcomes as durable documentation. ## Core Features & Use Cases - Structured Interrogation: Runs a grilling session that challenges assumptions, scope, and design decisions through persistent questioning. - Documentation as a Byproduct: Produces Architecture Decision Records (ADRs) and a project glossary as the interview progresses. - Domain Modeling Integration: Delegates to the domain-modeling skill to ground the discussion in a shared vocabulary. - Use Case: Before implementing a new feature, run a grilling session on the design proposal to expose weak points and automatically record each decision and its rationale as ADRs. ## Quick Start Ask the assistant to grill my current design proposal 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 that subjects the design to persistent structured questioning about assumptions, scope, and trade-offs. Each challenged decision is captured as an Architecture Decision Record so the reasoning is preserved.

What is an Architecture Decision Record and how is it created?▼

An Architecture Decision Record (ADR) documents a significant design decision along with its context and rationale. This Skill creates ADRs automatically as decisions are made and defended during the interview session.

Can I use this for plans that are not software designs?▼

Yes, the grilling approach works for any plan or design that benefits from rigorous questioning. The outputs are ADRs and a glossary, which are most natural in software and technical planning contexts.

Does the grilling session require the domain-modeling skill?▼

Yes, the session explicitly delegates to the domain-modeling skill to establish shared vocabulary and domain concepts. Without it, the glossary and domain grounding portions of the workflow would not function as intended.

When should I not use a design grilling session?▼

Avoid it for trivial changes with no meaningful trade-offs, where the interview overhead exceeds the value. It is best suited to designs with real architectural decisions worth documenting as ADRs.