grill-with-docs

Grill With Docs

Grill With Docs is a documentation-grounded grilling session. It does the same branch-by-branch interrogation as grill-me, but every challenge is anchored in the project's current language, design records, and observable implementation.

When to Use

• A plan must align with existing docs, glossary terms, ADRs, or architecture notes
• The same concept is described differently across code, docs, and the current proposal
• You need to challenge a plan without drifting away from the repo's existing vocabulary
• A durable decision may need to be recorded while the conversation is still active

When NOT to Use

Instead of grill-with-docs	Use
You only need plan interrogation, not documentation grounding	grill-me
You are writing or updating docs after implementation changed	doc-update
You need a broad codebase walkthrough or onboarding tour	code-tour

Workflow

1. Gather the current sources of truth

Before questioning the plan, inspect the best available durable references:

• root docs such as README.md or architecture notes
• glossary or context files if they exist
• ADRs or decision logs
• the current code path if the docs are stale or incomplete

If the repo does not maintain dedicated glossary or ADR files, use the nearest durable project docs instead of inventing new ceremony.

2. Challenge the plan against documented language

When the plan uses a term that conflicts with current project language, call it out directly.

Examples:

• "The docs call this a workspace, but the plan says project. Which term is canonical?"
• "The ADR says we prefer thin adapters here. Why does this proposal add a new orchestration layer?"

3. Use one question at a time

Like grill-me, walk the tree branch by branch. Each question should either:

• confirm the plan fits the existing docs
• expose a contradiction
• force a new durable decision

4. Check code when the docs and proposal disagree