One-click install
npx skills add https://github.com/ccomkhj/skills --skill grill-with-docs-ccomkhj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/ccomkhj/skills/tree/main/grill-with-docs
Command: npx skills add https://github.com/ccomkhj/skills --skill grill-with-docs-ccomkhj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents plans from drifting away from your project’s established domain language and documented decisions by forcing precise alignment with CONTEXT.md and ADRs.

Core Features & Use Cases

  • Relentless requirement clarification: Walks branch-by-branch through your design tree and asks one question at a time until assumptions and dependencies are resolved.
  • Glossary and terminology enforcement: Detects when your wording conflicts with CONTEXT.md and prompts you to reconcile meanings.
  • Inline documentation updates: Updates CONTEXT.md as terms become resolved, and offers ADR creation only when a real trade-off needs to be recorded.
  • Codebase cross-checking: Uses repo exploration to confirm whether the implementation matches the plan, surfacing contradictions.

Quick Start

Use grill-with-docs to stress-test your plan against your existing CONTEXT.md and ADRs, and expect it to ask one high-impact question at a time until the design is consistent with your documented domain.

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 engineering plan against a domain model in CONTEXT.md?

You can validate an engineering plan against a domain model by stress-testing it through sequential one-question-at-a-time interviews, checking your design tree for terminology conflicts and dependency resolution against your CONTEXT.md.

When should I create an ADR during a design review?

You should create an ADR during a design review only when a real trade-off is identified, specifically weighing reversal cost, surprise, and trade-off criteria, rather than documenting every minor decision.

How do I resolve glossary and terminology conflicts during requirements elicitation?

You resolve glossary conflicts during requirements elicitation by detecting wording mismatches against your documented domain language, prompting for reconciliation, and applying lazy inline updates to CONTEXT.md as terms become resolved.

Can I verify if my codebase matches a proposed product plan?

Yes, you can verify if your codebase matches a proposed product plan through codebase-first verification, which uses repo exploration to surface contradictions between the actual implementation and your proposed design.

How does walking a design tree improve documentation alignment?

Walking a design tree improves documentation alignment by forcing branch-by-branch requirement clarification, ensuring assumptions and dependencies are resolved before the design drifts away from established domain language and ADRs.