skills.rest
carmonalab
carmonalabOFFICIAL
Explore all skills by this author →
Website𝕏@carmonationGitHub

grill-with-docs

Interrogates plans and designs while generating ADRs and glossary documentation.

1|Updated Mar 7, 2025
Search Tags:#planning#documentation#domain modeling#adr#glossary#interview#design review
One-click install
npx skills add https://github.com/carmonalab/ECODA_paper --skill grill-with-docs-carmonalab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/carmonalab/ECODA_paper/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/carmonalab/ECODA_paper --skill grill-with-docs-carmonalab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions, vague terminology, and unchallenged decisions that surface too late. This Skill runs a relentless structured interview to stress-test a plan while simultaneously capturing the outcomes as durable documentation. ## Core Features & Use Cases - Structured Interrogation: Invokes a grilling workflow that challenges assumptions, scope, and design decisions through persistent questioning. - Documentation as a Byproduct: Produces Architecture Decision Records (ADRs) and a domain glossary as the interview progresses, via a domain-modeling pass. - Use Case: Before starting implementation of a new service, run this Skill on your draft design to expose weak points and walk away with written ADRs and a shared vocabulary for the team. ## Quick Start Ask the assistant to grill my current plan or design and document the decisions and terminology as we go.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
How do I stress-test a software design before implementation?▼

Run a structured interrogation of the plan that challenges assumptions, scope, and trade-offs through persistent questioning. This Skill coordinates a grilling pass and a domain-modeling pass so weaknesses surface before coding begins.

How to generate ADRs from a design discussion?▼

Architecture Decision Records are created as a byproduct of the interview process. As each decision is questioned and resolved, the outcome is captured as an ADR alongside a growing domain glossary.

What documentation does a design review interview produce?▼

The process produces two artifacts: Architecture Decision Records recording resolved design decisions, and a glossary defining domain terminology established during the conversation.

When should I not use an interview-based design review?▼

Avoid it for trivial changes with no architectural impact or when requirements are already fully specified and documented. The interview adds value when ambiguity, contested decisions, or undefined terminology exist.

Related Skills

Explore More Software Engineering Skills→
quaid-appquaid-app
3

architectural-proposals

Draft structured architectural proposals with problem statements, decisions, and risks.

Official
Advanced
cropsggcropsgg
15

domain-context

Standardize domain terminology across projects using CONTEXT.md and ADRs.

Community
Intermediate
K-Dense-AIK-Dense-AI
282

surveying-prior-work

Compile established methods and prior effect sizes to ground analysis planning.

Official
Advanced
farmountainfarmountain
1

PRD Generator Agent

Generate Product Requirements Documents with user stories and acceptance criteria.

Community
Advanced