grill-with-docs

Cross-reference project plans against CONTEXT.md and ADR files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents architectural drift and terminology confusion by forcing your project plans to align with your existing domain model, glossary, and documented design decisions.

Core Features & Use Cases

  • Domain Alignment: Challenges your proposed plans against your existing CONTEXT.md to ensure consistent language and conceptual boundaries.
  • Decision Integrity: Validates new ideas against existing ADRs (Architecture Decision Records) to prevent conflicting or redundant design choices.
  • Use Case: When proposing a new feature, use this skill to interview your plan, ensuring that terms like "Customer" or "Order" are used correctly and that the design respects previously established architectural constraints.

Quick Start

Invoke the grill-with-docs skill to begin an interview session regarding your current project plan and its alignment with existing documentation.

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 new project plans against existing domain models and architecture decisions?

To validate project plans against domain models, you can run an interview process that cross-references your proposals with CONTEXT.md and ADR files. This identifies terminology inconsistencies and design conflicts before implementation begins.

What is architectural drift and how do I prevent it when adding new features?

Architectural drift occurs when new features deviate from established design constraints. Prevent it by stress-testing proposals against your documented domain model, glossary, and Architecture Decision Records to ensure conceptual boundaries remain intact.

How do I check if my proposed feature conflicts with existing Architecture Decision Records?

To check for conflicts with existing Architecture Decision Records, analyze your repository documentation to cross-reference new ideas against established ADRs. This validates decision integrity and prevents redundant or contradictory design choices.

Do I need a CONTEXT.md file to ensure domain alignment for my software architecture?

Yes, a CONTEXT.md file is required to ensure domain alignment. The validation process actively analyzes this documentation to guarantee terms like Customer or Order are used correctly and respect established system constraints.

What's the best way to maintain terminology precision in domain-driven design documentation?

The best way to maintain terminology precision in domain-driven design is to enforce alignment with your project glossary and CONTEXT.md. Challenge new plans during an interview session to verify consistent language and conceptual boundaries.