grill-with-docs

Stress-tests design plans through structured interviews while updating CONTEXT.md glossaries and ADRs inline.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/arndvs/ctrlshft --skill grill-with-docs-arndvs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/arndvs/ctrlshft/tree/main/skills/grill-with-docs
Command: npx skills add https://github.com/arndvs/ctrlshft --skill grill-with-docs-arndvs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design plans often contain fuzzy terminology, hidden contradictions with existing code, and undocumented decisions that cause confusion later. This Skill interviews you relentlessly about every aspect of a plan, challenges inconsistencies against your codebase and domain glossary, and captures resolved terminology and architectural decisions as documentation the moment they crystallize. ## Core Features & Use Cases - Socratic Design Interrogation: Walks down each branch of the design tree one question at a time, providing recommended answers and resolving dependencies between decisions. - Inline Glossary Maintenance: Updates CONTEXT.md immediately when terms are resolved, flags ambiguous language, and challenges usage that conflicts with existing definitions. - Selective ADR Creation: Offers Architecture Decision Records only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Use Case: Before writing a PRD for a new billing feature, run this Skill to stress-test your domain model — it will catch that you use "account" to mean both Customer and User, record the distinction in CONTEXT.md, and document why you chose event-sourced orders in an ADR. ## Quick Start Ask the agent to grill you on your design plan for the new feature using the grill-with-docs skill, answering each question one at a time until shared understanding is reached.

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 implementation?▼

Run this Skill to be interviewed one question at a time about every branch of your design tree. Each question comes with a recommended answer, and questions answerable from the codebase are resolved by exploring the code directly instead of asking you.

What is a CONTEXT.md file in domain-driven design documentation?▼

CONTEXT.md is a project glossary defining canonical domain terms, their avoided aliases, relationships, and flagged ambiguities. It contains no implementation details — only the shared language of the domain, updated inline as terms are resolved during design discussions.

When should I write an Architecture Decision Record?▼

Write an ADR only when all three conditions hold: the decision is hard to reverse, it is surprising without context, and it resulted from a genuine trade-off between alternatives. Easy-to-reverse or obvious decisions should be skipped to avoid documentation noise.

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

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

What happens after the design interview reaches shared understanding?▼

The Skill offers three handoff paths: write a formal PRD, break the plan directly into GitHub issues, or start implementing immediately. If context fills up mid-interview, it persists decisions to a working directory for continuation.