grill-with-docs

Validate technical proposals against project documentation and ADRs.

3|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/XinAloha/skills --skill grill-with-docs-xinaloha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/XinAloha/skills/tree/main/methodology/grill-with-docs
Command: npx skills add https://github.com/XinAloha/skills --skill grill-with-docs-xinaloha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the gap between high-level architectural decisions and actual implementation by forcing a rigorous, document-driven review of proposed changes.

Core Features & Use Cases

  • Context-Aware Review: Validates proposals against existing ADRs (Architecture Decision Records) and project terminology.
  • Boundary Testing: Uses specific, edge-case scenarios to challenge the robustness of your technical logic.
  • Use Case: When proposing a new data source integration, the skill will cross-reference your plan with existing ADRs to ensure you aren't violating established architectural constraints or naming conventions.

Quick Start

Trigger the grill-with-docs skill to review your current architectural proposal against the existing ADRs and project context.

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 architectural designs against existing project documentation?

To validate architectural designs, you cross-reference technical proposals with existing ADRs and project terminology to ensure compliance with established architectural constraints and naming conventions.

What is an ADR review for technical proposals?

An ADR review for technical proposals is a document-driven validation process that pressure-tests new software designs against Architecture Decision Records to prevent violating established project boundaries.

How do I check if a new data source integration violates architectural constraints?

You check new data source integrations by applying context-aware boundary testing that cross-references the integration plan against existing ADRs to identify violations of established architectural constraints.

Can I use design review processes to manage technical debt?

Yes, you can use rigorous design review processes to manage technical debt by forcing document-driven validation that ensures new implementations align with high-level architectural decisions and established constraints.

When do I need document-driven consistency checks for software engineering workflows?

You need document-driven consistency checks when proposing architectural changes that require rigorous design review, ensuring domain-specific terminology adherence and architectural constraint verification.