grill-with-docs

Validating an implementation plan against a domain model involves cross-referencing proposed terminology and boundaries with a repository glossary in CONTEXT.md. This Skill interrogates your plan one question at a time to expose ambiguous terms and verify alignment with documented architecture.

An ADR is an Architectural Decision Record documenting trade-offs. You need to update it during code review when your implementation plan introduces hard, surprising decisions that conflict with or extend existing documented architecture boundaries.

Checking feature conflicts against documented architectural decisions requires reconciling your plan with docs/adr. This Skill cross-checks codebase implementation against repository boundaries and surfaces inconsistencies requiring ADR updates.

Yes, domain modeling clarifies requirements by challenging ambiguous terminology against project glossaries. This Skill applies iterative interrogation to refine assumptions, ensuring precise domain-meaningful terminology before implementation begins.

Stress-testing a design plan for terminology inconsistencies requires reconciling proposed terms with CONTEXT.md. This Skill forces precise definitions and explores codebase implementation to confirm or contradict claims, surfacing boundary conflicts.