grill-with-docs

Conduct design interviews and generate ADRs, glossaries, and decision logs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of conducting a thorough plan/design interview, ensuring that critical decisions, domain terms, and potential risks are captured as durable documentation artifacts.

Core Features & Use Cases

  • Structured Interview: Facilitates a one-question-at-a-time interview style, similar to grill-me.
  • Documentation Artifacts: Generates ADRs, glossary entries, and decision logs.
  • Use Case: Ideal for when a project requires detailed decision documentation to facilitate understanding and implementation for future contributors.

Quick Start

Run the 'grill-with-docs' skill to initiate a comprehensive design review and documentation generation process.

Frequently Asked Questions about grill-with-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate ADRs and decision logs for a complex software project?

You generate ADRs and decision logs by running an in-depth design and decision-making interview that captures key outcomes in durable documentation artifacts. This structured interview process ensures critical decisions are thoroughly evaluated and recorded.

What is the best way to conduct a design review that captures domain terms and risks?

The best way to conduct a design review is using a one-question-at-a-time interview format that systematically captures domain terms and risks. This approach ensures comprehensive plan evaluation and generates glossary entries alongside decision documentation.

When do I need structured decision documentation for my software architecture?

You need structured decision documentation when a project demands thorough future-proofing of decisions and detailed records for future contributors. It is ideal for complex projects requiring comprehensive plan evaluation and durable artifacts like ADRs.

How do I document software design decisions to facilitate understanding for future contributors?

You document design decisions by executing a comprehensive design review that produces glossary entries and decision logs. This process captures critical decisions and domain terms as durable artifacts, facilitating implementation and understanding for future contributors.

Can I use a structured interview to create glossary entries and ADRs simultaneously?

Yes, you can use a structured interview to create glossary entries and ADRs simultaneously. The interview facilitates a comprehensive design review that automatically generates these documentation artifacts alongside decision logs during the evaluation process.