grill-with-docs

Guide structured grilling sessions to generate ADRs and glossary entries.

16|2|Updated Mar 29, 2018
One-click install
npx skills add https://github.com/khoi/dotfiles --skill grill-with-docs-khoi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/khoi/dotfiles/tree/main/chezmoi/dot_agents/skills/grill-with-docs
Command: npx skills add https://github.com/khoi/dotfiles --skill grill-with-docs-khoi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams through a rapid grilling session to refine plans or designs, while producing ADRs and glossary entries as you go.

Core Features & Use Cases

  • Structured grilling workflow that surfaces assumptions, decisions, and design gaps.
  • On-the-fly generation of ADRs and domain glossary entries to keep documentation aligned with discussion.
  • Reusable prompts and domain-modeling techniques applicable to product strategy, UX design, and architecture planning.

Quick Start

Start a /grilling session with the /domain-modeling skill to drive a design discussion and generate ADRs and glossary entries as you go.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
What is a structured grilling session for architecture and design planning?

A structured grilling session is an interactive, prompt-driven workflow that surfaces assumptions, decisions, and design gaps to refine plans while auto-generating ADRs and glossary entries.

How do I generate ADR and domain glossary entries during a design discussion?

You generate ADR and domain glossary entries by running an interactive grilling workflow that coordinates domain-modeling steps and produces lightweight documentation on the fly as decisions are made.

Can I use this grilling workflow for early design and architecture reviews?

Yes, the grilling workflow is applicable during early design, architecture reviews, and planning discussions where rapid clarification and live documentation of requirements and domain modeling are needed.

Does this domain-modeling workflow require any external dependencies or model invocations?

No, this domain-modeling workflow operates without external dependencies and avoids model invocation, functioning purely as an interactive prompt-driven process to produce design documentation.

What is the best way to refine product strategy and UX design plans collaboratively?

The best way to refine product strategy and UX design plans is using reusable grilling prompts and domain-modeling techniques that drive interactive discussions to clarify requirements and document decisions.

When should I not use an automated grilling session for documentation?

You should avoid an automated grilling session when your team needs static, pre-written documentation rather than interactive, prompt-driven refinement of early plans or live architecture reviews.