skills.rest
sanjanb
sanjanbCOMMUNITY
Explore all skills by this author →
GitHub

grill-with-docs

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

1|Updated Jul 23, 2026
Search Tags:#planning#domain modeling#adr#glossary#interview#design review#architecture decision record
One-click install
npx skills add https://github.com/sanjanb/my-agent-harness --skill grill-with-docs-sanjanb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/sanjanb/my-agent-harness/tree/main/skills/mp-grill-with-docs
Command: npx skills add https://github.com/sanjanb/my-agent-harness --skill grill-with-docs-sanjanb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions, vague requirements, and undocumented decisions that surface too late. This Skill runs a relentless interview session that stress-tests a plan or design while capturing the outcomes as durable documentation. ## Core Features & Use Cases - Structured Interrogation: Runs a grilling session that challenges assumptions and gaps in a plan or design 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 so that every key decision is challenged, resolved, and recorded as an ADR with agreed terminology in the glossary. ## Quick Start Ask the agent to grill my current design proposal and produce 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 design before implementation?▼

Run a grilling session on the design document, where the agent asks persistent clarifying questions to expose hidden assumptions and gaps. Each resolved decision is captured as an Architecture Decision Record for future reference.

How to generate ADRs from a design discussion?▼

The grilling session documents decisions as Architecture Decision Records while the interview progresses. Each challenged and resolved design point becomes a recorded ADR rather than being lost in conversation.

What documentation does a design review produce?▼

This workflow produces two artifacts: Architecture Decision Records capturing each resolved design decision, and a glossary defining the agreed domain terminology established during the session.

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

No, the skill explicitly delegates to the domain-modeling skill during the grilling session. The domain-modeling skill must be available for the interview workflow to function as designed.

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

Avoid it for trivial changes with no architectural impact or when requirements are already fully specified and documented. The interview format adds the most value for ambiguous, high-stakes design decisions.

Related Skills

Explore More Software Engineering Skills→
PlagueHOPlagueHO
2

architectural-proposals

Draft architectural proposals documenting problem statements, architecture, decisions, and risks.

Community
Advanced
arndvsarndvs

grill-with-docs

Stress-tests design plans through structured interviews while updating CONTEXT.md glossaries and ADRs inline.

Community
Intermediate
yknothingyknothing
1

domain-modeling

Identify core domain concepts and produce a ubiquitous language glossary.

Community
Advanced
PlaidmustachePlaidmustache

spike

Decompose ideas into feasibility spikes and produce a VALIDATED, PARTIAL, or INVALIDATED verdict.

Community
Intermediate