skills.rest
prabaljainn
prabaljainnCOMMUNITY
Explore all skills by this author →
𝕏@prabaljainnGitHub

grill-with-docs

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

Updated Aug 17, 2026
Search Tags:#documentation#adr#ubiquitous language#design review#plan validation#architecture decisions#domain glossary
One-click install
npx skills add https://github.com/prabaljainn/my-claude-code-setup --skill grill-with-docs-prabaljainn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/prabaljainn/my-claude-code-setup/tree/main/agents/skills/grill-with-docs
Command: npx skills add https://github.com/prabaljainn/my-claude-code-setup --skill grill-with-docs-prabaljainn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often use vague or conflicting terminology and make undocumented architectural decisions that future readers cannot understand. This Skill runs a structured interrogation of your plan against your project's existing domain language and documented decisions, updating CONTEXT.md and ADRs as decisions crystallize. ## Core Features & Use Cases - Plan Grilling: Interviews you one question at a time about every branch of your design, providing recommended answers and exploring the codebase when questions can be answered there. - Terminology Enforcement: Challenges terms that conflict with CONTEXT.md, sharpens fuzzy language into canonical terms, and updates the glossary inline as terms are resolved. - Decision Recording: 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 implementing a partial order cancellation feature, run a grilling session that cross-checks your claims against the code, resolves whether 'cancellation' means full or partial, updates CONTEXT.md, and records an ADR explaining the chosen approach. ## Quick Start Ask the assistant to grill you on your implementation plan for a new feature and update the project glossary 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 implementing it?▼

Run a grilling session that interviews you one question at a time about every branch of the design tree, with recommended answers provided for each question. Questions answerable from the codebase are resolved by exploring the code instead of asking you.

How to keep a project glossary of domain terms consistent?▼

Maintain a CONTEXT.md file with opinionated term definitions and an _Avoid_ list of rejected synonyms. During design discussions, conflicting usage is called out immediately and resolved terms are written into CONTEXT.md inline rather than batched.

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 real trade-off between genuine alternatives. Easy-to-reverse or obvious decisions should be skipped.

Does this work with monorepos containing multiple domain contexts?▼

Yes. If a CONTEXT-MAP.md exists at the repo root, the skill reads it to locate each context's own CONTEXT.md and docs/adr directory. Single-context repos use one root CONTEXT.md, and files are created lazily only when first needed.

What is the difference between CONTEXT.md and an ADR?▼

CONTEXT.md is purely a glossary of domain terms with tight definitions and avoided synonyms, containing no implementation details. An ADR records a specific architectural decision and its rationale, stored as a numbered file in docs/adr/.

Related Skills

Explore More Software Engineering Skills→
Matt-Aurora-VenturesMatt-Aurora-Ventures
58

brainstorming

Guides teams from vague ideas to approved designs via structured questioning and multi-approach proposals.

Community
Intermediate
cropsggcropsgg
15

domain-context

Standardize domain terminology across projects using CONTEXT.md and ADRs.

Community
Intermediate
a35506322a35506322

grill-with-docs

Stress-test project plans against domain documentation, codebase, and ADRs.

Community
Intermediate
Samuelca6399Samuelca6399

remote-collaboration

Design async-first workflows with RFCs, agendas, and communication norms for distributed teams.

Community
Intermediate