grill-with-docs

Challenge proposed plans against codebase terminology and documented ADR decisions.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/babually/bongo-template --skill grill-with-docs-babually
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/babually/bongo-template/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/babually/bongo-template --skill grill-with-docs-babually

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you challenge a proposed plan against the codebase, the existing domain language, and documented architectural decisions so you can catch ambiguities, contradictions, and missing trade-offs early.

Core Features & Use Cases

  • Relentless plan interrogation: Walks through a design one question at a time, asking for clarifications until the intent is unambiguous.
  • Codebase-informed guidance: Uses repository structure and documentation to resolve questions from the implementation instead of guessing.
  • Documentation upkeep: Updates glossary and ADR-style documentation inline as terms and decisions are clarified.
  • Use case: A team is introducing a new workflow and wants to ensure the terminology matches existing concepts and that any durable architectural decision is recorded properly.

Quick Start

Ask the skill to review your plan against the repository’s current terminology and decisions, then answer its questions one by one.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
How do I review an architecture plan against existing codebase decisions?

Review an architecture plan by challenging the proposed design against existing repository structure and documented decisions to surface ambiguities, contradictions, and hidden trade-offs. The skill interrogates the plan one question at a time until intent is unambiguous.

What is the best way to align domain terminology with existing glossary documentation?

Align domain terminology by reconciling proposed plan concepts against the project's existing glossary. As terms are clarified during plan interrogation, glossary entries are updated inline to ensure domain language remains consistent across the codebase.

How do I capture architectural decisions as I refine a project plan?

Capture architectural decisions by recording them in ADR-style documentation as they crystallize during plan review. The skill updates decision records inline while walking through design questions and resolving trade-offs against the codebase.

Can I use this approach for repositories without existing ADR documentation?

This approach works best with repositories containing glossary and ADR documentation, as it relies on documented decisions and domain language to challenge plans. Without existing documentation, the reconciliation and interrogation features have limited context for surfacing contradictions.

Why does my architecture review miss hidden trade-offs in proposed plans?

Architecture reviews miss hidden trade-offs when plans are not stress-tested against existing codebase structure and documented decisions. Interrogating the design question by question resolves ambiguities and exposes contradictions early before implementation begins.

Does plan interrogation work for new workflow introductions in an existing project?

Plan interrogation works for new workflows by ensuring terminology matches existing concepts and durable decisions are recorded properly. The skill walks through the proposed workflow step by step, asking clarifying questions resolved from the implementation.