grill-with-docs

Runs a structured interview session that sharpens plans and produces glossary and ADR documentation.

3|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/MaxWolf-01/agents --skill grill-with-docs-maxwolf-01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/MaxWolf-01/agents/tree/main/mx/skills/grill-with-docs
Command: npx skills add https://github.com/MaxWolf-01/agents --skill grill-with-docs-maxwolf-01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans, feature ideas, and external inputs like meeting transcripts or client briefs often contain hidden assumptions and gaps that only surface during implementation. This Skill runs a relentless interview-style session to stress-test an idea before building, while capturing the outcomes as durable documentation. ## Core Features & Use Cases - Plan Sharpening: Interrogates a plan or design through a grilling session to expose weak assumptions and unresolved questions. - Documentation as a Byproduct: Creates a glossary and Architecture Decision Records (ADRs) as the session progresses. - External Input Processing: Works through meeting transcripts, client briefs, or bug reports before any code is written. - Use Case: Paste a client brief into the session and let the interview challenge each requirement, ending with a refined plan plus ADRs documenting the decisions made. ## Quick Start Ask the agent to grill your feature plan or design document and generate glossary and ADR docs from the discussion.

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 feature plan before writing code?

Run a grilling session on the plan, which interrogates each assumption through structured questioning. The session exposes gaps and records the resolved decisions as ADRs and glossary entries.

What documents does a grilling session produce?

The session produces a glossary of domain terms and Architecture Decision Records (ADRs) capturing the decisions made. These docs are created incrementally as the interview progresses.

Can I use this with meeting transcripts or client briefs?

Yes, the session accepts external inputs such as meeting transcripts, client briefs, and bug reports. It works through the content to clarify requirements before any building starts.

When should I not use an interview-style planning session?

Avoid it for trivial, well-understood changes where the overhead of documentation outweighs the benefit. It is designed for plans with ambiguity, multiple stakeholders, or architectural consequences.