What problem does it solve? Proposed features often drift from a project's established vocabulary, contradict locked architectural decisions, or carry unstated assumptions that surface only after costly implementation. This Skill interrogates a plan against the project's documented domain model before any PRD is written, so terminology, decisions, and boundaries are settled up front. ## Core Features & Use Cases - Domain-model grilling: Challenges a plan across five axes — terminology drift, ADR conflicts, unstated assumptions, boundary crossings, and unresolved forks — using OMNIGRID-CONTEXT.md and omnigrid/artifacts/adrs/ as the source of truth. - Inline decision capture: Writes resolved terms to the glossary, architectural trade-offs to sequentially numbered ADRs, and minor resolved misreadings to a Flagged ambiguities section, each with its rationale. - Lazy doc creation: Creates OMNIGRID-CONTEXT.md and ADR files the first time a decision makes them real, without scolding the user for missing docs. - Use Case: A developer proposes a refactor that renames a core concept. The Skill flags that the glossary explicitly avoids that synonym, quotes the conflicting ADR, forces a decision on the fork, and records the outcome — so the follow-up PRD stage needs no re-derivation. ## Quick Start Ask the assistant to grill your proposed feature plan against the project's context glossary and ADRs before writing the PRD.
