grill-with-docs

Interview users to refine designs and generate ADRs and glossaries.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/ZzAve/teambalance-app --skill grill-with-docs-zzave
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/ZzAve/teambalance-app/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/ZzAve/teambalance-app --skill grill-with-docs-zzave

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill conducts a thorough interview process to refine and document plans, producing Architectural Decision Records (ADR's) and glossaries simultaneously.

Core Features & Use Cases

  • Interview-Based Refinement: Engage in an in-depth interview to enhance plans and designs.
  • Documentation Generation: Outputs ADRs and glossaries during the interview process.
  • Use Case: When you have a draft design and need to ensure it's comprehensive and well-documented, use this Skill to conduct a structured review that results in detailed ADRs and a comprehensive glossary.

Quick Start

Start the grill-with-docs session to refine your design and generate ADRs.

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 architectural designs and generate ADRs simultaneously?

To refine architectural designs and generate ADRs, you need to conduct an in-depth interview process. This approach engages you in structured data collection to comprehensively review draft designs while automatically outputting Architectural Decision Records and glossaries.

What is the best way to create a glossary during the design refinement process?

The best way to create a glossary during design refinement is through an interview-based review. By answering targeted questions about your system architecture, the documentation process captures domain terms to build a comprehensive glossary alongside your design decisions.

Do I need a draft design to start an interview for Architectural Decision Records?

Yes, you need a draft design to start an interview for Architectural Decision Records. The process is applicable when you have an existing design that requires structured documentation and comprehensive refinement through human interaction and decision-making.

When do I need to use an interview-based approach for systems architecture documentation?

You need an interview-based approach for systems architecture documentation when you have a draft design requiring structured review. It is applicable for software development processes needing comprehensive ADRs and glossaries generated through interactive data collection.

Can I automate documentation generation without human interaction for my software development plan?

No, you cannot automate documentation generation without human interaction using this approach. The interview process explicitly requires human interaction for data collection and decision-making to ensure the architectural designs are thoroughly refined and accurately documented.