Verified:GitHub

grill-with-docs

Aligns proposed designs and domain terminology with existing CONTEXT.md and ADR documentation via interactive codebase cross-checking.

3|Updated May 11, 2026

Search Tags:#documentation #domain modeling #architecture decisions #ADRs #requirements clarification #codebase review #glossary consistency

Ready to run

npx skills add https://github.com/JeromyJSmith/lattice-platform --skill grill-with-docs-jeromyjsmith

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/JeromyJSmith/lattice-platform/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/JeromyJSmith/lattice-platform --skill grill-with-docs-jeromyjsmith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you validate that your design, terminology, and decisions match the project’s existing domain model and documentation, reducing misunderstandings and rework.

Core Features & Use Cases

Relentless plan interrogation: Questions every aspect of the user’s plan until a shared understanding is reached.
Domain-model and glossary alignment: Detects terminology conflicts and proposes precise canonical terms.
Scenario-driven boundary testing: Stress-tests relationships with concrete edge-case scenarios.
Code and documentation cross-checking: Uses codebase exploration to confirm claims and surface contradictions.
Inline documentation updates: Updates CONTEXT.md as terms are resolved and offers ADRs sparingly when trade-offs are real.

Quick Start

Invite the skill to review your proposed plan and answer one question at a time until it aligns your decisions with the existing CONTEXT.md and ADR trail.

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 architecture decisions against an existing codebase and domain glossary?▼

Stress-testing proposed architecture involves sequential questioning with feedback gating to resolve ambiguities. It cross-checks your codebase to confirm claims and surfaces contradictions before updating CONTEXT.md and offering ADRs for irreversible trade-offs.

What is the best way to ensure domain terminology consistency before implementing a new plan?▼

Domain modeling alignment detects terminology conflicts between proposed plans and existing project documentation. It proposes precise canonical terms and updates CONTEXT.md inline as terms are resolved during interactive interrogation sessions.

How do I clarify ambiguous requirements through scenario-driven boundary testing?▼

Scenario-driven boundary testing stress-tests relationships between domain concepts using concrete edge-case scenarios. This process resolves misunderstandings and reduces rework by reaching a shared understanding through sequential questioning.

When do I need to create an Architecture Decision Record for a design trade-off?▼

Architecture Decision Records are needed when a design trade-off is irreversible. The process recommends ADRs sparingly and uses lazy scaffolding to document real trade-offs alongside resolved CONTEXT.md updates.

Can I use interactive interrogation to surface contradictions between my plan and existing ADRs?▼

Interactive interrogation surfaces contradictions between proposed plans and existing ADRs. It questions every aspect of the plan until a shared understanding is reached and confirms claims through codebase exploration.