grill-with-docs

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

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill grill-with-docs-sevwren
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/SevWren/Daily-Motivation-Brain-Helper/tree/main/CLAUDE/skills/engineering/grill-with-docs
Command: npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill grill-with-docs-sevwren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions, vague terms, and unchallenged decisions. This Skill stress-tests a plan through a relentless question-and-answer interview while capturing the outcomes as durable documentation. ## Core Features & Use Cases - Socratic Plan Review: Runs a grilling session that probes weaknesses, ambiguities, and unstated assumptions in a plan or design. - Documentation as a Byproduct: Produces Architecture Decision Records (ADRs) and a domain glossary as the interview progresses. - Domain Modeling Integration: Delegates to the domain-modeling skill to structure concepts discovered during the session. - Use Case: Before implementing a new feature, run a grilling session on your design proposal to surface edge cases and record each decision as an ADR with a shared glossary of terms. ## Quick Start Ask the assistant to grill my current design 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 grilling session that interviews you about your plan, probing assumptions, edge cases, and unstated decisions. Each resolved question is captured as an Architecture Decision Record so the reasoning is preserved.

What is an Architecture Decision Record and how is it created?▼

An ADR is a short document capturing a single architectural decision and its rationale. This Skill generates ADRs automatically as decisions are made during the interview, alongside a glossary of domain terms.

Can I use this for non-software plans?▼

The interview format works for any plan or design that benefits from rigorous questioning, but the outputs are oriented toward software engineering artifacts like ADRs and domain glossaries.

What are the limitations of an interview-based design review?▼

The quality of the review depends on the answers you provide; it cannot verify technical feasibility or run code. It complements, but does not replace, prototyping or empirical testing.