grill-with-docs

Guide design-review sessions to update CONTEXT.md and ADRs inline.

5|Updated Oct 18, 2025
One-click install
npx skills add https://github.com/rexshihaoren/rexyDigest --skill grill-with-docs-rexshihaoren
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/rexshihaoren/rexyDigest/tree/main/docs/ai/skills/grill-with-docs
Command: npx skills add https://github.com/rexshihaoren/rexyDigest --skill grill-with-docs-rexshihaoren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grilling with Docs provides a guided, interactive session that challenges a project's plan against its existing domain model and documentation, helping capture precise terminology and decisions in real time by updating CONTEXT.md and ADRs inline.

Core Features & Use Cases

  • Strongly prompts domain-clarifying questions to surface terminology conflicts.
  • Updates CONTEXT.md and ADRs inline as decisions crystallize, ensuring documentation stays aligned with decisions.
  • Use Case: For new architecture discussions, run a grilling session to enforce consistent domain language and traceable decisions.

Quick Start

Initiate a guided grilling session to stress-test your plan against your project's domain language and existing documentation.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
How do I stress-test my architecture plan against an existing domain model?

To stress-test an architecture plan against a domain model, use a guided interactive session that iteratively challenges your design to surface terminology conflicts and enforce consistent domain language before finalizing decisions.

What is the best way to update CONTEXT.md and ADRs during a design review?

The best way to update CONTEXT.md and ADRs during a design review is through inline documentation updates captured in real time as decisions crystallize, ensuring documentation stays aligned with architectural choices and preserves traceability.

How do I resolve terminology conflicts when discussing a new domain model?

To resolve terminology conflicts in a domain model, apply domain-clarifying questions during a design review session to surface inconsistencies and update your documentation inline as precise terminology is agreed upon.

Do I need existing ADRs to run a domain model grilling session?

You do not need existing ADRs to run a domain model grilling session, as the interactive process updates CONTEXT.md and decision records inline, capturing architecture decisions as they are newly formed and crystallized.

Why does my documentation lose traceability after architecture discussions?

Documentation loses traceability after architecture discussions when decisions are not captured inline. Running an interactive grilling session preserves traceability by updating ADRs and CONTEXT.md in real time as issues are surfaced.