grill-with-docs

Run structured interview sessions to validate project plans and generate Architecture Decision Records.

3|1|Updated Nov 5, 2015
One-click install
npx skills add https://github.com/Flowm/dotfiles --skill grill-with-docs-flowm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/Flowm/dotfiles/tree/main/home/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/Flowm/dotfiles --skill grill-with-docs-flowm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of vague, undervalidated project plans and system designs that lack formal documentation and shared terminology, which often lead to implementation rework, team misalignment, and missed requirements during development.

Core Features & Use Cases

  • Structured Design Validation: Runs a relentless, targeted interview (grilling session) to challenge assumptions, identify gaps, and refine plans or designs before implementation begins.
  • Automated Documentation Generation: Creates Architecture Decision Records (ADRs) to document key design choices and tradeoffs as they are validated during the session.
  • Shared Glossary Creation: Builds a consistent domain glossary during the grilling process to eliminate terminology ambiguity across cross-functional teams.
  • Use Case: A product team developing a new payment processing flow can use this Skill to stress-test their proposed architecture, document why they chose Stripe over PayPal, and align on terms like "idempotency key" across engineering, product, and operations stakeholders.

Quick Start

Use the grill-with-docs skill to run a grilling session on your proposed customer onboarding flow design and generate the associated ADR and shared glossary.

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 interview session for validating system design assumptions?

A structured design validation interview challenges proposed architecture plans and product roadmaps to identify gaps and unvalidated assumptions before implementation begins. This grilling process eliminates terminology misalignment and reduces downstream development rework.

How do I automatically generate Architecture Decision Records from a design review?

You can automatically generate Architecture Decision Records by running a structured grilling session on your system design. The validation process captures key design choices and tradeoffs as they are discussed, outputting formal ADRs to document the validated decisions.

Can I use this design validation process for cross-functional team alignment?

Yes, structured design validation is built for cross-functional teams refining product roadmaps and architectures. It creates a shared domain glossary during the interview session, ensuring engineering, product, and operations stakeholders align on terminology like idempotency keys.

What's the best way to refine a project plan and eliminate unvalidated assumptions?

The best way to refine project plans is through a relentless, targeted grilling session that stress-tests the proposed design. This structured interview challenges assumptions, identifies missing requirements, and outputs refined plans alongside automated ADRs and glossaries.

When do I need to create a shared domain glossary for software architecture planning?

You need a shared domain glossary when cross-functional teams experience terminology ambiguity during early planning phases. Creating the glossary during design validation ensures all stakeholders align on domain terminology before implementation begins.

Does this grilling session work for early stage product roadmap refinement?

Yes, the structured grilling session applies directly to cross-functional teams refining product roadmaps during early planning phases. It stress-tests proposed architectures and design proposals, generating ADRs and glossaries as byproducts to reduce implementation rework.