grill-with-docs

Validate architecture plans against project domain language in CONTEXT.md and ADRs.

40|9|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/akillness/jeo-skills --skill grill-with-docs-akillness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/akillness/jeo-skills/tree/main/.agent-skills/grill-with-docs
Command: npx skills add https://github.com/akillness/jeo-skills --skill grill-with-docs-akillness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides teams to validate architecture plans against the project's domain language, surfacing terminology gaps and ensuring documentation stays aligned with decisions as they crystallize.

Core Features & Use Cases

  • Glossary alignment: checks CONTEXT.md terminology against the current model and ADRs to prevent drift.
  • Inline documentation updates: updates CONTEXT.md and ADRs as decisions crystallize during the session.
  • Triage-ready outputs: produces structured notes and suggested issues for implementation, triage, and follow-up work.

Quick Start

Begin the grilling session by reviewing CONTEXT.md, relevant ADRs, and source files to stress-test domain terminology.

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 plans against my project's domain model?

Validate architecture plans against the domain model by running a deterministic grilling workflow that stress-tests domain terminology against CONTEXT.md and ADRs. This process surfaces terminology gaps and enforces glossary alignment to prevent documentation drift during design reviews.

What is glossary alignment and how does it prevent documentation drift?

Glossary alignment checks CONTEXT.md terminology against the current model and ADRs to prevent drift. It ensures documentation stays aligned with decisions as they crystallize by sharpening precision and surfacing terminology gaps during design reviews.

When do I need to create an ADR during a design review?

Create an ADR during a design review when architectural decisions crystallize during the grilling session. The workflow applies lazy ADR creation, generating records only when terminology alignment and precision sharpening confirm a new architectural decision.

Can I update CONTEXT.md inline while reviewing architecture plans?

Yes, you can update CONTEXT.md inline while reviewing architecture plans. The grilling workflow enforces inline documentation updates, modifying CONTEXT.md and ADRs in place as decisions crystallize and terminology gaps are resolved during the session.

What is the best way to prepare for a domain model terminology triage?

Prepare for domain model terminology triage by reviewing CONTEXT.md, relevant ADRs, and source files to stress-test domain terminology. This quick start step establishes the baseline needed for the deterministic grilling workflow to validate plans effectively.