Challenge proposed plans against codebase language and documented decisions.
npx skills add https://github.com/kartikkabadi/skills --skill grill-with-docs-kartikkabadi
Please help me install this Agent Skill. Skill: grill-with-docs Source: https://github.com/kartikkabadi/skills/tree/main/grill-with-docs Command: npx skills add https://github.com/kartikkabadi/skills --skill grill-with-docs-kartikkabadi
This Skill helps teams pressure-test a plan against the language, assumptions, and documented decisions already present in a codebase. It reduces ambiguity by forcing terms to be precise and surfacing contradictions between proposed changes and existing documentation.
Ask me to grill your plan against the current codebase and documentation, then answer each question one by one as I challenge assumptions and refine the terminology.
High-intent search queries and answers about installing and using this skill.
To stress-test an architecture plan, interrogate the proposed changes against existing codebase terminology and documented decisions. Resolve ambiguity by forcing precise definitions, updating glossaries, and creating ADRs for decisions involving hard-to-reverse trade-offs.
Create an Architecture Decision Record during a design review when a proposed decision is hard to reverse, reflects real trade-offs between alternatives, and contradicts or significantly extends existing domain documentation and terminology within the codebase.
The best way to align terminology is through relentless clarification, asking questions one by one against the codebase, updating a shared glossary like CONTEXT.md as terms are resolved, and surfacing contradictions before implementation begins.
Yes, you can check existing codebase documentation directly when resolving ambiguity. Interrogating the repository allows you to answer questions from current code, validate assumptions, and ensure proposed plans align with documented architecture decisions.
Codebase exploration helps terminology alignment sessions by grounding abstract discussions in actual repository files, surfacing hidden contradictions, and verifying that proposed terms match the language already established in existing documentation.
babuallyChallenge proposed plans against codebase terminology and documented ADR decisions.
roerohanValidate implementation plans against project domain models and architectural decisions.
ogprotegeAudit repository documentation against code and recent changes.
Destynova2Analyze codebases for god functions, circular dependencies, dead code, and module boundaries.
