grill-with-docs

Stress-tests plans against project glossaries and records decisions in CONTEXT.md and ADRs.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/ttphats/project-detedxs26 --skill grill-with-docs-ttphats
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/ttphats/project-detedxs26/tree/main/.augment/skills/custom/mattpocock/grill-with-docs
Command: npx skills add https://github.com/ttphats/project-detedxs26 --skill grill-with-docs-ttphats

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often use vague or conflicting terminology and make undocumented architectural decisions that future readers cannot understand. This Skill runs a structured interrogation of your plan against your project's existing domain language and documented decisions, updating CONTEXT.md and ADRs as conclusions are reached. ## Core Features & Use Cases - Socratic Plan Review: Asks one question at a time, walking each branch of the design tree and providing a recommended answer for every question. - Terminology Enforcement: Challenges terms that conflict with the existing CONTEXT.md glossary and sharpens fuzzy language into canonical terms. - Inline Documentation Updates: Updates CONTEXT.md the moment a term is resolved and offers ADRs only when a decision is hard to reverse, surprising, and the result of a real trade-off. - Use Case: Before implementing a new order cancellation feature, run a grilling session to reconcile your plan with the existing glossary, verify the code's actual behavior, and record the cancellation policy decision as an ADR. ## Quick Start Start a grilling session on my plan for the new feature and challenge it against our CONTEXT.md and existing ADRs.

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 a design plan before implementation?▼

Run a grilling session that interviews you one question at a time about every branch of the plan, providing a recommended answer for each question. Questions answerable from the codebase are resolved by exploring the code directly instead of asking.

What is a CONTEXT.md file in domain-driven design documentation?▼

CONTEXT.md is a project glossary defining canonical domain terms in one or two sentences each, with avoided synonyms listed under each term. It contains no implementation details and is updated inline whenever a term is resolved during discussion.

When should I write an architecture decision record?▼

Write an ADR only when all three conditions hold: the decision is hard to reverse, it is surprising without context, and it resulted from a real trade-off between alternatives. Decisions that are easy to reverse or obvious should be skipped.

Does this work with multiple bounded contexts in one repo?▼

Yes. If a CONTEXT-MAP.md exists at the repo root, the skill reads it to locate each context's CONTEXT.md and context-specific ADR directories. When the relevant context is unclear for a topic, it asks before proceeding.

What happens when my plan contradicts the existing code?▼

The contradiction is surfaced immediately with a direct comparison, such as the code canceling entire orders while the plan assumes partial cancellation. You must resolve which behavior is correct before the session continues.