grill-with-docs

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

10|3|Updated Jul 18, 2019
One-click install
npx skills add https://github.com/tanqimin/MyFavsORM --skill grill-with-docs-tanqimin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/tanqimin/MyFavsORM/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/tanqimin/MyFavsORM --skill grill-with-docs-tanqimin

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 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 assumptions. - Documentation as a Byproduct: Produces Architecture Decision Records (ADRs) and a domain glossary while the interview progresses. - Use Case: Before implementing a new service, run this Skill on your design proposal to pressure-test key decisions and walk away with written ADRs and a shared vocabulary for the team. ## Quick Start Ask the assistant to grill my design document 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 interrogation of the design that challenges assumptions, edge cases, and trade-offs. This Skill drives that interview and records the resulting decisions as ADRs plus a glossary of domain terms.

What is an Architecture Decision Record and when should I write one?

An ADR is a short document capturing a significant architectural decision, its context, and its consequences. Write one whenever a non-trivial design choice is made, such as during a design review or planning interview.

Can this Skill generate documentation automatically during a design review?

Yes. It creates ADRs and a domain glossary as the interview progresses, so documentation emerges from the discussion rather than being written separately afterward.

Does grill-with-docs work on its own or require other skills?

It orchestrates two other skills, grilling and domain-modeling, by invoking them through the Skill tool. Those skills must be available in the environment 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 on ambiguous, high-stakes designs with unresolved trade-offs.