grill-with-docs

Interrogate plans against domain language and update CONTEXT.md and ADRs.

1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/paialex/ai-skills-bank --skill grill-with-docs-paialex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/paialex/ai-skills-bank/tree/main/mattpocock_skills/engineering/grill-with-docs
Command: npx skills add https://github.com/paialex/ai-skills-bank --skill grill-with-docs-paialex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a guided grilling session to stress-test a plan against the project's domain language and existing documentation, updating CONTEXT.md and ADRs inline as decisions crystallize.

Core Features & Use Cases

  • Live questioning to challenge design decisions against existing domain terminology.
  • Inline documentation updates to CONTEXT.md and ADRs as decisions crystallize.
  • Context-aware session support across single-context repositories or CONTEXT-MAP.md structures.

Quick Start

To begin, run a grilling session against your repository to pressure-test your plan and capture inline documentation changes.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
How do I stress-test design decisions against my project's domain language?

You can stress-test design decisions by running a guided grilling session that interrogates your plan against domain terminology, identifying unresolved design issues and updating documentation inline as decisions crystallize.

Can I automatically update CONTEXT.md and ADRs while evaluating a plan?

Yes, the grilling session applies inline documentation updates to CONTEXT.md and ADRs as decisions crystallize, ensuring auditable changes to project context and architectural records during the evaluation.

Does this grilling approach work with multi-repository CONTEXT-MAP.md structures?

The grilling session supports both single-context repositories and CONTEXT-MAP.md structures, allowing context-aware evaluation across complex project documentation architectures.

What is the best way to capture auditable architectural decisions during a planning session?

The best way is to use a guided grilling session that interrogates your plan against existing domain language, producing ADR-friendly decisions with auditable changes directly applied to your context files.

When should I use a domain language grilling session for my design decisions?

Use a grilling session when you need to pressure-test a plan against existing domain terminology and documentation, capturing crystallized decisions as inline updates to CONTEXT.md and ADRs.

Are there prerequisites for running a documentation grilling session on my repository?

You need a repository with existing CONTEXT.md or CONTEXT-MAP.md files to apply the grilling session, which interrogates your plan against the project's domain language to resolve design decisions.