skills.rest
dohcivil-ui
dohcivil-uiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

grill-with-docs

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

Updated Aug 21, 2026
Search Tags:#planning#domain modeling#adr#glossary#interview#design review#architecture decision record
One-click install
npx skills add https://github.com/dohcivil-ui/naichangmoo.com --skill grill-with-docs-dohcivil-ui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/dohcivil-ui/naichangmoo.com/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/dohcivil-ui/naichangmoo.com --skill grill-with-docs-dohcivil-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designs and plans often contain hidden assumptions, vague terms, and unexamined trade-offs that surface too late. This Skill runs a relentless structured interview to stress-test a plan while capturing the outcomes as durable documentation. ## Core Features & Use Cases - Design Interrogation: Invokes a grilling workflow that challenges assumptions, edge cases, and decisions in a plan or design. - Documentation as Output: Produces Architecture Decision Records (ADRs) and a domain glossary as the interview progresses. - Use Case: Before committing to a new service architecture, run this Skill to have your design questioned point by point, ending with ADRs recording each decision and a glossary aligning team terminology. ## Quick Start Grill my proposed architecture for the new billing service 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 that challenges each assumption, edge case, and trade-off in the design. This Skill coordinates that interview and records the resulting 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, they are captured as Architecture Decision Records. A domain glossary is built alongside to standardize terminology.

What documents does a design review interview produce?▼

This workflow produces two artifacts: Architecture Decision Records documenting each decision and its rationale, and a domain glossary defining the key terms used across the design.

Can I invoke this Skill automatically in a conversation?▼

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

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

The output quality depends on the detail of the plan provided and the answers given during the interview. It documents decisions but does not validate them against code, benchmarks, or production behavior.

Related Skills

Explore More Software Engineering Skills→
gjallagjalla
1

write-design-doc

Draft structured software design documents with required sections before implementation.

Official
Advanced
rrbandarrbanda

wiki-architect

Convert codebases into hierarchical wiki catalogs with onboarding guides.

Community
Advanced
U1traVenoU1traVeno

grill-with-docs

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

Community
Basic
thedotmackthedotmack
92.8k

what-the

Explain technical concepts using who, what, where, why, and when framing.

Community
Basic