grill-with-docs

Validate proposed plans and update CONTEXT.md, ADRs, glossary inline.

15|2|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/Liuchun-oss/codelf-agent --skill grill-with-docs-liuchun-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/Liuchun-oss/codelf-agent/tree/main/resources/skills/grill-with-docs
Command: npx skills add https://github.com/Liuchun-oss/codelf-agent --skill grill-with-docs-liuchun-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This section describes the need to stress-test a plan against a project's domain language and existing documentation, reducing misalignment between strategy and a team's established terminology.

Core Features & Use Cases

  • Validate plans against CONTEXT.md and ADRs, prompting inline updates as decisions solidify.
  • Ensure glossary alignment and terminology consistency across the repository as decisions evolve.
  • Provide structured prompts to update documentation with rationale and outcomes in real time.

Quick Start

Align your plan with the project's domain language by grilling the plan and updating 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 validate a project plan against existing domain documentation?

Validating a plan against domain documentation requires grilling the proposed strategy against CONTEXT.md and ADRs to surface gaps. This process cross-references your plan with established project terminology to resolve ambiguities and ensure alignment.

What is documentation grilling for architecture decisions?

Documentation grilling is a stress-testing process that interrogates a proposed plan against your domain model. It surfaces misalignments between strategy and established terminology, prompting structured updates to ADRs and glossaries as decisions crystallize.

How do I keep CONTEXT.md and ADRs in sync with code changes?

Keeping CONTEXT.md and ADRs in sync involves applying a grilling process to your plan that prompts inline documentation updates. As architectural decisions solidify, the Skill provides structured recommendations to update project documents with rationale.

Can I maintain glossary consistency when evolving project terminology?

You can maintain glossary consistency by grilling your plan against the existing domain language. This surfaces terminology gaps and prompts inline glossary updates as decisions evolve, ensuring terminology consistency across the repository.

What's the best way to ensure traceable decision-making for architecture updates?

Ensuring traceable decision-making requires prompting for direct updates to project documents with rationale and outcomes. The grilling process provides structured recommendations until your plan achieves alignment with the domain model.