grill-with-docs

Stress-tests plans through structured interviews and updates CONTEXT.md glossaries and ADRs inline.

Updated May 7, 2026
One-click install
npx skills add https://github.com/Pieter-1337/Euricom-tsz --skill grill-with-docs-pieter-1337
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/Pieter-1337/Euricom-tsz/tree/main/.claude/skills/matt-grill-with-docs
Command: npx skills add https://github.com/Pieter-1337/Euricom-tsz --skill grill-with-docs-pieter-1337

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often contain fuzzy terminology, hidden contradictions with existing code, and undocumented decisions that cause confusion later. This Skill runs a relentless one-question-at-a-time interview that challenges your plan against your project's domain language and documented decisions, capturing resolutions in CONTEXT.md and ADRs as they happen. ## Core Features & Use Cases - Plan Grilling Interview: Walks down each branch of the design tree one question at a time, providing a recommended answer for each question and exploring the codebase when answers can be found there. - Terminology Sharpening: Challenges terms that conflict with the existing CONTEXT.md glossary, proposes canonical terms for vague language, and updates the glossary inline as terms are resolved. - Selective ADR Creation: Offers Architecture Decision Records only when a decision is hard to reverse, surprising without context, and the result of a real trade-off, using a minimal ADR format. - Use Case: Before implementing a new order cancellation feature, run a grilling session to discover that your code cancels entire Orders while your plan assumes partial cancellation, then record the resolved terminology in CONTEXT.md and the cancellation strategy as an ADR. ## Quick Start Grill my implementation plan for the new billing feature and update our domain docs as we resolve decisions.

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

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

How to keep domain terminology consistent across a project?

Maintain a CONTEXT.md glossary that defines canonical terms, lists aliases to avoid, and flags ambiguities with resolutions. During planning discussions, any term conflicting with the glossary is called out immediately and the file is updated inline as terms are resolved.

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 genuine alternatives. If any condition is missing, skip the ADR to avoid documentation noise.

Does this work with multiple bounded contexts in one repo?

Yes. If a CONTEXT-MAP.md exists at the repo root, it lists each context, its location, and its relationships. The session infers which context the current topic relates to and asks when unclear, keeping context-specific ADRs in each context's own docs/adr directory.

What happens when my plan contradicts the existing code?

The contradiction is surfaced explicitly during the session. For example, if the code cancels entire Orders but you describe partial cancellation, you are asked which behavior is correct before proceeding.