grill-with-docs

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

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill grill-with-docs-fatih0234
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/Fatih0234/mattpocock-skills-pi/tree/main/skills/engineering/grill-with-docs
Command: npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill grill-with-docs-fatih0234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designs and plans often contain hidden assumptions, vague terms, and unexamined trade-offs that surface only during implementation. This Skill runs a relentless structured interview that pressure-tests a plan or design while capturing the outcomes as durable documentation. ## Core Features & Use Cases - Relentless Design Interview: Loads the grilling skill to challenge assumptions, edge cases, and decisions in a plan or design through pointed questioning. - Documentation as a Byproduct: Loads the domain-modeling skill to produce Architecture Decision Records (ADRs) and a domain glossary as the interview progresses. - Use Case: Before implementing a new billing subsystem, run this Skill on your design draft. It will grill you on failure modes and naming, then leave you with ADRs explaining each decision and a glossary aligning the team's vocabulary. ## Quick Start Ask the agent to grill the attached 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 interview on the design document. The skill challenges assumptions, edge cases, and trade-offs through pointed questions, surfacing weaknesses before any code is written.

How to generate ADRs from a design discussion?

This skill creates Architecture Decision Records automatically as the interview progresses. Each challenged decision and its resolution is captured as an ADR, so documentation emerges from the conversation rather than being written afterward.

What is a domain glossary in software design?

A domain glossary defines the shared vocabulary of a project, aligning team members on the meaning of entities and terms. This skill builds one during the interview via the domain-modeling skill it loads.

Can I invoke grill-with-docs automatically in a workflow?

No. The skill sets disable-model-invocation to true and its policy disallows implicit invocation, so it only runs when you explicitly request it.

When should I not use a design grilling interview?

Avoid it for trivial changes or well-understood tasks where the overhead of an interview and ADR writing outweighs the benefit. It is best suited to designs with meaningful architectural decisions and ambiguity.