grill-with-docs

Validate project plans against a domain model and update CONTEXT.md and ADRs.

Updated May 11, 2026
One-click install
npx skills add https://github.com/guhans6/agent-workbench --skill grill-with-docs-guhans6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/guhans6/agent-workbench/tree/main/shared/skills/grill-with-docs
Command: npx skills add https://github.com/guhans6/agent-workbench --skill grill-with-docs-guhans6

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps users to validate their plans against a domain model, refine their terminology, and update documentation inline, ensuring a shared understanding and maintaining accurate records.

Core Features & Use Cases

  • Domain Model Validation: Challenge plans with the existing domain model to ensure alignment.
  • Terminology Refinement: Sharpen and clarify terminology during discussions.
  • Documentation Update: Update CONTEXT.md and ADRs inline as decisions are made.
  • Use Case: When developing a new feature, use this Skill to discuss and validate the design against the project's domain model and documented decisions.

Quick Start

Start a grill-with-docs session to discuss your feature design and validate it against the project's domain model.

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 feature plans against a domain model during design discussions?

Domain model validation challenges your feature plans against existing architecture to ensure alignment. By stress-testing designs collaboratively, you verify that new features fit the established domain boundaries and documented decisions before implementation.

How do I update CONTEXT.md and ADRs inline during design discussions?

Inline documentation updates capture design decisions directly in CONTEXT.md and ADRs during collaborative discussions. This ensures architectural decisions and domain context are recorded accurately as discussions happen, maintaining shared understanding.

How do I refine terminology to ensure alignment across a software project?

Terminology refinement sharpens and clarifies domain language during design discussions to ensure alignment. It identifies ambiguous terms and updates inline documentation, guaranteeing all collaborators share a precise understanding of the domain.

Do I need to explore the codebase before validating plans against the domain model?

Exploring your codebase and documentation is required to provide the context for domain model validation. The Skill analyzes existing project files, ADRs, and domain models to accurately stress-test new plans and update inline documentation.

When should I use domain model validation for feature design?

Use domain model validation when developing new features to ensure alignment with existing architecture. It is ideal for collaborative design discussions where you need to refine terminology and update CONTEXT.md or ADRs inline as decisions are made.

What are the limitations of using inline documentation updates for design validation?

Design validation focuses on terminology refinement and inline documentation updates rather than structural code testing. It ensures plans align with the domain model and captures decisions in files like ADRs, but does not execute or verify code behavior.