skills.rest
wachawo
wachawoCOMMUNITY
Explore all skills by this author →
GitHub

grill-docs

Stress-test software design plans against domain models and architectural documentation.

Updated May 5, 2026
Search Tags:#architecture#documentation#refactoring#adr#domain-driven-design#code-review
One-click install
npx skills add https://github.com/wachawo/claude-skills --skill grill-docs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-docs
Source: https://github.com/wachawo/claude-skills/tree/main/skills/grill-docs
Command: npx skills add https://github.com/wachawo/claude-skills --skill grill-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents architectural drift and terminology confusion by forcing a rigorous, iterative review of your project plans against your existing domain model and documentation.

Core Features & Use Cases

  • Domain Stress-Testing: Interrogates your proposed changes to ensure they align with established architectural decisions and business logic.
  • Glossary Enforcement: Automatically flags ambiguous terminology and updates your CONTEXT.md to maintain a single source of truth.
  • Use Case: When proposing a new feature, use this skill to walk through edge cases and verify if the design requires a new ADR or conflicts with existing domain definitions.

Quick Start

Initiate the grill-docs skill to begin a structured interrogation of your current project plan and documentation.

Frequently Asked Questions about grill-docs

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

FAQPage Schema
How do I validate new feature plans against existing domain models and architecture documentation?▼

You can stress-test software design plans against existing domain models by running a guided, iterative interrogation that flags inconsistencies with established system boundaries. This enforces alignment with your current architecture and business logic.

What is the best way to prevent architectural drift when proposing code refactoring?▼

Preventing architectural drift during refactoring involves rigorously reviewing proposed changes against existing domain definitions. A structured interrogation checks if the refactoring conflicts with established constraints and verifies if a new ADR is required.

How do I maintain consistent project terminology across CONTEXT.md and ADR files?▼

Maintaining consistent project terminology requires flagging ambiguous definitions during design reviews and automatically updating your CONTEXT.md. This keeps a single source of truth across your architectural decision records and codebase.

When do I need to create a new ADR for a proposed software design change?▼

You need a new ADR when a proposed software design change conflicts with established domain definitions or system boundaries. Structured interrogation of the plan identifies edge cases that require formal architectural decisions.

Can I use domain-driven design stress-testing for iterative refinement of project terminology?▼

Domain-driven design stress-testing supports iterative refinement of project terminology through one-question-at-a-time interrogation. This guided process validates proposed changes against established domain models and architectural constraints.

Related Skills

Explore More Software Engineering Skills→
yash-gargyash-garg

domain-modeling

Resolve ambiguous domain terminology and record architectural decisions in CONTEXT.md and ADR formats.

Community
Intermediate
SatoryKonoSatoryKono
1

architecture-guardian

Identify architectural boundary violations in BioETL code and generate a compliance report.

Community
Advanced
TrogonStackTrogonStack
10

event-definition

Standardize event definition creation and review for event-driven architectures.

Official
Intermediate
tkerseytkersey
66

commit

Create small Git commits with validation signals before finalizing.

Community
Intermediate