grill-with-docs

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

1|Updated Mar 2, 2025
One-click install
npx skills add https://github.com/marjorg/setup --skill grill-with-docs-marjorg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/marjorg/setup/tree/main/home/.agents/skills/archive/0-matt/grill-with-docs
Command: npx skills add https://github.com/marjorg/setup --skill grill-with-docs-marjorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions, vague terminology, and unchallenged decisions that surface only during implementation. This Skill runs a relentless interview against your plan or design and captures the outcomes as durable documentation. ## Core Features & Use Cases - Relentless Interview: Challenges every assumption and decision in a plan or design through structured questioning. - Documentation as Output: Produces Architecture Decision Records (ADRs) and a domain glossary as the interview progresses. - Orchestrated Workflow: Delegates to the "grilling" and "domain-modeling" skills to combine critique with structured documentation. - Use Case: Before starting a new microservice, run this Skill on your design draft to expose weak points and walk away with ADRs and a shared vocabulary for the team. ## Quick Start Ask the assistant to grill your 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 interview against the design that challenges every assumption and decision. This Skill coordinates a grilling process that surfaces weak points and records the outcomes as ADRs and a glossary.

How to generate ADRs from a design discussion?

Invoke this Skill on your plan or design and it documents each challenged decision as an Architecture Decision Record while the interview proceeds. It also builds a domain glossary of the terms used.

What documents does this Skill produce?

It produces Architecture Decision Records (ADRs) capturing design decisions and a glossary defining domain terms. Both are created incrementally during the interview rather than as a separate step.

Does this Skill work on its own or need other skills?

It depends on two other skills named "grilling" and "domain-modeling", which it invokes to perform the interview and produce the documentation. Those skills must be available for it to function.

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

Avoid it for trivial changes with no architectural impact or when decisions are already finalized and documented. It adds the most value early, when assumptions can still be challenged cheaply.