grill-with-docs

Stress-tests plans against domain glossaries and records decisions in CONTEXT.md and ADR files.

2|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill grill-with-docs-brandtam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/brandtam/rubber-ducky-legacy/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill grill-with-docs-brandtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often embed fuzzy terminology and undocumented decisions that later cause confusion or get re-litigated. This Skill runs a structured interrogation of your plan against your project's existing domain language and architecture decision records, sharpening terms and capturing decisions as they crystallize. ## Core Features & Use Cases - Plan interrogation: Asks one question at a time, walking each branch of the design tree and providing a recommended answer for every question. - Glossary enforcement: Challenges terms that conflict with CONTEXT.md, proposes canonical names for vague language, and updates the glossary inline as terms are resolved. - Selective ADR capture: Offers an Architecture Decision Record only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Use Case: Before implementing a partial order cancellation feature, run a grilling session to reconcile the plan with the existing Order/Invoice glossary, verify behavior against the codebase, and record the cancellation boundary decision as an ADR. ## Quick Start Ask the agent to grill you on your implementation plan for the current feature and update CONTEXT.md and ADRs as decisions are made.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
How do I stress-test a software design plan before coding?▼

Run a grilling session that interviews you one question at a time about every branch of the plan, providing a recommended answer for each. Questions answerable from the codebase are resolved by exploring the code directly instead of asking.

What is a CONTEXT.md glossary file in a repository?▼

CONTEXT.md is a domain glossary defining canonical terms, aliases to avoid, relationships between concepts, and flagged ambiguities. It contains no implementation details and is updated inline as terminology is resolved during design discussions.

When should I write an Architecture Decision Record?▼

Write an ADR only when a decision is hard to reverse, surprising without context, and the result of a genuine trade-off between alternatives. If any of the three conditions is missing, the decision does not need a record.

Does this work with multiple bounded contexts in one repo?▼

Yes. If a CONTEXT-MAP.md exists at the repo root, the session reads it to locate each context's CONTEXT.md and context-specific ADR directories, then infers which context the current topic belongs to or asks when unclear.

What happens when my plan contradicts the existing code?▼

The session cross-references stated behavior against the codebase and surfaces contradictions directly, for example when the code cancels entire orders but the plan assumes partial cancellation is possible.