grill-with-docs

Validate implementation plans against project domain models and architectural decisions.

27|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/roerohan/skills --skill grill-with-docs-roerohan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/roerohan/skills/tree/main/grill-with-docs
Command: npx skills add https://github.com/roerohan/skills --skill grill-with-docs-roerohan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the frequent issue of implementation plans that conflict with your project's existing domain terminology, documented architectural decisions, and actual codebase structure, which leads to wasted rework, team misalignment, and code that fails to fit project conventions.

Core Features & Use Cases

  • Relentless Plan Validation: Asks targeted, one-at-a-time questions about every aspect of your plan to resolve decision dependencies and catch misalignments before work begins.
  • Domain Terminology Enforcement: Flags conflicting or vague terms against your project's CONTEXT.md glossary to ensure consistent, precise language across the team.
  • Automated Documentation Sync: Updates CONTEXT.md inline as terms are resolved, and creates ADRs for high-impact, hard-to-reverse decisions to keep project documentation aligned with planning outcomes.
  • Use Case: For example, if you are designing a new order cancellation feature, this Skill will challenge whether your definition of "cancellation" matches the existing glossary, verify if the code supports partial cancellations as you described, and create an ADR if the chosen approach involves a non-reversible trade-off.

Quick Start

Use the grill-with-docs skill to stress-test your new user authentication feature plan against the project's existing domain terms and documented 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 validate implementation plans against existing project domain terminology?

To validate implementation plans against domain terminology, this Skill asks targeted questions one at a time to cross-reference your design against existing CONTEXT.md glossaries and catch misalignments before work begins.

What is an ADR and when do I need to create one for architectural decisions?

An ADR, or architectural decision record, captures irreversible trade-offs. You need to create one when a feature plan involves high-impact, hard-to-reverse architectural decisions that must be formally documented.

How do I keep documentation synced when updating domain terminology in my project?

To keep documentation synced when updating domain terminology, this Skill automatically updates your CONTEXT.md glossary inline as conflicting or vague terms are resolved during the plan validation workflow.

Can I use codebase exploration to verify if existing code supports my feature design?

Yes, you can use codebase exploration to verify if existing code supports your feature design. This Skill integrates with codebase exploration tools to cross-reference plans against actual code structure.

What is the best way to stress-test a new feature plan before development begins?

The best way to stress-test a new feature plan is through relentless plan validation that challenges your definitions, verifies codebase support, and flags misalignments with documented architectural decisions.

Why does my implementation plan fail to fit existing project conventions and domain models?

Your implementation plan fails to fit project conventions when it conflicts with existing domain terminology, documented architectural decisions, and actual codebase structure, which leads to wasted rework and team misalignment.