grill-with-docs

Debate design decisions against CONTEXT.md and ADR documentation.

5|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/kenlck/skills --skill grill-with-docs-kenlck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/kenlck/skills/tree/main/ken-swe/skills/grill-with-docs
Command: npx skills add https://github.com/kenlck/skills --skill grill-with-docs-kenlck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams validate and align product plans with existing domain models and documentation by forcing structured, domain-aware conversation and inline updates to CONTEXT.md and ADRs.

Core Features & Use Cases

  • Domain-driven grilling: Challenge every design choice against the current domain model and docs to surface assumptions.
  • Inline documentation refinement: Update CONTEXT.md and ADRs in place as decisions crystallize.
  • Glossary sharpening: Clarify terminology to avoid ambiguity across contexts and teams.
  • Use Case: Start a session when planning a major architecture change to ensure decisions map to documented context and constraints.

Quick Start

Begin a grilling session against your repository's CONTEXT.md and ADRs to surface inconsistencies and capture inline updates automatically.

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 architecture plans against existing domain documentation?

To validate architecture plans against existing domain documentation, use a structured grilling process that challenges every design decision against your current domain model, surfacing hidden assumptions and terminology gaps.

What is domain-driven grilling for design decisions?

Domain-driven grilling is a process that stress-tests project plans by debating design choices against documented context, ensuring new decisions map to existing domain constraints and updating CONTEXT.md inline as decisions crystallize.

How do I keep ADRs and CONTEXT.md updated when plans change?

Keep ADRs and CONTEXT.md updated by enforcing inline documentation refinement during planning sessions, capturing decisions in place as they are finalized to maintain domain consistency across stakeholders.

Can I use this grilling process with multiple context files instead of a single CONTEXT.md?

Yes, the grilling process supports codebases with multiple contexts by using CONTEXT-MAP.md and ADRs to trace decisions and surface terminology gaps across different contexts and teams.

What is the best way to resolve terminology gaps across development teams?

The best way to resolve terminology gaps is to sharpen the project glossary during design debates, clarifying ambiguous terms directly within CONTEXT.md to enforce domain-consistent vocabulary across all stakeholders.

When do I need to stress-test plans against domain docs?

Stress-test plans against domain docs when planning a major architecture change, ensuring new design decisions align with the documented context and constraints before implementation begins.