grill-with-docs

Yes, you can update project documentation inline as decisions are made during your plan validation. This Skill supports real-time terminology refinement and automatically updates your CONTEXT.md and ADRs to reflect new design choices.

Yes, you need CONTEXT.md and ADRs to perform domain model validation, as the Skill requires access to these files for context. They provide the established terminology and architectural decisions needed to check your plan accurately.

The best way to align feature terminology with existing documentation is to refine and clarify terms in real-time during a design review. This process catches inconsistencies early and updates your project's domain model records immediately.

Design validation works by challenging your current feature design against the established domain model and documentation to identify inconsistencies. It ensures your existing components remain aligned with the project's architectural standards and terminology.

You should not use documentation-based plan validation if your project lacks an established domain model or foundational documents like CONTEXT.md and ADRs. Without these context sources, the Skill cannot accurately compare or stress-test your plans.