grill-with-docs

Challenge software design plans against domain models and documented decisions.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/cchrisv/newtonSelector --skill grill-with-docs-cchrisv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/cchrisv/newtonSelector/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/cchrisv/newtonSelector --skill grill-with-docs-cchrisv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid poorly aligned technical decisions by challenging plans against existing domain language, architectural context, and documented decisions.

Core Features & Use Cases

  • Plan Interrogation: Systematically questions design choices one decision at a time while recommending answers and exploring trade-offs.
  • Domain Alignment: Identifies ambiguous terminology, checks concepts against project documentation, and sharpens shared language.
  • Documentation Updates: Captures resolved terminology in CONTEXT.md and records significant architectural decisions through ADRs when appropriate.

Quick Start

Use the grill-with-docs skill to review my implementation plan against the project's domain model and identify unresolved 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 my implementation plan against existing project documentation?

Validating implementation plans against project documentation involves systematically interrogating design choices, checking terminology against domain models, and identifying unresolved architectural decisions for trade-off analysis.

What is the best way to resolve ambiguous domain terminology during architecture planning?

Resolving ambiguous domain terminology during architecture planning requires iteratively questioning concepts, exploring the codebase, and capturing resolved definitions in a shared context document.

How do I write an ADR for a significant architectural decision?

Writing an ADR for a significant architectural decision involves challenging the proposed plan against existing documented trade-offs, then recording the resolved architectural alignment and decision rationale.

When should I update CONTEXT.md during a software design planning session?

Updating a context document during a software design planning session is necessary when terminology clarification resolves ambiguous concepts, ensuring the shared domain language reflects the latest architectural decisions.

Can I use this approach to review design plans without any existing domain models?

Reviewing design plans without existing domain models limits the approach, as the skill relies on checking concepts against project documentation to improve architectural alignment and resolve ambiguity through iterative questioning.

How does codebase exploration improve architectural alignment?

Codebase exploration improves architectural alignment by verifying that planned design choices match existing domain models and documented decisions, resolving ambiguity through concrete codebase context during planning.