skills.rest
kileroppo
kileroppoCOMMUNITY
Explore all skills by this author →
GitHub

grill-with-docs

Stress-test development plans against project glossaries and architectural decisions.

Updated Aug 27, 2026
Search Tags:#documentation#glossary#design review#ADR#domain model#requirements clarification#codebase alignment
One-click install
npx skills add https://github.com/kileroppo/AI-Coding-Guidance-Skills --skill grill-with-docs-kileroppo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/kileroppo/AI-Coding-Guidance-Skills/tree/main/skills/grill-with-docs
Command: npx skills add https://github.com/kileroppo/AI-Coding-Guidance-Skills --skill grill-with-docs-kileroppo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents misalignment between a proposed plan and your project's actual domain model and documented decisions by forcing terminology and assumptions into the open.

Core Features & Use Cases

  • Relentless domain interviews: Challenges every aspect of the plan until a shared understanding is reached, one question at a time.
  • Terminology sharpening against CONTEXT: Detects conflicts and resolves fuzzy or overloaded terms into a precise canonical glossary.
  • Inline documentation updates: Updates CONTEXT.md as terms become resolved, and offers ADRs sparingly when there is a meaningful, hard-to-reverse trade-off.

Quick Start

Ask the AI to stress-test your plan by grilling it against your project's existing CONTEXT.md and ADRs until the plan matches your documented domain language.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
How do I check if my development plan conflicts with existing domain models and architectural decisions?▼

You can stress-test your plan by challenging terminology and assumptions against existing domain models and architectural decisions through guided, one-question-at-a-time elicitation to resolve conflicts.

What is the best way to clarify fuzzy or overloaded domain terminology during a design review?▼

The best way to clarify fuzzy domain terminology during a design review is to detect conflicts and sharpen overloaded terms into a precise canonical glossary, updating CONTEXT.md inline as terms become resolved.

How do I generate an ADR from requirements clarification without over-documenting?▼

Generate an ADR sparingly during requirements clarification only when a meaningful, hard-to-reverse trade-off is identified, ensuring architectural decisions are documented without excessive overhead.

When do I need to cross-reference my codebase during domain language alignment?▼

You need to cross-reference your codebase during domain language alignment when terminology conflicts, unclear boundaries, or questionable assumptions must be resolved to ensure complete alignment.

Does requirements discovery work without an existing project glossary?▼

Requirements discovery functions best with an existing project glossary, as the process relies on stress-testing a proposed plan against recorded architectural decisions and documented domain language to reveal misalignment.

Related Skills

Explore More Software Engineering Skills→
acme-skunkworksacme-skunkworks

grill-with-docs

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

Official
Intermediate
DektoraDektora

analyze-module-depth

Analyze module depth to identify shallow modules and refactoring opportunities.

Official
Advanced
mmartinsolivmmartinsoliv

grill-with-docs

Challenge plans against existing domain documentation and terminology.

Community
Advanced
samjhechtsamjhecht
4

brainstorming

Convert rough ideas into validated designs through structured questioning and documentation.

Community
Basic