skills.rest
Herxinsasa
HerxinsasaCOMMUNITY
Explore all skills by this author →
GitHub

grill-with-docs

Validate feature plans against project glossaries, ADRs, and codebase.

1|Updated Apr 22, 2026
Search Tags:#domain modeling#codebase analysis#plan validation#context documentation#terminology alignment#adr management#requirement review
One-click install
npx skills add https://github.com/Herxinsasa/Skills-Collector --skill grill-with-docs-herxinsasa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/Herxinsasa/Skills-Collector/tree/main/mattpocock-skills/skills/engineering/grill-with-docs
Command: npx skills add https://github.com/Herxinsasa/Skills-Collector --skill grill-with-docs-herxinsasa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of building features that are misaligned with your project's existing domain terminology, documented architectural decisions, and actual codebase implementation, preventing costly rework, team confusion, and inconsistent documentation.

Core Features & Use Cases

  • Plan Stress-Testing: Conducts structured Q&A sessions to challenge every aspect of your feature or architectural plan against existing project context and documented decisions.
  • Terminology Alignment: Detects and resolves vague, overloaded, or conflicting terminology by cross-referencing your plan with the project's CONTEXT.md glossary in real time.
  • Inline Documentation Updates: Automatically updates CONTEXT.md and creates Architecture Decision Records (ADRs) as decisions crystallize, ensuring documentation stays in sync with planning progress.
  • Use Case: For example, when designing a new order cancellation feature for an e-commerce platform, use this Skill to validate that your plan's definition of "cancellation" matches the existing glossary, check that your proposed flow aligns with existing ADRs about order processing, and capture any new architectural decisions as formal ADRs.

Quick Start

Use the grill-with-docs skill to walk through your new order cancellation feature plan, challenge any misaligned terminology against the project's existing glossary, validate your proposed flow against documented ADRs and the codebase, and update the project's CONTEXT.md and ADRs as you finalize decisions.

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 feature plans against existing domain terminology and ADRs?▼

To validate feature plans against domain terminology and ADRs, use structured Q&A sessions to cross-reference your plan with the project's CONTEXT.md glossary and documented architectural decisions in real time. This stress-testing detects misaligned terms and prevents inconsistent codebase implementation.

What is the best way to keep project documentation in sync during feature design?▼

The best way to keep documentation in sync during feature design is through inline documentation updates that automatically modify CONTEXT.md and create Architecture Decision Records as decisions crystallize. This ensures your project glossary and ADRs accurately reflect planning progress.

How does terminology alignment work when reviewing requirements for an existing codebase?▼

Terminology alignment works by detecting and resolving vague, overloaded, or conflicting terms during requirement review. It cross-references your planned features against the project's existing CONTEXT.md glossary to ensure domain model consistency and reduce downstream rework.

Can I use this for architectural decision-making on projects with existing documentation?▼

Yes, you can use this for architectural decision-making on projects with existing documentation. It applies to software development planning scenarios by enforcing real-time validation of proposed flows against documented ADRs and probing edge cases to ensure plan consistency.

Do I need a CONTEXT.md file to perform plan validation and domain model refinement?▼

Yes, a CONTEXT.md file is needed to perform plan validation and domain model refinement. The terminology alignment process relies on cross-referencing your feature plans against this existing project glossary to detect and resolve any conflicting domain terms.

Related Skills

Explore More Software Engineering Skills→
roerohanroerohan
27

grill-with-docs

Validate implementation plans against project domain models and architectural decisions.

Community
Intermediate
a35506322a35506322

grill-with-docs

Stress-test project plans against domain documentation, codebase, and ADRs.

Community
Intermediate
rexshihaorenrexshihaoren
5

improve-codebase-architecture

Scan domain glossaries, ADRs, and CONTEXT.md to surface architectural deepening opportunities.

Community
Advanced
Zoomma1Zoomma1
3

grill-with-docs

Validate project plans against the domain model and update documentation inline.

Community
Advanced