grill-with-docs

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

Updated Jan 19, 2023
One-click install
npx skills add https://github.com/inkfin/dotfiles --skill grill-with-docs-inkfin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/inkfin/dotfiles/tree/main/dot_agents/skills/exact_grill-with-docs
Command: npx skills add https://github.com/inkfin/dotfiles --skill grill-with-docs-inkfin

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 runs a relentless interview session that pressure-tests a plan or design while capturing the outcomes as durable documentation. ## Core Features & Use Cases - Structured Interrogation: Runs a grilling session that challenges assumptions and forces decisions to be made explicit. - Documentation as a Byproduct: Produces Architecture Decision Records (ADRs) and a glossary as the interview progresses. - Domain Modeling Integration: Delegates to the domain-modeling skill to ground terminology and concepts during the session. - Use Case: Before implementing a new service, run a grilling session on the design proposal so every contested decision is recorded as an ADR and every domain term lands in the glossary. ## Quick Start Ask the assistant to grill my current design proposal and document the decisions as ADRs and a glossary.

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 design before implementation?

Run a grilling session on the design, which asks relentless clarifying questions to expose hidden assumptions and unresolved trade-offs. Each decision reached during the session is recorded as an Architecture Decision Record.

What documentation does a design grilling session produce?

The session produces Architecture Decision Records (ADRs) capturing each decision and its rationale, plus a glossary defining the domain terms that come up during the interview.

Does this skill work with domain modeling?

Yes, the grilling session explicitly delegates to the domain-modeling skill, so terminology and domain concepts are modeled and captured in the glossary as the interview proceeds.

Can this skill be invoked automatically by the AI?

No, it sets disable-model-invocation and disallows implicit invocation, so it only runs when the user explicitly requests a grilling session.

When should I not use a grilling session for a design?

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