grill-with-docs

Interview an LLM plan against project domain documentation and code.

6|1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/snewhouse/aa-ma-forge --skill grill-with-docs-snewhouse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/snewhouse/aa-ma-forge/tree/main/claude-code/skills/grill-with-docs
Command: npx skills add https://github.com/snewhouse/aa-ma-forge --skill grill-with-docs-snewhouse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you stop drifting by forcing your proposed plan to be challenged against the project’s established domain language and documented decisions, reducing vague or conflicting terminology before execution.

Core Features & Use Cases

  • Relentless plan interrogation: Interview-driven questioning that walks the design tree branch-by-branch until shared understanding is reached.
  • Terminology sharpening: Detects glossary conflicts and replaces fuzzy or overloaded terms with precise canonical ones.
  • Scenario-based boundary testing: Probes edge cases with concrete invented scenarios to clarify relationships and constraints.
  • Code cross-referencing: Checks whether the user’s stated behavior matches what the code actually does, and surfaces contradictions.
  • Inline documentation updates: Updates CONTEXT.md in the project’s documented format as terms become resolved.
  • Sparing ADR offers: Proposes adding ADRs only when decisions meet the project’s criteria for being hard to reverse, surprising without context, and involving real trade-offs.

Quick Start

Ask the skill to stress-test your current plan by walking it down one branch at a time while it challenges terminology and validates assumptions against the codebase and existing docs.

Frequently Asked Questions about grill-with-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate an architecture plan against existing project documentation?

To stress-test a plan, you walk the design tree branch-by-branch using interview-driven questioning, sharpen terminology by detecting glossary conflicts, and probe edge cases with concrete scenarios to clarify constraints.

What is the best way to resolve terminology conflicts in domain modeling before coding?

This approach replaces fuzzy terms with canonical definitions by testing boundaries with invented scenarios, ensuring shared understanding of the domain model and preventing drift across sessions.

How do I prevent plan and code mismatches from causing drift across sessions?

You prevent drift by forcing the proposed plan to be challenged against existing documentation, applying a sequential question-by-question workflow to reach shared understanding and resolve dependencies.

When do I need to propose an Architecture Decision Record for a design choice?

ADRs are offered sparingly, exclusively for decisions that are hard to reverse and involve real trade-offs, ensuring documentation updates remain focused on significant architecture choices rather than minor plan adjustments.

Does this plan review approach work for long-horizon design planning?

It applies specifically to long-horizon design by using interview-driven questioning to walk the design tree branch-by-branch until shared understanding is reached and dependencies are resolved.