grill-with-docs

Stress-test software plans against documented domain models and existing decisions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you validate a proposed approach against the project’s existing terminology, glossary, and recorded architectural decisions so you can reduce misalignment and accidental rework.

Core Features & Use Cases

  • Relentless plan interrogation: Walks branch-by-branch through the design tree, resolving dependencies between decisions one-by-one.
  • Terminology sharpening via CONTEXT.md: Detects conflicting terms, proposes canonical replacements, and updates the glossary inline as terms get resolved.
  • Decision recording with ADRs: Proposes ADRs only when the decision is hard to reverse, surprising without context, and a real trade-off.

Quick Start

Use the grill-with-docs skill to interview an AI about your plan, requiring the AI to cross-check the codebase and update CONTEXT.md and ADRs inline 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 validate a software design plan against existing domain terminology?

To validate a plan against domain terminology, conduct an interactive one-question-at-a-time interview that cross-references the codebase, detects glossary conflicts, and proposes canonical updates to CONTEXT.md.

When should I write an Architecture Decision Record during domain modeling?

Write an Architecture Decision Record during domain modeling only when a decision represents a real trade-off, is hard to reverse, and would be surprising without context, ensuring documentation remains focused and highly relevant.

What is the best way to align product requirements with a documented codebase?

Align product requirements with a documented codebase by stress-testing proposed approaches branch-by-branch, resolving decision dependencies iteratively to prevent accidental rework and terminology misalignment.

Can I perform architecture review and terminology validation across multi-context repositories?

Yes, you can perform architecture review and terminology validation across multi-context repositories, applying iterative domain modeling checks to ensure structural consistency and glossary alignment throughout the project.

How does immediate glossary conflict detection work during requirements discovery?

Immediate glossary conflict detection works by interrogating your plan interactively, identifying conflicting terms as they arise, and proposing canonical replacements directly within your CONTEXT.md file to maintain strict terminology alignment.