skills.rest
alex-jordan547
alex-jordan547COMMUNITY
Explore all skills by this author →
GitHub

grill-with-docs

Runs a structured interview to sharpen plans while generating ADRs and a glossary.

Updated Jul 3, 2026
Search Tags:#planning#documentation#domain modeling#adr#glossary#interview#design review
One-click install
npx skills add https://github.com/alex-jordan547/agent-setup --skill grill-with-docs-alex-jordan547
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/alex-jordan547/agent-setup/tree/main/archive/grill-with-docs
Command: npx skills add https://github.com/alex-jordan547/agent-setup --skill grill-with-docs-alex-jordan547

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions, vague terminology, and unchallenged decisions. This Skill runs a relentless interview that pressure-tests a plan or design while capturing the outcomes as durable documentation. ## Core Features & Use Cases - Relentless Interview: Runs a grilling session that challenges assumptions and forces explicit decisions about the plan or design. - Documentation as Output: Creates Architecture Decision Records (ADRs) and a glossary as the interview progresses, so decisions and terminology are captured in writing. - Domain Modeling Integration: Delegates the questioning approach to the domain-modeling skill for structured exploration of the problem space. - Use Case: Before implementing a new feature, run this Skill to interrogate the design, record each decision as an ADR, and build a shared glossary of domain terms for the team. ## Quick Start Ask the agent to grill my current plan and document the decisions as ADRs and a glossary.

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 interview that challenges every assumption in the plan. This Skill grills the design through targeted questions and records each resolved decision as an Architecture Decision Record.

How to create ADRs during a design review session?▼

The Skill generates Architecture Decision Records as the interview progresses, capturing each decision and its rationale in real time rather than writing them afterward from memory.

What is a domain glossary and why create one?▼

A glossary defines the shared vocabulary of a problem domain so all stakeholders use terms consistently. This Skill builds one automatically as ambiguous terms surface during the interview.

Does this Skill work without the domain-modeling skill installed?▼

No, it explicitly delegates the questioning to the domain-modeling skill, so that skill must be available for the session to run as intended.

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 assumptions and terminology are still unresolved.

Related Skills

Explore More Software Engineering Skills→
webinywebiny
8.0k

grill-me

Interviews the user question-by-question to stress-test plans and resolve design decisions.

Official
Basic
anavvanzinanavvanzin

agency-senior-project-manager

Convert site specifications into structured development task lists with acceptance criteria.

Community
Advanced
contentbugvideoeditingcontentbugvideoediting

architecture-decision-records

Capture architectural decisions as structured ADR documents under docs/adr.

Community
Advanced
lucas-ferrari-correalucas-ferrari-correa

new-rfc

Guide structured RFC interviews to generate formal RFC documents.

Community
Advanced