grill-with-docs

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designs and plans often contain hidden assumptions, vague terminology, and unexamined trade-offs that surface only during implementation. This Skill stress-tests a plan through relentless questioning and captures the outcomes as durable documentation. ## Core Features & Use Cases - Relentless Design Interview: Challenges a plan or design with probing questions to expose gaps, ambiguities, and weak decisions. - Documentation as a Byproduct: Produces Architecture Decision Records (ADRs) and a domain glossary while the interview progresses. - Composed Workflow: Delegates to the "grilling" and "domain-modeling" skills, combining adversarial review with structured domain capture. - Use Case: Before implementing a new service, run this Skill on your design draft to pressure-test the architecture and walk away with ADRs and a shared vocabulary for the team. ## Quick Start Ask the AI 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 assumptions, scope, and trade-offs with probing questions. This Skill automates that interview and records the resolved decisions as ADRs and a glossary.

How to generate ADRs from a design discussion?▼

Invoke this Skill on your plan or design; as the interview surfaces decisions and their rationale, it writes them up as Architecture Decision Records along with a domain glossary.

What documents does a design review interview produce?▼

This workflow produces two artifacts: Architecture Decision Records capturing key decisions and their reasoning, and a glossary defining the domain terms used across the design.

Can I invoke grill-with-docs automatically in a workflow?▼

No. The Skill sets disable-model-invocation to true and its agent policy disallows implicit invocation, so it must be triggered explicitly by the user.

What are the limitations of an interview-based design review?▼

The output quality depends on the design material provided and the answers given during the interview. It does not validate code, run benchmarks, or replace formal architecture review with domain experts.