grill-with-docs

Interrogate project plans against domain models and update CONTEXT.md and ADRs.

16|Updated Jun 6, 2026

Search Tags:#documentation #context #adr #decision-making #terminology #domain-model

Ready to run

npx skills add https://github.com/Insik-Han/han-monorepo-template --skill grill-with-docs-insik-han

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/Insik-Han/han-monorepo-template/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/Insik-Han/han-monorepo-template --skill grill-with-docs-insik-han

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.

Core Features & Use Cases

Interactive questioning guides a step-by-step interrogation of design decisions with immediate feedback.
Documentation alignment updates CONTEXT.md and ADRs inline as decisions crystallise.
Knowledge consolidation strengthens shared terminology and reduces onboarding friction.

Quick Start

Use grill-with-docs to stress-test an plan against the repository's domain language and update guidelines as decisions crystallise.

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 an architectural plan against my domain model?▼

You can stress-test plans by engaging in an interactive question-by-question dialogue that interrogates your design decisions against the domain model. As decisions crystallize, the session updates CONTEXT.md and ADRs inline to lock down terminology.

What is the best way to align project terminology with existing documentation?▼

The best way to align terminology is through an interactive grilling session that challenges your plan against the repository's domain language. It locks down design decisions and updates CONTEXT.md inline to reduce onboarding friction.

How do I update CONTEXT.md and ADRs while making design decisions?▼

You can update CONTEXT.md and ADRs by running an interactive interrogation of your design decisions. As decisions crystallize, the tool applies inline updates to your documentation to ensure alignment with the domain model.

When do I need to write an Architecture Decision Record for terminology alignment?▼

You need an ADR when you must lock down project design decisions and align terminology with the domain model. Capturing decisions in ADRs consolidates shared knowledge and reduces onboarding friction for the team.

Can I use interactive questioning to explore dependencies in my codebase?▼

Yes, you can use interactive questioning to optionally explore your codebase when resolving branching questions and dependencies. It interrogates your current plan against the domain model to clarify and lock down design decisions.

Why does my project plan diverge from the established domain model?▼

Your plan diverges when design decisions lack alignment with the established domain model and terminology. An interactive grilling session stress-tests the plan against existing documentation to identify gaps and lock down decisions.