grill-with-docs

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

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/salomepoulain/makery-stations --skill grill-with-docs-salomepoulain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/salomepoulain/makery-stations/tree/main/stations/claude/workbench/pantry/skills/grill-with-docs
Command: npx skills add https://github.com/salomepoulain/makery-stations --skill grill-with-docs-salomepoulain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designs and plans often contain hidden assumptions, vague terminology, and unexamined trade-offs. This Skill stress-tests a plan through relentless questioning while simultaneously 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 Generation: Produces Architecture Decision Records (ADRs) and a domain glossary as the interview progresses, via a domain-modeling workflow. - Use Case: Before implementing a new service, run this Skill on your design proposal 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 grilling session that challenges each assumption, edge case, and trade-off in the design. This Skill coordinates that interview and records the outcomes as ADRs and a glossary.

How to generate ADRs from a design discussion?

The Skill captures decisions surfaced during the interrogation and writes them as Architecture Decision Records. It also builds a domain glossary so terminology stays consistent across the team.

What documents does a design review produce?

This workflow produces two artifacts: Architecture Decision Records documenting key choices and their rationale, and a glossary defining domain terms used throughout the design.

Can this Skill be invoked automatically by the model?

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

When should I not use a design grilling workflow?

Avoid it for trivial changes or well-understood tasks where interrogation adds no value. It is best suited to novel designs with meaningful architectural trade-offs worth documenting.