grill-with-docs

Analyze project codebase and documentation for terminology consistency and domain model alignment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enhances understanding and documentation of a project's domain model, ensuring terminology clarity and consistency.

Core Features & Use Cases

  • Domain Model Review: Real-time examination of design decisions for alignment with the documented model.
  • Terminology Clarification: Provides precise definitions and corrects any inconsistencies or ambiguities.
  • Documentation Updates: Updates CONTEXT.md and ADRs inline as decisions are made, maintaining a living document.
  • Use Case: When reviewing a proposed feature that interacts with customer data, this Skill ensures the design aligns with the project's existing definitions and policies.

Quick Start

Use the grill-with-docs skill to review the customer data handling in the new feature proposal 'customer-profile-upgrade.md'.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
How do I ensure codebase terminology aligns with my documented domain model?

Domain model review performs real-time analysis of your project codebase and documentation to ensure terminology consistency and alignment with the documented domain model. It corrects ambiguities and validates design decisions against existing CONTEXT.md files.

How do I update ADRs and CONTEXT.md automatically during code review?

You update ADRs and CONTEXT.md inline during code review by proposing documentation updates as decisions are made. This maintains a living document reflecting the current domain model and terminology.

What is the best way to check feature proposals against existing domain definitions?

The best way to check feature proposals against existing domain definitions is to review proposed features interacting with customer data, ensuring the design aligns with existing project definitions and policies.

Do I need existing CONTEXT.md and ADRs to analyze domain model consistency?

Yes, you need existing CONTEXT.md and ADRs to analyze domain model consistency. The process requires access to these existing documents and the ability to navigate the codebase to propose or update them.

Can I use real-time documentation analysis for projects without existing ADRs?

You can use real-time documentation analysis without existing ADRs, as the process can propose and create new ADRs based on interactions. However, it works best when updating existing CONTEXT.md files for terminology consistency.

Why does domain terminology become inconsistent between code and documentation?

Domain terminology becomes inconsistent when design decisions are made without real-time review against the documented model. This creates ambiguities and misalignment between the codebase and existing documentation.