grill-with-docs

Challenges plans against domain glossaries and updates CONTEXT.md and ADR documentation inline.

2|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/Nzettodess/Awesome-Agent-Skills --skill grill-with-docs-nzettodess
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/Nzettodess/Awesome-Agent-Skills/tree/main/Skills/Engineering%20Skills/skills/engineering/grill-with-docs
Command: npx skills add https://github.com/Nzettodess/Awesome-Agent-Skills --skill grill-with-docs-nzettodess

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often contain fuzzy terminology and hidden contradictions with existing code and documented decisions, leading to misaligned implementations. This Skill stress-tests a plan through a structured interview, resolving terminology conflicts and recording decisions as they crystallise. ## Core Features & Use Cases - Plan Grilling Session: Interviews the user one question at a time, walking each branch of the design tree and providing recommended answers. - Glossary Enforcement: Challenges terms that conflict with CONTEXT.md, sharpens vague language into canonical terms, 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. - Use Case: Before implementing a partial order cancellation feature, run a grilling session to discover that the codebase cancels entire Orders, reconcile the contradiction, define 'cancellation' precisely in CONTEXT.md, and record the chosen approach as an ADR. ## Quick Start Grill my plan for adding partial order cancellation and update the project docs as we make 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 design plan before implementation?▼

Run a grilling session that interviews you one question at a time, walking each branch of the design tree with recommended answers. It explores the codebase to answer questions directly and surfaces contradictions between your plan and existing code.

How to maintain a domain glossary in a software project?▼

Keep a CONTEXT.md file at the repo root defining canonical terms with aliases to avoid. Update it inline whenever a term is resolved during design discussions, keeping definitions to one or two sentences and free of implementation details.

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 these three conditions is missing, skip the ADR to avoid documentation noise.

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

Yes, multi-context repos use a CONTEXT-MAP.md at the root listing each context's location and relationships. The skill infers which context the current topic relates to and asks when it is unclear.

What happens when my plan contradicts the existing code?▼

The skill cross-references your statements against the codebase and surfaces contradictions directly, such as when code cancels entire orders but the plan assumes partial cancellation. You then decide which behavior is correct.