grill-with-docs

You validate a project plan by stress-testing its assumptions against repository CONTEXT.md and ADRs. This process interviews decisions branch-by-branch, resolving dependencies and aligning terminology to reduce ambiguity and future rework.

You should create an Architecture Decision Record only when a decision is hard to reverse, surprising without context, and represents real trade-offs. This ensures documentation remains sparse and captures only critical architectural choices.

Scenario-driven validation works by iteratively exploring the codebase and interviewing assumptions to resolve decision dependencies. It validates integration patterns and domain relationships against existing CONTEXT.md files to ensure architectural alignment.

Yes, you can review codebase architecture and update documentation simultaneously. The approach cross-checks design claims against the codebase, updates CONTEXT.md inline when concepts are resolved, and optionally creates ADRs for significant trade-offs.