Skip to content

grill-with-docs — Documentation-Aware Review

  • Trigger: /grill-with-docs or keywords "against docs", "check against CONTEXT.md", "grill with docs"
  • Best for: Design review against existing docs, terminology alignment, ADR updates
  • Not for: New projects without docs, pure code review

Overview

grill-with-docs reviews your plan against the project's existing domain model (CONTEXT.md) and Architecture Decision Records (ADRs). It:

  • Checks plan terminology against CONTEXT.md
  • Validates alignment with existing architecture decisions
  • Updates documentation inline as decisions crystallize

Trigger Conditions

grill-with-docs auto-triggers when you:

  • Mention "check against docs", "align with ADRs"
  • Need to maintain consistency with project standards during design
  • Use the /grill-with-docs command

Examples

Example 1: Domain Model Alignment

/grill-with-docs Does our new payment plan align with the payment domain model in CONTEXT.md?

Claude will:

  1. Read payment domain definitions from CONTEXT.md
  2. Compare terminology in the plan
  3. Flag conflicts or inconsistencies

Example 2: ADR Consistency Check

/grill-with-docs Check if this caching plan violates ADR-003 (no distributed caching)

Example 3: Terminology Alignment

/grill-with-docs Align our terms: the plan uses "user" but CONTEXT.md uses "member"

Example 4: Update Docs

/grill-with-docs We decided on Redis Cluster — update ADR-005 to record this decision

Review Dimensions

DimensionSourceWhat's Checked
Domain TerminologyCONTEXT.mdNaming consistency
Architecture ConstraintsADRsConflicts with existing decisions
Code PatternsCodebaseAlignment with existing patterns
Business ProcessesDomain ModelProcess matching

Notes

  • If CONTEXT.md and actual code diverge, trust the code and update docs
  • ADRs record decisions — they're not immutable rules but changes should be documented
  • Review results come in two levels: "fixable" and "needs discussion"
  • Doc changes are applied via Edit — review before committing