grill-with-docs

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

83|9|Updated May 6, 2026
One-click install
npx skills add https://github.com/compozy/skeeper --skill grill-with-docs-compozy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/compozy/skeeper/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/compozy/skeeper --skill grill-with-docs-compozy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams align plans with their domain model by relentlessly challenging proposed designs against existing terminology and documented decisions, then inline-updating CONTEXT.md and ADRs as decisions crystallize.

Core Features & Use Cases

  • Interactive domain-driven critique that surfaces ambiguities and aligns terminology.
  • Live updates to CONTEXT.md and ADRs as decisions are made so documentation stays auditable.
  • Suitable for design sessions, architecture reviews, and policy-definition sprints where language and decisions evolve.

Quick Start

Start a grilling session by asking domain-alignment questions and update CONTEXT.md and ADRs as decisions crystallize.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
How do I align a proposed software design with existing domain documentation?

To align a software design with domain documentation, this Skill challenges proposed plans against the existing domain model to surface ambiguities, sharpen terminology, and inline-update CONTEXT.md and ADRs as decisions are made.

What is domain-driven design refinement for architecture reviews?

Domain-driven refinement is an interactive critique process that surfaces ambiguities and aligns terminology by challenging proposed designs against the existing domain model, ensuring language and decisions evolve consistently during architecture reviews.

How do I update CONTEXT.md and ADRs during a design exploration session?

You update CONTEXT.md and ADRs during design exploration by running a grilling session that challenges your plan against the domain model, automatically inlining architectural decisions and terminology resolutions into the documentation as they crystallize.

Can I use domain model critique for policy-definition sprints?

Yes, you can use domain model critique for policy-definition sprints, as the interactive grilling process is suitable for any design session where language and decisions evolve, ensuring policies align with the existing domain terminology.

Do I need repository access to challenge plans against the domain model?

Yes, you need repository access to read existing documentation like CONTEXT.md, ADRs, and codebase files, and to update them inline as domain-alignment decisions crystallize during the interactive critique session.

When should I not use a domain-driven critique approach?

You should avoid domain-driven critique when your project lacks an existing domain model or documented decisions to challenge against, as the process requires existing CONTEXT.md and ADRs to function effectively.