grill-with-docs

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions, gaps, and ambiguities that surface too late. This Skill runs a relentless interview session that stress-tests your plan while capturing the outcomes as durable documentation. ## Core Features & Use Cases - Structured Grilling Session: Runs a /grilling interview that challenges your plan or design with probing questions. - Documentation as a Byproduct: Creates Architecture Decision Records (ADRs) and a glossary as the session progresses. - Domain Modeling Integration: Leverages the /domain-modeling skill to ground the discussion in domain concepts. - Use Case: Before committing to a new system architecture, run a grilling session to expose weak assumptions and walk away with ADRs and a shared glossary for the team. ## Quick Start Ask the assistant to run a grilling session on your current design plan and produce ADRs and a glossary as you answer its questions.

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 plan with an AI interview?

Run a grilling session that asks relentless probing questions about your plan or design. The session challenges assumptions and gaps, and documents the resolved decisions as ADRs and a glossary along the way.

What documentation does a grilling session produce?

The session produces Architecture Decision Records (ADRs) capturing key decisions and a glossary defining domain terms. These artifacts are created incrementally as the interview progresses.

Can I use this for architecture decision records?

Yes, generating ADRs is a core output of the skill. As the interview surfaces design decisions, they are recorded as ADRs so the rationale behind each choice is preserved for the team.

When should I not use a grilling session for planning?

Avoid it for trivial or well-understood tasks where deep interrogation adds no value. It is best suited for complex plans or designs with significant ambiguity, trade-offs, or unvalidated assumptions.