grill-with-docs

Refine architectural plans through interactive interviews and generate decision records.

Updated Jul 3, 2026

Search Tags:#architecture #interview #decision tracking #design documentation #interactive planning

Ready to run

npx skills add https://github.com/pxlcrtiv/opencode-setup --skill grill-with-docs-pxlcrtiv

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/pxlcrtiv/opencode-setup/tree/main/skills/grill-with-docs
Command: npx skills add https://github.com/pxlcrtiv/opencode-setup --skill grill-with-docs-pxlcrtiv

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The grill-with-docs Skill helps refine and document plans and designs through collaborative interviews, reducing ambiguity and fostering clarity.

Core Features & Use Cases

Interview-based Refinement: Facilitates detailed discussions to hone plans and designs.
Documentation Creation: Automatically generates Architectural Decision Records (ADR's) and glossaries.
Use Case: When preparing a high-level architectural design, use this Skill to conduct a focused grilling session with the team to extract and document design decisions and assumptions.

Quick Start

Start a grilling session on your architecture using the /grilling command followed by your 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 plans through interactive interviewing?▼

Software architecture plans are refined through interactive interviewing by conducting collaborative grilling sessions that extract design decisions and assumptions, automatically generating structured documentation for decision tracking. This reduces ambiguity and fosters clarity in iterative design workshops.

What is an Architectural Decision Record and when do I need one?▼

An Architectural Decision Record (ADR) is structured documentation that captures design decisions and assumptions made during software architecture planning. You need one when preparing a high-level architectural design to ensure decision tracking and reduce ambiguity across the team.

How do I document design decisions and assumptions during a planning workshop?▼

Design decisions and assumptions are documented during planning workshops by using AI-mediated decision logging that automatically generates ADRs and glossaries from interactive interview sessions, ensuring all architectural choices are tracked and shared.

Can I use interactive planning to improve existing design documentation?▼

Interactive planning can be used to improve existing design documentation through focused grilling sessions that extract and refine architectural decisions, leveraging AI-mediated decision logging to update ADRs and glossaries with clarified assumptions.

Does architecture interview-based refinement require active collaboration?▼

Architecture interview-based refinement requires active collaboration to conduct the interactive interviewing sessions needed for AI-mediated decision logging, ensuring that the resulting ADRs and glossaries accurately reflect the team's design decisions and assumptions.

What are the limitations of using interactive planning for architecture decision tracking?▼

Interactive planning for architecture decision tracking is limited by its reliance on active collaboration and AI-mediated decision logging, making it less suitable for fully automated pipelines or scenarios where team members cannot participate in iterative design workshops.