grill-with-docs

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

Updated May 31, 2026
One-click install
npx skills add https://github.com/AlexanderNarbaev/agi --skill grill-with-docs-alexandernarbaev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/AlexanderNarbaev/agi/tree/main/.opencode/skills/matt-pocock/grill-with-docs
Command: npx skills add https://github.com/AlexanderNarbaev/agi --skill grill-with-docs-alexandernarbaev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions, vague terminology, and undocumented decisions. This Skill stress-tests a plan through a relentless structured interview while simultaneously capturing the outcomes as durable documentation. ## Core Features & Use Cases - Design Interrogation: Invokes a grilling workflow that challenges every assumption in a plan or design through pointed questions. - Domain Modeling: Invokes a domain-modeling workflow to clarify entities, terms, and boundaries as the interview progresses. - Living Documentation: Produces Architecture Decision Records (ADRs) and a glossary as byproducts of the interview, so decisions are recorded as they are made. - Use Case: Before implementing a new service, run this Skill on your draft design to expose weak points and walk away with written ADRs and a shared vocabulary for the team. ## Quick Start Ask the assistant to grill my current design document 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 software design before implementation?

Run a structured grilling interview on the design that challenges each assumption, decision, and undefined term. This Skill coordinates that interview and records the outcomes as ADRs and a glossary while you answer.

How to generate ADRs from a design discussion?

The Skill captures decisions as they surface during the interview and writes them as Architecture Decision Records. You answer questions about your plan, and the documentation is produced as a byproduct of the conversation.

What is domain modeling in a design review?

Domain modeling clarifies the entities, terms, and boundaries of the problem space. This Skill invokes a dedicated domain-modeling workflow alongside the grilling interview to build a shared glossary of precise definitions.

Can this Skill be invoked automatically by the agent?

No. Its agent policy sets allow_implicit_invocation to false, so it only runs when explicitly requested by the user rather than being triggered automatically.

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 adds the most value when assumptions are unexamined and terminology is unsettled.