grill-with-docs

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designs and plans often contain hidden assumptions, vague terminology, and unexamined trade-offs that surface too late. This Skill runs a relentless structured interview against your plan or design and captures the outcomes as durable documentation. ## Core Features & Use Cases - Relentless Design Interview: Challenges a plan or design through the grilling workflow to expose gaps, ambiguities, and weak decisions. - Documentation as a Byproduct: Produces Architecture Decision Records (ADRs) and a domain glossary while the interview progresses, via the domain-modeling workflow. - Use Case: Before implementing a new service, run this Skill on your design proposal to stress-test the reasoning and walk away with ADRs and a shared vocabulary for the team. ## Quick Start Ask the assistant to grill my current design proposal and document the decisions and domain terms as we go.

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 against the design that challenges assumptions, scope, and trade-offs. This Skill coordinates that interview and records the resulting decisions as ADRs and glossary entries.

How to create ADRs during a design review?

Invoke this Skill on your plan or design; it delegates to the domain-modeling workflow to write Architecture Decision Records as the interview surfaces each significant decision.

What does the grill-with-docs skill produce as output?

It produces Architecture Decision Records and a domain glossary, generated incrementally while the design is being interrogated. The interview itself sharpens the plan.

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 or well-understood tasks where no meaningful trade-offs exist. The interview adds value when a plan contains untested assumptions or undefined domain terminology.