grill-with-docs

Stress-test project plans against domain glossaries, ADRs, and codebase context.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of building features that conflict with existing project terminology, undocumented architectural decisions, and established domain context, which leads to rework, team misalignment, and confusing code that future engineers cannot easily understand.

Core Features & Use Cases

  • Domain Alignment Grilling: Relentlessly questions every aspect of your plan to resolve ambiguities and align with existing project context and codebase implementation.
  • Terminology Sharpening: Catches conflicting or vague terms against your project's CONTEXT.md glossary and proposes precise canonical language to avoid cross-team miscommunication.
  • Inline Documentation Updates: Automatically updates your CONTEXT.md glossary and creates ADRs for high-impact, hard-to-reverse decisions as they are crystallized during the session.
  • Use Case: For example, when designing a new order cancellation feature, the skill will flag if you use "account" when the project glossary defines that term as "Customer", stress-test edge cases like partial cancellations against existing code, and create an ADR if you decide to deviate from the standard event-sourced pattern for this specific use case.

Quick Start

Use the grill-with-docs skill to stress-test your proposed new user authentication flow against the existing project domain model and glossary.

Frequently Asked Questions about grill-with-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a new feature plan against existing project documentation and codebase context?▼

To validate a feature plan against existing project documentation, you stress-test proposed plans by cross-referencing them with project glossaries, prior ADRs, and codebase implementation to surface contradictions before writing code.

What is domain alignment for software engineering plans and why does it matter?▼

Domain alignment resolves misalignment between proposed plans and existing domain terminology or undocumented architectural decisions, preventing implementation errors, rework, and team confusion caused by conflicting codebase context.

How do I keep a project glossary and CONTEXT.md updated when proposing new architectural decisions?▼

You keep a CONTEXT.md glossary updated by sharpening vague terms into canonical language during plan validation, automatically updating the glossary and creating ADRs for hard-to-reverse architectural trade-offs as they crystallize.

Does plan validation work without existing ADRs or a defined domain glossary?▼

Plan validation works best with existing ADRs and a CONTEXT.md glossary, but can still question ambiguities and establish canonical domain language for undocumented architectural decisions during your software engineering workflow.

When should I create an ADR instead of just updating the project glossary?▼

You should create an ADR when plan validation crystallizes a high-impact, hard-to-reverse architectural trade-off, whereas glossary updates apply to resolving terminology conflicts and sharpening domain language definitions.