grill-with-docs

Validate project plans against domain models and update documentation inline.

4|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/AshenDulsanka/agent-arche --skill grill-with-docs-ashendulsanka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/AshenDulsanka/agent-arche/tree/main/skills/grill-with-docs
Command: npx skills add https://github.com/AshenDulsanka/agent-arche --skill grill-with-docs-ashendulsanka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill facilitates a rigorous evaluation of project plans against existing domain models, enhances terminology precision, and maintains up-to-date documentation, fostering a robust codebase foundation.

Core Features & Use Cases

  • Domain Model Validation: Assess and validate project plans in alignment with established domain models.
  • Terminology Refinement: Ensure consistent and precise use of terminology within the project.
  • Documentation Updates: Automatically update documentation like CONTEXT.md and ADRs inline as decisions are made.
  • Use Case: Imagine you are implementing a new feature and want to ensure it aligns with the existing architecture. Use this Skill to challenge your design decisions and documentation against the existing codebase and models.

Quick Start

Start a grilling session with the 'grill-with-docs' skill by initiating the discussion on your plan's specifics.

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 new feature plan against an existing domain model?

To validate a feature plan against a domain model, engage in a deep Q&A grilling session that challenges design decisions and aligns terminology directly with your established codebase architecture.

What is the best way to maintain accurate inline documentation during project development?

The best way to maintain inline documentation is to update files like CONTEXT.md and ADRs automatically during a Q&A session, ensuring documentation reflects decisions as they are made.

How do I ensure consistent terminology across my software project codebase?

To ensure consistent terminology, use a grilling session to refine and standardize terms against your existing domain models, verifying that inline documentation matches the established vocabulary.

Can I use domain model validation if my project lacks established documentation?

No, this domain model validation requires a project codebase with documentation already in place to challenge plans, align terminology, and update inline docs like ADRs effectively.

When do I need to challenge project plans against established architecture?

You need to challenge project plans when implementing new features, ensuring design decisions and terminology align with the existing domain model before proceeding with codebase updates.