grill-with-docs

Interviews a plan or design and generates ADRs and glossary documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions, vague decisions, and undocumented terminology that surface only during implementation. This Skill runs a structured interview that challenges a plan or design while producing Architecture Decision Records (ADRs) and a glossary as the conversation progresses. ## Core Features & Use Cases - Relentless Design Interview: Runs a grilling session that probes and sharpens a plan or design through targeted questioning. - Documentation as Output: Creates ADRs and glossary entries incrementally during the interview rather than as a separate step. - Domain Modeling Integration: Builds on the domain-modeling skill to ground the interview in a shared vocabulary. - Use Case: Before starting a new service, run a grilling session on your draft architecture so that key decisions are captured as ADRs and domain terms are defined in a glossary for the team. ## Quick Start Ask the agent to run a grilling session on your current plan or design document so it can challenge the decisions 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 design document before implementation?▼

Run a grilling session on the plan or design, which asks relentless clarifying questions to expose weak assumptions. As the interview proceeds, decisions are recorded as ADRs and terms are added to a glossary.

How to generate ADRs from an architecture discussion?▼

The grilling interview captures Architecture Decision Records as decisions are made during the conversation. This avoids writing ADRs retroactively and keeps rationale tied to the actual discussion.

What documentation does a design interview produce?▼

The session produces two artifacts: ADRs recording architectural decisions and a glossary defining domain terms. Both are created incrementally as the interview progresses rather than afterward.

Does this skill work without the domain-modeling skill?▼

The skill explicitly instructs the agent to run the grilling session using the domain-modeling skill, so domain modeling is part of its intended workflow. Without it, the shared vocabulary grounding would be missing.

When should I not use an interview-based design review?▼

Interview-based review is less useful for trivial changes with no architectural impact or when decisions are already fully documented. It adds the most value for ambiguous plans with unresolved trade-offs.