grill-with-docs

Interrogate project plans and architectural designs to identify structural weaknesses.

Updated May 3, 2026
One-click install
npx skills add https://github.com/skogai/marketplace --skill grill-with-docs-skogai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/skogai/marketplace/tree/main/skogai-core/skills/grill-with-docs
Command: npx skills add https://github.com/skogai/marketplace --skill grill-with-docs-skogai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of critical review in early-stage design and planning, ensuring that ideas are stress-tested before implementation.

Core Features & Use Cases

  • Critical Design Review: Conducts a structured, relentless interview to identify gaps in logic or architecture.
  • Automated Documentation: Simultaneously generates essential project artifacts like Architecture Decision Records (ADRs) and glossaries during the session.
  • Use Case: Use this during the initial phase of a new feature to ensure all edge cases are considered and that your technical documentation is kept in sync with your evolving design.

Quick Start

Initiate a design review session by asking the assistant to grill the current project plan and document the findings.

Frequently Asked Questions about grill-with-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review an architectural design to find structural weaknesses before implementation?

Review an architectural design by conducting an interactive, logic-based interrogation of project plans to identify gaps and structural weaknesses. This critical design review stress-tests early-stage ideas through rigorous questioning before committing to implementation.

How do I generate Architecture Decision Records during the design phase?

Generate Architecture Decision Records (ADRs) by running an interactive design review session that simultaneously captures essential project artifacts. The session documents key decisions and creates glossaries while interrogating your evolving architecture.

What is the best way to ensure technical documentation stays in sync with an evolving project plan?

To keep technical documentation in sync, use a design review session that generates ADRs and glossaries concurrently with the planning process. This ensures edge cases are considered and artifacts match the evolving design.

When do I need a critical design review in the software development lifecycle?

You need a critical design review during the initial phase of a new feature to ensure all edge cases are considered. It addresses the lack of stress-testing in early-stage planning by identifying logic and architecture gaps before implementation begins.

Does the design review process require specific domain modeling terminology to work effectively?

The design review leverages domain modeling techniques to ensure comprehensive coverage of technical requirements and project terminology. It interrogates your domain language to validate that architectural designs account for all necessary concepts.

Can I use this design interrogation approach for existing project plans or only new features?

You can use this logic-based interrogation on existing project plans to identify structural weaknesses and document findings. While best applied during the initial phase of a new feature, it also stress-tests and documents decisions for evolving designs.