grill-with-docs

Interviews a plan or design and generates ADRs and glossary documentation.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/malikkotb/shellpluscore --skill grill-with-docs-malikkotb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/malikkotb/shellpluscore/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/malikkotb/shellpluscore --skill grill-with-docs-malikkotb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions, vague terms, and undocumented decisions. This Skill stress-tests a plan through a structured interview while capturing the outcomes as durable documentation. ## Core Features & Use Cases - Relentless Interviewing: Challenges a plan or design with probing questions to expose gaps, ambiguities, and unexamined trade-offs. - Documentation as a Byproduct: Creates Architecture Decision Records (ADRs) and a domain glossary as the interview progresses. - Use Case: Before implementing a new feature, run the interview on your design draft to surface weak points and walk away with ADRs and a shared glossary 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 interview against your design draft that challenges assumptions, scope, and trade-offs. This Skill coordinates a grilling pass and domain modeling so weaknesses surface before code is written.

How to generate ADRs from a design discussion?

The interview captures each significant decision as it is challenged and resolved, then writes it up as an Architecture Decision Record. A glossary of domain terms is produced alongside the ADRs.

What is a domain glossary in software design?

A domain glossary defines the key terms and concepts used in a project so the team shares one vocabulary. This Skill builds the glossary incrementally as the interview clarifies terminology.

Can this Skill be invoked automatically by the AI?

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

When should I not use a design grilling interview?

Avoid it for trivial changes with no architectural impact, where a full interview and ADR overhead outweigh the benefit. It is best suited to designs with meaningful trade-offs or new domain concepts.