grill-with-docs

Validate plans against domain knowledge and update documentation in real-time.

1|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/JuanMS20/bundles-skills --skill grill-with-docs-juanms20
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/JuanMS20/bundles-skills/tree/main/skills/matt-pocock/grill-with-docs
Command: npx skills add https://github.com/JuanMS20/bundles-skills --skill grill-with-docs-juanms20

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a grilling session that challenges your plans against the existing domain model, enhances terminology clarity, and updates documentation (CONTEXT.md, ADRs) in real-time as decisions are made. It's used when a user needs to stress-test a plan against their project's language and documented decisions.

Core Features & Use Cases

  • Domain Model Validation: Test your plan against the existing domain model to ensure alignment.
  • Terminology Clarification: Enhance the clarity of technical terms and ensure consistency with project documentation.
  • Documentation Update: Dynamically update project documentation as decisions are crystallized.
  • Use Case: Imagine you're planning a new feature for a project. Use this Skill to validate your plan against the existing domain knowledge, refine your terminology, and update the project documentation in real-time.

Quick Start

Start a grill-with-docs session by providing your plan or design and asking questions about it.

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 my project plan against an existing domain model?

To validate a project plan against an existing domain model, you can run a grilling session that stress-tests your design using real-time analysis of your project documentation and domain-specific context. This ensures your plan aligns with documented decisions.

What is the best way to clarify technical terminology during project planning?

Clarifying technical terminology during project planning involves stress-testing your design against existing domain knowledge to enhance clarity and consistency. This process ensures your technical terms align dynamically with your project documentation.

Can I update project documentation like CONTEXT.md and ADRs in real-time?

Yes, you can update project documentation like CONTEXT.md and ADRs in real-time by running a grilling session that crystallizes decisions dynamically. This ensures your documentation reflects changes exactly as they are made.

Do I need existing project documentation to perform design validation?

Yes, design validation requires real-time analysis of existing project documentation and domain-specific context to function effectively. The validation process stresses your plans against this documented domain knowledge to ensure alignment.

When should I stress-test a feature plan against domain knowledge?

You should stress-test a feature plan against domain knowledge whenever you need to ensure alignment with your project's language and documented decisions before implementation. This is ideal during project planning and design validation phases.