grill-with-docs-codex

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

18|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/dachent/skills --skill grill-with-docs-codex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs-codex
Source: https://github.com/dachent/skills/tree/main/grill-with-docs-codex
Command: npx skills add https://github.com/dachent/skills --skill grill-with-docs-codex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents architectural drift and terminology confusion by rigorously interviewing the user about their plans against the project's existing documentation, ADRs, and domain language.

Core Features & Use Cases

  • Terminology Alignment: Automatically identifies and resolves conflicts between user language and project-defined domain terms.
  • Architectural Guardrails: Enforces the creation of ADRs for significant decisions and ensures plans align with established architectural patterns.
  • Use Case: When starting a new feature, use this skill to ensure your proposed implementation respects existing bounded contexts and naming conventions defined in your CONTEXT.md files.

Quick Start

Use the grill-with-docs-codex skill to review my current plan for the new billing module integration.

Frequently Asked Questions about grill-with-docs-codex

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate project plans against existing domain terminology and ADRs?

Validating project plans against domain terminology and ADRs requires cross-referencing your proposed implementation with CONTEXT.md files. This skill facilitates interactive grilling sessions to identify terminology conflicts and enforce architectural documentation standards during development.

What is the best way to prevent architectural drift when starting a new feature?

Preventing architectural drift involves rigorously interviewing your plans against project documentation and established patterns. This skill acts as architectural guardrails by ensuring your proposed implementation respects existing bounded contexts and naming conventions defined in your documentation.

Do I need specific documentation files to perform architectural plan validation?

Yes, performing architectural plan validation requires access to project-level CONTEXT.md, CONTEXT-MAP.md, and docs/adr/ directories. These files provide the necessary codebase context and architectural decision records for comparative analysis during the grilling session.

How do I enforce documentation standards for significant architectural decisions?

Enforcing documentation standards for significant architectural decisions is achieved by requiring the creation of ADRs. This skill ensures plans align with established architectural patterns and automatically identifies conflicts between your language and project-defined domain terms.

Can I resolve terminology conflicts between my codebase and project documentation automatically?

Resolving terminology conflicts between your codebase and project documentation happens through interactive comparative analysis. The skill automatically identifies misalignments between user language and project-defined domain terms, facilitating sessions to correct these discrepancies.