grill-with-docs

Stress-tests plans against domain glossaries and updates CONTEXT.md and ADRs inline.

4|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/gabriellst/codm --skill grill-with-docs-gabriellst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/gabriellst/codm/tree/main/.claude/skills/grill-with-docs
Command: npx skills add https://github.com/gabriellst/codm --skill grill-with-docs-gabriellst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often contain fuzzy terminology and hidden contradictions with existing code and documented decisions. This Skill runs a structured interrogation session that challenges your plan against the project's domain model, sharpening language and capturing decisions as documentation before implementation begins. ## Core Features & Use Cases - Relentless Q&A Interrogation: Asks one question at a time with a recommended answer, walking each branch of the design tree until dependencies between decisions are resolved. - Glossary Enforcement: Challenges terms that conflict with CONTEXT.md, sharpens vague language into canonical terms, and cross-references claims against the actual codebase. - Inline Documentation: Updates CONTEXT.md the moment a term is resolved and offers ADRs only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Use Case: Before building a partial 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 chosen approach in an ADR. ## Quick Start Ask the agent to grill you on your implementation plan for a new feature and update the project documentation as decisions are made.

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 aspect of the plan, providing a recommended answer for each question. Questions that can be answered by exploring the codebase are resolved through code exploration instead of asking you.

How to keep a domain glossary consistent with the codebase?

Maintain a CONTEXT.md glossary and challenge any term that conflicts with it during planning discussions. When a term is resolved, update CONTEXT.md immediately rather than batching changes, and keep the file free of implementation details.

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.

Does this work with repositories that have multiple bounded contexts?

Yes. If a CONTEXT-MAP.md exists at the repository root, the repo is treated as multi-context, with each context keeping its own CONTEXT.md and context-specific docs/adr directory alongside system-wide decisions.

What happens if no CONTEXT.md or ADR files exist yet?

Files are created lazily, only when there is something to write. A CONTEXT.md is created when the first term is resolved, and the docs/adr directory is created when the first ADR is needed.