Verified:GitHub

grill-with-docs

Interrogates plans or designs through structured questioning while generating ADRs and glossaries.

2|Updated Jul 6, 2026

Search Tags:#planning #domain modeling #adr #glossary #design review #interrogation

One-click install

npx skills add https://github.com/NAMEWTA/learning-open-code --skill grill-with-docs-namewta

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/NAMEWTA/learning-open-code/tree/main/translator/open-ai-skills/matt-pocock-skills/skills/engineering/grill-with-docs
Command: npx skills add https://github.com/NAMEWTA/learning-open-code --skill grill-with-docs-namewta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions, ambiguities, and undocumented decisions. This Skill stress-tests a plan or design through a relentless interview process while simultaneously capturing the outcomes as durable documentation. ## Core Features & Use Cases - Rigorous Interrogation: Runs a grilling session that challenges every aspect of a plan or design to expose gaps and weak assumptions. - Documentation as a Byproduct: Produces Architecture Decision Records (ADRs) and a domain glossary during the interview, so reasoning is preserved. - Domain Modeling Integration: Leverages the /domain-modeling skill to structure the vocabulary and concepts uncovered during the session. - Use Case: Before implementing a new feature, run a grilling session on the design proposal to surface edge cases and record each decision as an ADR for the team. ## Quick Start Ask the agent to run a grilling session on your current plan or design document to challenge its assumptions and produce 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 the design document, which systematically challenges assumptions and decisions through structured questioning. The process exposes gaps and records each resolved decision as an Architecture Decision Record.

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 generates ADRs automatically as decisions are clarified during the interrogation session.

How to build a domain glossary for a software project?▼

Use the integrated domain-modeling capability during the grilling session to identify and define key domain terms. The resulting glossary captures shared vocabulary that keeps the team aligned on concepts.

When should I use a design interrogation workflow?▼

Use it before committing to implementation, when a plan or design contains untested assumptions or ambiguous requirements. It is less useful for trivial changes or already well-documented decisions.