grill-with-docs

Validate proposed plans against domain models and documented decisions.

Updated May 6, 2026

Search Tags:#architecture #code review #documentation #domain modeling #adr #glossary

Ready to run

npx skills add https://github.com/Takfes/indie-scaffolder --skill grill-with-docs-takfes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/Takfes/indie-scaffolder/tree/main/components/agent-skills-commands/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/Takfes/indie-scaffolder --skill grill-with-docs-takfes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams pressure-test a proposed plan against the codebase, the project's domain language, and existing architectural decisions before changes are made.

Core Features & Use Cases

Relentless guided interview: Asks one question at a time and recommends answers to uncover hidden assumptions and decision branches.
Glossary and decision alignment: Checks proposed terminology against existing CONTEXT.md definitions and surfaces conflicts immediately.
Documentation updates in place: Captures resolved terms in CONTEXT.md and records hard trade-off decisions as ADRs when they truly matter.
Use case: A product engineer wants to introduce a new workflow, and the Skill helps validate the plan, refine the language, and update project documentation without drifting into implementation detail.

Quick Start

Tell me the plan you want to stress-test, and I will interrogate it one question at a time while checking the repository's documentation for contradictions.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema

How do I stress-test a proposed architecture plan against existing domain models?▼

To stress-test a plan against domain models, use an incremental interview process that validates terminology and boundaries against your codebase, checking for contradictions before implementation begins.

What is the best way to align new code review terminology with existing documentation?▼

Aligning terminology during code review requires checking proposed terms against existing CONTEXT.md definitions, immediately surfacing conflicts, and capturing resolved language in your glossary to prevent semantic drift.

How do I record architectural trade-off decisions during a planning session?▼

Record architectural trade-offs by crystallizing hard decisions made during questioning into ADR files, ensuring significant design choices are formally documented inline as they emerge.

Can I use guided questioning to uncover hidden assumptions in a software design plan?▼

Yes, guided one-question-at-a-time interviewing uncovers hidden assumptions by recommending targeted answers and systematically exploring decision branches before any implementation work starts.

Does stress-testing documentation work without writing actual code?▼

Yes, validation focuses entirely on plans, domain language, and documented decisions, intentionally avoiding implementation detail to ensure boundaries and trade-offs are clarified first.