grill-with-docs

Stress-test project plans against CONTEXT.md and ADR documentation.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/remiconnesson/nuxt-minimal-starter-v0-template --skill grill-with-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/remiconnesson/nuxt-minimal-starter-v0-template/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/remiconnesson/nuxt-minimal-starter-v0-template --skill grill-with-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grilling sessions help teams validate and sharpen domain language and decisions by challenging plans against existing documentation and updating docs inline as decisions crystallize.

Core Features & Use Cases

  • Relentless questioning to surface assumptions
  • On-the-fly CONTEXT.md and ADR updates
  • Works with single-context or multi-context repos, and aligns terminology with domain experts

Quick Start

Initiate a grilling session on your repo to stress-test your plan against CONTEXT.md and ADRs, then update the documentation 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 stress-test project plans against existing documentation?

To stress-test project plans against documentation, the Skill simulates decision-making through relentless questioning to surface assumptions, then updates CONTEXT.md and ADRs inline as decisions crystallize during a sequential grilling conversation.

What is a grilling session for domain documentation?

A grilling session for domain documentation is a conversational process that validates and sharpens domain language by challenging plans against existing CONTEXT.md files and ADRs, converging on shared terminology through systematic sequential questioning.

Do I need an existing repository structure to validate decisions with ADRs?

Yes, validating decisions with ADRs requires an actively documented repository structure containing CONTEXT.md or CONTEXT-MAP.md and ADRs, supporting both single-context and multi-context repos to align terminology with domain experts.

How do I update CONTEXT.md and ADRs inline during a planning conversation?

You update CONTEXT.md and ADRs inline by engaging in a sequential questioning process that revises decisions in real time as the conversation unfolds, automatically applying changes to the documentation when decisions crystallize.

Can I use this documentation grilling approach with a multi-context repo?

Yes, documentation grilling works with multi-context repos by utilizing CONTEXT-MAP.md to navigate multiple contexts, aligning terminology across different domain areas while systematically questioning and updating decisions inline.