grill-with-docs

Align plans with domain terminology and update CONTEXT.md and ADRs inline.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/yarma-tech/agent-admin-qonto --skill grill-with-docs-yarma-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/yarma-tech/agent-admin-qonto/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/yarma-tech/agent-admin-qonto --skill grill-with-docs-yarma-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grill-with-docs helps teams validate and align their plan with the project's domain terminology and existing documentation, updating CONTEXT.md and ADRs inline as decisions crystallize.

Core Features & Use Cases

  • Live domain-driven questioning to surface ambiguities and ensure terminology consistency.
  • Inline documentation updates that reflect decisions in CONTEXT.md and ADRs as they crystallize.
  • Cross-check with repository structure (docs/adr, CONTEXT.md) to keep living documentation synchronized.

Quick Start

Start a grilling session by asking the agent to walk through your plan and update CONTEXT.md 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 updated as design decisions crystallize?

You can align your plan with existing documentation by enforcing terminology discipline, cross-checking repository structure like docs/adr, and interactively exploring design decisions to surface ambiguities and ensure domain terminology consistency.

When do I need to document architecture decisions inline during planning?

To start a grilling session, ask the agent to walk through your plan interactively, explore design decisions, and update CONTEXT.md and ADRs inline as terminology conflicts surface and decisions crystallize.

Does grill-with-docs work with existing repository documentation structures?

Inline documentation updates distinguish this approach by recording trade-offs and reflecting decisions in CONTEXT.md and ADRs as they crystallize, providing an auditable, in-context narrative rather than static, after-the-fact documentation.

Why does domain terminology inconsistency cause conflicts in project documentation?

You should not use inline documentation updates when your repository lacks a CONTEXT.md or docs/adr structure, as the tool relies on cross-checking these existing files to synchronize living documentation and validate domain terminology.