grill-with-docs

To validate a project plan against a domain model, engage in a collaborative Q&A session to stress-test your feature approach against documented architectural and domain decisions. This ensures your plan aligns with existing project constraints before implementation begins.

Refining terminology and updating project documentation simultaneously happens through collaborative design sessions that automatically apply clarified terms to your project files. This inline update process keeps your documented decisions synchronized with ongoing terminology discussions.

Yes, collaborative design sessions can parse and update project documentation like CONTEXT.md and ADRs inline. As you discuss and finalize terminology or domain model decisions, the documentation is automatically modified to reflect those updates.

The best way to stress-test a new feature against documented domain decisions is to engage domain experts in a thorough Q&A conversation. This validates your feature design directly against the project's specific language and architectural records.

Yes, you need existing project documentation formats like CONTEXT.md and ADRs to clarify terminology effectively. The Skill requires these files to parse existing domain decisions and update them inline as new terminology refinements are agreed upon.