grill-with-docs

Decision tracking through Architecture Decision Records captures hard-to-reverse choices, ensuring they remain traceable over time. You create ADRs when decisions crystallize during plan validation to maintain a permanent record of why specific architectural paths were chosen.

You can use this grilling approach for any project scale where domain language consistency and decision traceability matter. It works by relentlessly questioning your plan against existing CONTEXT.md and ADRs to promote stakeholder alignment regardless of project size.

The best way to ensure decisions are traceable is by updating CONTEXT.md inline and recording ADRs when decisions become hard to reverse. This captures changes directly as they crystallize, linking domain language updates to their underlying architectural rationale.

Project plans develop inconsistencies with domain language when assumptions are not challenged against existing CONTEXT.md and ADRs. Grilling your plan against concrete codebase scenarios surfaces these gaps and ambiguities before implementation begins.