grill-with-docs

Challenge project plans to align domain language and update CONTEXT.md and ADRs.

1|Updated May 20, 2025
One-click install
npx skills add https://github.com/vessux/dotfiles --skill grill-with-docs-vessux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/vessux/dotfiles/tree/main/umbel/skills/pocock/grill-with-docs
Command: npx skills add https://github.com/vessux/dotfiles --skill grill-with-docs-vessux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating plan decisions with the project's language and keeping the documentation in sync can be slow and error-prone. This Skill runs a guided grilling session to surface ambiguities, align vocabulary, and update CONTEXT.md and ADRs as decisions crystallize.

Core Features & Use Cases

  • Relentless, question-driven iteration to surface assumptions about goals, scope, and terminology.
  • Inline updates to CONTEXT.md and ADRs as decisions emerge, ensuring living documentation stays aligned with the plan.
  • Optional codebase exploration to verify decisions against actual implementation.

Quick Start

Start the grilling session and begin iterating on your plan while the assistant updates CONTEXT.md and ADRs 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 keep CONTEXT.md and ADRs aligned with project decisions?

To keep CONTEXT.md and ADRs aligned, you can run a guided grilling session that surfaces ambiguities in your plan and performs inline updates to documentation as decisions crystallize.

What is an interactive grilling session for project documentation?

An interactive grilling session relentlessly questions project goals and terminology step-by-step to align domain language, updating living documentation like CONTEXT.md as decisions emerge.

How do I surface hidden assumptions in domain language during design sessions?

Surface hidden assumptions in domain language by applying relentless question-driven iteration during early design sessions, challenging scope and terminology one question at a time.

Can I verify documentation decisions against the actual codebase?

Yes, you can verify documentation decisions against the actual codebase through optional codebase exploration, ensuring your CONTEXT.md and ADRs match the real implementation.

Does this approach require manual updates to ADRs after planning?

No, this approach performs inline updates to ADRs during the grilling session, ensuring living documentation stays synchronized with the plan as decisions crystallize without manual post-processing.