grill-with-docs

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

Updated Feb 22, 2024
One-click install
npx skills add https://github.com/tlipoca9/dotfiles --skill grill-with-docs-tlipoca9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/tlipoca9/dotfiles/tree/main/home/dot_agents/skills/grill-with-docs
Command: npx skills add https://github.com/tlipoca9/dotfiles --skill grill-with-docs-tlipoca9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designs and plans often contain hidden assumptions, vague terminology, and unexamined trade-offs that surface only during implementation. This Skill runs a relentless structured interview that pressure-tests a plan or design and captures the outcomes as durable documentation. ## Core Features & Use Cases - Relentless Interviewing: Invokes a grilling workflow that challenges assumptions, edge cases, and decisions in a plan or design. - Documentation as a Byproduct: Produces Architecture Decision Records (ADRs) and a domain glossary while the interview progresses, via a domain-modeling workflow. - Use Case: Before implementing a new service, present your draft design and let the interview expose weak points while automatically recording each decision as an ADR and defining domain terms in a glossary. ## Quick Start Ask the assistant to grill my current design document and record 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 software design before implementation?▼

Present your plan or design and run a structured grilling interview that challenges assumptions, edge cases, and trade-offs. Each challenged decision is captured as an Architecture Decision Record so the reasoning is preserved.

How to generate ADRs during a design review?▼

ADRs are generated as a byproduct of the interview process rather than written separately. As each design decision is questioned and resolved, the outcome is recorded as an Architecture Decision Record alongside a domain glossary.

What documentation does a design grilling session produce?▼

The session produces two artifacts: Architecture Decision Records capturing resolved design decisions, and a glossary defining domain terms. Both are created incrementally as the interview progresses.

Can this skill be invoked automatically by the AI?▼

No, the skill sets disable-model-invocation to true and its policy disallows implicit invocation. It must be explicitly requested by the user, and it delegates to separate grilling and domain-modeling skills.

When should I not use an interview-based design review?▼

Avoid it for trivial changes with no meaningful trade-offs, or when you need automated static analysis of code rather than reasoning about design intent. It targets plans and designs, not implemented code quality.