grill-with-docs

Name: grill-with-docs
Availability: InStock
Author: Spontus

Stress-test proposed plans against repository glossary and architectural decisions.

1|Updated May 22, 2026

Search Tags:#domain modeling #architecture decisions #ADR creation #documentation updates #codebase review #glossary alignment #terminology disambiguation

Ready to run

npx skills add https://github.com/spontus-reach/spontus --skill grill-with-docs-spontus-reach

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents mismatched terminology and undocumented assumptions by forcing a plan to align with the project’s existing glossary and recorded decisions.

Core Features & Use Cases

Relentless plan interrogation: Breaks the design tree into one-by-one questions, resolving dependencies between decisions until understanding is shared.
Glossary and terminology sharpening: Challenges conflicting or vague terms against CONTEXT.md and proposes canonical wording when ambiguity appears.
Doc-first decision crystallization: Updates CONTEXT.md inline as terms are resolved and offers ADRs only when trade-offs are meaningful, surprising, and hard to reverse.

Quick Start

Use grill-with-docs to challenge your proposed architecture against the repository’s domain language and update CONTEXT.md and ADRs as decisions become clear.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema

How do I verify an architecture plan against existing domain documentation?▼

Stress-testing a plan against domain documentation involves interrogating your proposed architecture against the repository's CONTEXT.md glossary and existing ADRs. The skill breaks the design into single questions, resolving dependencies and updating documentation inline as terminology conflicts are clarified.

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

An Architecture Decision Record is needed when a design trade-off is meaningful, surprising, and hard to reverse. The skill evaluates your proposed plan during interrogation and offers ADR creation only for trade-offs that meet these specific criteria, keeping documentation lightweight otherwise.

How do I disambiguate conflicting domain terminology in a codebase review?▼

To disambiguate conflicting domain terminology, the skill cross-checks vague or conflicting terms against the project's CONTEXT.md file and proposes canonical wording. It inspects the codebase when needed to ensure terminology precision and relationship boundaries align with actual implementations.

Can I update my CONTEXT.md file inline while resolving architecture decisions?▼

Yes, you can update CONTEXT.md inline while resolving architecture decisions. The skill applies glossary and terminology updates directly to CONTEXT.md using a prescribed format as terms are clarified during the guided interrogation process.

What are the limitations of using glossary alignment for architecture reviews?▼

A limitation of glossary alignment for architecture reviews is that it requires guided, single-question feedback-waiting interrogation, meaning it cannot process decisions asynchronously. It also relies entirely on the accuracy of existing CONTEXT.md and ADR documentation to validate proposed plans.