grill-with-docs

Interrogates a plan or design while generating ADRs and a glossary.

28|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/NauelG/astro-blocks --skill grill-with-docs-nauelg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/NauelG/astro-blocks/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/NauelG/astro-blocks --skill grill-with-docs-nauelg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designs and plans often contain hidden assumptions, vague terminology, and unchallenged decisions that surface late as costly rework. This Skill stress-tests a plan through relentless questioning and captures the outcomes as durable documentation. ## Core Features & Use Cases - Relentless Interview: Challenges a plan or design by invoking a grilling workflow that probes assumptions, gaps, and trade-offs. - Documentation as a Byproduct: Produces Architecture Decision Records (ADRs) and a domain glossary while the interview progresses, via a domain-modeling workflow. - Use Case: Before implementing a new feature, run this Skill on your design proposal to expose weak points and walk away with written ADRs and a shared vocabulary for the team. ## Quick Start Grill my current design proposal and produce ADRs and a glossary documenting the decisions we settle.

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 structured grilling interview on the design that challenges assumptions, edge cases, and trade-offs. This Skill coordinates that interview and records the resolved decisions as ADRs and glossary entries.

How to generate ADRs from a design discussion?▼

Invoke this Skill on your plan; it pairs the grilling interview with a domain-modeling pass that writes Architecture Decision Records and a glossary as the conversation resolves each decision.

What documents does this design review produce?▼

It produces Architecture Decision Records (ADRs) capturing decisions and rationale, plus a glossary defining domain terms, both generated during the interview rather than afterward.

Can I invoke this Skill automatically in a workflow?▼

No. The Skill sets disable-model-invocation to true and its policy disallows implicit invocation, so it only runs when explicitly requested by the user.

When should I not use a grilling-style design review?▼

Avoid it for trivial changes with no architectural impact or when requirements are already fully settled and documented, since the interview overhead adds little value in those cases.