grill-with-docs

Validate feature plans against CONTEXT.md terminology and create ADR documents.

10|2|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/sumpalabs/petrodb --skill grill-with-docs-sumpalabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/sumpalabs/petrodb/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/sumpalabs/petrodb --skill grill-with-docs-sumpalabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of building features that conflict with your project's existing domain terminology, documented architectural decisions, or unstated domain constraints, which often leads to costly rework and team misalignment.

Core Features & Use Cases

  • Terminology Validation: Challenges your plan against the existing glossary in CONTEXT.md to catch mismatched or overloaded terms immediately.
  • Edge Case Probing: Asks targeted questions about domain relationships and boundaries to force precise definition of concept behavior.
  • Inline Documentation Updates: Updates CONTEXT.md and creates ADRs in real time as decisions are finalized, keeping project documentation in sync with planning.
  • Use Case: For example, if you are designing a new order cancellation feature, the Skill will flag if you use "cancel" in a way that conflicts with the existing glossary definition, ask about partial vs full cancellation edge cases, and create an ADR if the chosen approach is hard to reverse and involves a meaningful trade-off.

Quick Start

Use the grill-with-docs skill to walk through your proposed new feature plan, answering questions about domain term definitions and decision trade-offs as they arise.

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

Domain modeling validation challenges proposed feature plans against existing domain terminology and documented architectural decisions. It applies context mapping to enforce consistency between planned changes and project documentation, reducing rework from terminology conflicts.

When do I need to create an ADR for architectural trade-offs during software planning?

ADR creation is needed when a chosen design approach is hard to reverse and involves a meaningful architectural trade-off. Capturing non-obvious decision rationale during planning sessions creates auditable records of these trade-offs.

How does edge case probing work for domain relationships and boundaries?

Edge case probing asks targeted questions about domain relationships and boundaries to force precise definition of concept behavior. It ensures partial versus full scenario behaviors are explicitly defined during the software development planning process.

Can I update CONTEXT.md and generate ADRs in real time during planning sessions?

Inline documentation updates apply to CONTEXT.md and ADR creation in real time as decisions are finalized. This keeps project documentation perfectly in sync with the planning outcomes without requiring manual post-meeting updates.

What is the best way to resolve ambiguous terminology conflicts before implementation?

Resolving ambiguous terminology conflicts requires stress-testing plans against established project context and decisions. Plan validation eliminates misalignment by resolving overloaded terms and capturing unstated domain constraints before development begins.