grill-with-docs

To validate an architecture plan against a codebase, this Skill cross-checks your proposed design against existing repository documentation and context files. It identifies hidden assumptions and challenges ambiguous terms to ensure your plan aligns with current architecture notes.

Aligning domain terminology requires cross-checking proposed terms against a project glossary. This Skill interrogates ambiguous domain language one question at a time, recommends concrete definitions, and captures resolved terms directly in CONTEXT.md.

Documenting architecture decisions during a design review involves recording hard-to-reverse or surprising trade-offs as ADRs. This Skill automatically suggests creating Architecture Decision Records when resolved decisions warrant formal documentation.

Yes, you can use context files and ADRs to stress-test design plans. This Skill reads existing CONTEXT.md files and architecture notes to pressure-test your proposed boundaries and naming conventions before implementation begins.

You should record a resolved decision as an ADR when the trade-off is hard to reverse or surprising. This Skill evaluates resolved terminology and design boundaries, updating CONTEXT.md for general alignment and ADRs for significant architectural shifts.