grill-with-docs

To validate architecture proposals, this skill grills planning documents against local context files and ADRs to ensure terminology, boundaries, and evidence align with current code before implementation begins.

Checking PRD alignment involves evaluating terminology and boundaries against local context files like .opencode-context.md and CONTEXT.md to verify expectations match existing domain models and code.

Recording durable architecture decisions in ADR format is handled by capturing validated outcomes from plan reviews directly into ADR or context notes to maintain documentation hygiene.

Yes, you can review domain models for terminology consistency by applying this skill during pre-implementation reviews to evaluate expectations against current code and domain language.

You need local context files such as .opencode-context.md, CONTEXT.md, and docs/adr/ to perform an architecture review and validate that plans align with current documentation.

Planning document terminology mismatches current code when domain alignment checks are skipped, meaning boundaries and expectations were not evaluated against existing context and domain language.