grill-with-domain-modeling

Name: grill-with-domain-modeling
Availability: InStock
Author: chichex

Conduct structured interviews to synchronize architectural decision records with domain modeling.

2|Updated Jul 13, 2026

Search Tags:#planning #architecture #documentation #adr #domain-modeling #grill

Ready to run

npx skills add https://github.com/chichex/skills --skill grill-with-domain-modeling

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grill-with-domain-modeling
Source: https://github.com/chichex/skills/tree/main/claude/grill-with-domain-modeling
Command: npx skills add https://github.com/chichex/skills --skill grill-with-domain-modeling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the fragmentation between high-level planning and technical documentation by ensuring that domain knowledge, glossaries, and architectural decisions are captured simultaneously during the planning phase.

Core Features & Use Cases

Integrated Documentation: Automatically maintains CONTEXT.md and ADRs as decisions are made during a grill session.
Structured Decision Making: Enforces a strict separation between plan confirmation and ADR creation to prevent cognitive overload and ensure clarity.
Use Case: Use this when starting a complex feature to ensure that every architectural choice is documented as an ADR and the domain glossary is updated before a single line of code is written.

Quick Start

Invoke the grill-with-domain-modeling skill to begin a structured planning session that captures domain documentation and architectural decisions.

Frequently Asked Questions about grill-with-domain-modeling

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

FAQPage Schema

How do I document architectural decisions while planning a complex feature?▼

To document architectural decisions during planning, you can use a structured interview process that synchronizes domain modeling with ADR creation. This approach enforces strict separation between plan confirmation and formal documentation to prevent cognitive overload and ensure clarity.

What is the best way to maintain a domain glossary and ADRs simultaneously?▼

The best way to maintain a domain glossary and ADRs simultaneously is through an integrated planning session that automatically captures CONTEXT.md and architectural decisions as they are made, eliminating fragmentation between high-level planning and technical documentation.

When do I need to create architectural decision records before writing code?▼

You need to create architectural decision records before writing code when starting a complex feature that requires rigorous planning, ensuring domain knowledge and glossaries are captured and validated upfront.

Can I validate technical plans and generate documentation artifacts at the same time?▼

Yes, you can validate technical plans and generate documentation artifacts simultaneously by conducting a structured grill session that enforces creation of ADRs and glossaries, where plan confirmation strictly precedes formalization of architectural decisions.

Why does separating plan confirmation from ADR creation matter?▼

Separating plan confirmation from ADR creation matters because it prevents cognitive overload and ensures clarity by enforcing a strict sequential workflow where technical plans are fully validated before formal architectural decisions are documented.

Does this domain modeling approach work without external dependencies or components?▼

Yes, this domain modeling approach works without external dependencies, operating as a standalone structured planning session that facilitates interviews, validates plans, and enforces documentation artifact creation through its own internal workflow.