grill-with-docs

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often contain fuzzy terminology and undocumented decisions that cause confusion later. This Skill runs a structured interrogation of your plan against your project's existing domain language and documented decisions, updating CONTEXT.md glossaries and Architecture Decision Records as terms and trade-offs are resolved. ## Core Features & Use Cases - Relentless plan interrogation: Asks one question at a time, walking each branch of the design tree and providing a recommended answer for every question. - Domain language enforcement: Challenges terms that conflict with CONTEXT.md, sharpens vague wording into canonical terms, and updates the glossary inline as terms are resolved. - Decision capture with ADRs: Offers to write an ADR only when a decision is hard to reverse, surprising without context, 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, discover that the code contradicts your assumption about partial cancellations, and record the resolution as an ADR. ## Quick Start Grill my plan for the new billing feature against our existing domain model and update the docs as we go.

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 the design tree, providing a recommended answer for each question. Questions answerable from the codebase are resolved by exploring the code instead of asking you.

How do I keep a domain glossary consistent with my code?▼

Maintain a CONTEXT.md glossary of canonical terms with avoided synonyms, and challenge any usage that conflicts with it during design discussions. Update the glossary inline as each term is resolved rather than batching changes.

When should I write an Architecture Decision Record?▼

Write an ADR only when a decision is hard to reverse, surprising without context, and the result of a real trade-off between genuine alternatives. If any of the three conditions 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 belongs to and asks when unclear.

What are the limitations of a grilling session for design review?▼

The session depends on your answers and the existing documentation, so undocumented assumptions outside the codebase may go unchallenged. CONTEXT.md is strictly a glossary and must not be used as a spec or scratch pad for implementation details.