grill-with-docs

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

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/taylorelley/skills --skill grill-with-docs-taylorelley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/taylorelley/skills/tree/main/skills/workflow/grill-with-docs
Command: npx skills add https://github.com/taylorelley/skills --skill grill-with-docs-taylorelley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often contain fuzzy terminology, hidden assumptions, and decisions that contradict existing code or documentation. This Skill runs a relentless one-question-at-a-time interview that challenges your plan against the project's domain model, sharpening language and recording decisions as they crystallise. ## Core Features & Use Cases - Guided interrogation: Walks down each branch of the design tree one question at a time, providing a recommended answer for each, and explores the codebase directly when a question can be answered there. - Terminology enforcement: Challenges terms that conflict with the existing CONTEXT.md glossary, proposes canonical names for vague language, and updates CONTEXT.md inline as terms are resolved. - Decision recording: Offers to write an ADR only when a decision is hard to reverse, surprising without context, and the result of a real trade-off, using the format in ADR-FORMAT.md. - Use Case: Before implementing a partial order cancellation feature, run a grilling session to discover that your code cancels entire Orders, reconcile the contradiction, add 'cancellation' to CONTEXT.md, and record an ADR explaining the chosen boundary. ## Quick Start Ask the agent 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 design plan before implementing it?

Run a grilling session that interviews you one question at a time about every branch of the design tree. Each question comes with a recommended answer, and questions answerable from the codebase are resolved by exploring the code directly.

What is a CONTEXT.md file in a software project?

CONTEXT.md is a domain glossary at the repo root defining project-specific terms with one or two sentence definitions and avoided synonyms. It contains no implementation details and is updated inline as terminology decisions are made.

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, skip the ADR to avoid documentation noise.

Does this work with monorepos containing multiple domain contexts?

Yes. If a CONTEXT-MAP.md exists at the root, the session reads it to locate each context's CONTEXT.md and context-specific docs/adr directories. System-wide decisions go in the root docs/adr folder.

What happens when my plan contradicts the existing code?

The session cross-references your statements against the codebase and surfaces contradictions directly, such as when code cancels entire orders but the plan assumes partial cancellation. You must resolve which behavior is correct before proceeding.