grill-with-docs

Interrogate technical designs and generate ADRs and project glossaries.

Updated Dec 17, 2025
One-click install
npx skills add https://github.com/Frantss/oxform --skill grill-with-docs-frantss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/Frantss/oxform/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/Frantss/oxform --skill grill-with-docs-frantss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the ambiguity and lack of clarity in early-stage technical designs or project plans by forcing a structured, critical review process.

Core Features & Use Cases

  • Critical Inquiry: Conducts a relentless interview to identify gaps, risks, and logical fallacies in your proposed architecture.
  • Documentation Generation: Automatically captures the output of the session into formal Architecture Decision Records (ADRs) and a project glossary.
  • Use Case: Use this when you have a draft design for a new feature and need to ensure all edge cases are covered before implementation begins.

Quick Start

Initiate the grill-with-docs skill to begin a critical review of the current system architecture proposal.

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 architecture designs and identify risks before implementation?

To review architecture designs effectively, you need a structured critical interrogation process that challenges assumptions and identifies potential failure points within the software development lifecycle. This ensures all edge cases are covered before implementation begins.

What is the best way to generate Architecture Decision Records (ADRs) from a design review?

Generating Architecture Decision Records (ADRs) from a design review is best achieved by capturing the output of a structured critical inquiry session. This formalizes the architectural decisions and identified trade-offs directly into project documentation.

How do you create a project glossary during the architectural design phase?

To create a project glossary during the architectural design phase, extract definitions and domain terms clarified during a structured technical interrogation. This captures the refined vocabulary as a direct output of the critical review process.

When do I need a critical review process for my software architecture proposal?

You need a critical review process for your software architecture proposal when you have a draft design for a new feature and must resolve ambiguity. It forces a rigorous questioning phase to ensure logical fallacies and gaps are addressed.

Does a structured technical interrogation help refine early-stage project plans?

Yes, a structured technical interrogation helps refine early-stage project plans by relentlessly interviewing the design to identify gaps, risks, and logical fallacies in your proposed architecture before development starts.

What to do to ensure edge cases are covered in a new feature design?

To ensure edge cases are covered in a new feature design, conduct a relentless critical inquiry that challenges assumptions within the draft proposal. This structured review identifies potential failure points before implementation begins.