skills.rest
rnaarla
rnaarlaCOMMUNITY
Explore all skills by this author →
GitHub

grill-with-docs

Validate project plans against CONTEXT.md and ADRs for terminology consistency.

Updated Apr 28, 2026
Search Tags:#documentation#ADR#alignment#decision-making#CONTEXT.md#domain-language#grill
One-click install
npx skills add https://github.com/rnaarla/agent_skills --skill grill-with-docs-rnaarla
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/rnaarla/agent_skills/tree/main/skills/engineering/grill-with-docs
Command: npx skills add https://github.com/rnaarla/agent_skills --skill grill-with-docs-rnaarla

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grill the project plan against the domain language and existing documentation to eliminate misalignment.

Core Features & Use Cases

  • Validate terminology against CONTEXT.md and ADRs to ensure consistency.
  • Update CONTEXT.md and ADRs inline as decisions crystallize and dependencies surface.
  • Surface terminology gaps and risks through iterative questioning.

Quick Start

Run a grilling session to validate this plan against your repository’s CONTEXT.md and ADRs.

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 project plans against existing documentation and domain language?▼

Validating project plans against domain language involves grilling the plan against existing CONTEXT.md and ADRs to eliminate misalignment. This process surfaces terminology gaps and risks through iterative questioning to ensure complete consistency.

What is the best way to keep CONTEXT.md and ADRs updated as project decisions evolve?▼

Keeping CONTEXT.md and ADRs updated requires updating them inline as decisions crystallize and dependencies surface. This ensures documentation accurately reflects the current project state and terminology throughout the lifecycle.

How do I identify terminology gaps in my software documentation?▼

Identifying terminology gaps in documentation requires iteratively questioning the project plan against established domain language. This surfaces misalignment between planned features and existing CONTEXT.md definitions or ADR decisions.

Do I need repository access to align project plans with ADRs?▼

Yes, aligning project plans with ADRs requires repository structure access and the ability to update CONTEXT.md and ADRs. This access is necessary to validate terminology and apply inline updates as decisions evolve.

When should I grill a project plan against domain language?▼

Grilling a project plan against domain language is necessary when eliminating misalignment between planned implementation and existing documentation. It is crucial for validating terminology and updating CONTEXT.md as decisions crystallize.

Related Skills

Explore More Software Engineering Skills→
JCE-Joshhh77JCE-Joshhh77
16

grill-with-docs

Validate planning proposals against local context and ADR files.

Community
Intermediate
u9401066u9401066

git-doc-updater

Update project documentation before Git commits with semantic versioning.

Community
Intermediate
dachentdachent
18

grill-with-docs-codex

Validate project plans against domain terminology, ADRs, and codebase context.

Community
Intermediate
arthur-debertarthur-debert

grill-me-with-docs

Challenge plans against CONTEXT.md, ADRs, and spec documents.

Community
Advanced