grill-with-docs

Align domain terminology and decisions by updating CONTEXT.md and ADRs inline.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams align their plans with the domain model by conducting a relentless grilling session, surfacing ambiguities, and updating CONTEXT.md and ADRs in real time as decisions crystallize.

Core Features & Use Cases

  • Guides stakeholders through a structured interview process that uncovers dependencies, assumptions, and trade-offs.
  • Updates domain documentation inline (CONTEXT.md, ADRs) as decisions are made, ensuring living, synchronized guidance.
  • Works with codebase exploration when needed to ground discussions in actual implementation.

Quick Start

Start the grilling session by answering the AI’s questions one at a time until the domain language and decisions are aligned and documented.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
How do I align domain terminology and decisions with stakeholder input?

You can align domain terminology by conducting a structured grilling session that surfaces ambiguities, captures decision rationale, and updates CONTEXT.md and ADRs inline as stakeholders answer questions.

What is the best way to keep CONTEXT.md and ADRs synchronized during project planning?

Keeping CONTEXT.md and ADRs synchronized requires updating documentation in real time as decisions crystallize during a disciplined grilling session, ensuring living guidance reflects the latest domain model alignment.

How does a grilling session uncover dependencies and trade-offs in a domain model?

A grilling session uncovers dependencies by guiding stakeholders through a relentless interview process, asking targeted questions one at a time to expose assumptions and surface trade-offs within the evolving domain model.

Can I use an existing domain model and ADRs as input for stakeholder alignment?

Yes, you can use existing domain models and ADRs as input, applying the grilling process to projects with evolving CONTEXT.md documentation to validate terminology and update decisions inline.

Do I need to explore the codebase to align domain documentation with actual implementation?

You can explore the codebase when needed to ground stakeholder discussions in actual implementation, ensuring the domain terminology and decisions captured in CONTEXT.md and ADRs reflect real technical constraints.

When should I not use a structured grilling session for documentation updates?

A structured grilling session may be unnecessary for simple projects without evolving CONTEXT.md or ADRs, or when stakeholder alignment and domain terminology are already fully documented and unambiguous.