grill-with-docs

Interrogate plans against CONTEXT.md domain models and documented decisions.

2|Updated Jun 1, 2017

Search Tags:#documentation #adr #glossary #domain-driven-design #architecture-review #requirements-clarification #terminology-validation

Ready to run

npx skills add https://github.com/carlos-algms/dotfiles --skill grill-with-docs-carlos-algms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/carlos-algms/dotfiles/tree/main/AI-configs/skills/grill-with-docs
Command: npx skills add https://github.com/carlos-algms/dotfiles --skill grill-with-docs-carlos-algms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you validate your design decisions by forcing alignment with your existing domain language, glossary, and recorded architectural trade-offs.

Core Features & Use Cases

Relentless plan interrogation: Walks down each branch of your design tree one question at a time until dependencies between decisions are resolved.
Terminology conflict detection: Challenges mismatched or ambiguous terms by comparing them against your documented glossary in CONTEXT.md.
Documentation updates as you decide: Updates CONTEXT.md inline when terms are resolved, keeping it free of implementation detail.
ADR offering when justified: Suggests creating an ADR only when the decision is hard to reverse, surprising without context, and involves a real trade-off.

Quick Start

Tell the AI to grill your plan using your project's existing CONTEXT.md and docs/adr decisions, asking one question at a time until it converges on a shared understanding.

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 an architecture plan against an existing domain model?▼

Validating an architecture plan against a domain model requires stress-testing decisions by interrogating each branch against documented glossary terms in CONTEXT.md. This process involves iterative, single-question pacing to resolve dependencies until terminology conflicts are eliminated and shared understanding converges.

What is requirements clarification through relentless plan interrogation?▼

Requirements clarification through plan interrogation is a technique that walks down each branch of a design tree one question at a time until dependencies between decisions are fully resolved. It forces alignment with existing domain language and recorded architectural trade-offs.

When do I need to create an Architecture Decision Record for a design choice?▼

You need to create an Architecture Decision Record when the design choice is hard to reverse, surprising without context, and involves a real trade-off. ADR creation is offered conditionally only when all three explicit criteria are met during the interrogation process.

How do I detect terminology conflicts between a new plan and my domain glossary?▼

Detecting terminology conflicts involves comparing proposed plan terms against your documented glossary in CONTEXT.md. Mismatched or ambiguous terms are challenged during interrogation, and CONTEXT.md is updated inline when terms are resolved, keeping it free of implementation detail.

Can I use domain-driven design terminology validation for integration discussions?▼

Yes, domain-driven design terminology validation applies to architecture and integration discussions where terminology must match CONTEXT.md. It explores the codebase and docs when possible to ensure proposed integration plans align with recorded architectural decisions.