grill-with-docs

Refine plans and designs through structured interviews, generating ADRs and glossary entries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive interview process to refine plans and designs, simultaneously generating documentation like ADRs and glossary entries.

Core Features & Use Cases

  • Interview-Based Refinement: Engage in a structured interview to enhance and clarify plans or designs.
  • Documentation Generation: Automatically create and update documentation such as Architecture Decision Records (ADR) and glossary terms.
  • Use Case: Utilize this Skill to iterate on a software architecture design, ensuring all stakeholders are aligned and that critical decisions are well-documented.

Quick Start

Start a /grilling session to refine your project's architecture with the /domain-modeling skill.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
How do I refine software architecture designs through a structured interview?▼

You refine software architecture designs through a structured interview process that enhances plans and clarifies design intent. This approach systematically validates architectural decisions and ensures stakeholders are aligned.

How do I generate Architecture Decision Records and glossary entries during design refinement?▼

To generate Architecture Decision Records and glossary entries during design refinement, you participate in an iterative interview session. This process automatically captures and updates critical decisions and domain terms as supporting documentation.

What is the best way to document iterative architecture reviews for software development?▼

The best way to document iterative architecture reviews is using structured interviews to drive refinement. This simultaneously produces Architecture Decision Records and glossary entries to maintain alignment across stakeholders throughout the software development process.

When do I need Architecture Decision Records for my software development process?▼

You need Architecture Decision Records when refining software architecture iteratively to ensure critical decisions are well-documented. They provide supporting documentation that keeps stakeholders aligned during design reviews.

Can I use structured interviews to align stakeholders on a software architecture plan?▼

Yes, you can use structured interviews to align stakeholders on a software architecture plan. This interview-based refinement process enhances designs while simultaneously generating Architecture Decision Records and glossary entries.