grill-with-docs

Interrogate plans and designs to produce decision records and a glossary.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a vague plan or design into a rigorous conversation that exposes hidden assumptions, clarifies boundaries, and produces durable documentation.

Core Features & Use Cases

  • Deep interrogation: Pushes a proposal through systematic questioning so weak spots surface early.
  • Decision capture: Produces architecture decision records and a glossary while the discussion unfolds.
  • Design and planning support: Useful for product ideas, technical designs, and domain modeling sessions where precision matters.

Quick Start

Ask the skill to run a grilling session for your plan or design and generate the associated decision records and 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 capture architecture decisions and a glossary during a design review?

To capture architecture decision records and a glossary during a design review, use a structured grilling session that systematically questions a proposal and documents the clarified trade-offs and terminology as the discussion unfolds.

What is a grilling session for domain modeling and product planning?

A grilling session for domain modeling is a rigorous interview process that exposes hidden assumptions in a vague plan, clarifies boundaries, and turns the discussion into durable decision records and a structured glossary.

How do I expose hidden assumptions in a technical design before implementation?

You expose hidden assumptions in a technical design by pushing the proposal through iterative, systematic questioning that targets terminology and trade-offs, ensuring weak spots surface early before development begins.

Can I use this approach for both product ideas and architecture design reviews?

Yes, you can use this interrogation approach for product ideas, technical designs, and architecture sessions where precision matters, because it systematically clarifies boundaries and produces documentation aligned with your workflow.

What is the best way to document trade-offs and boundaries in a domain modeling session?

The best way to document trade-offs and boundaries in a domain modeling session is applying iterative questioning that systematically forces clarification of terminology, directly outputting structured decision records and a glossary.

When do I need to generate architecture decision records from a planning discussion?

You need to generate architecture decision records from a planning discussion when a vague design requires rigorous conversation to clarify terminology, expose hidden assumptions, and produce durable documentation for future reference.