grill-with-docs

Interviews users to sharpen plans while recording decisions as ADRs and glossary entries.

Updated May 5, 2026
One-click install
npx skills add https://github.com/josippapez/ai-setup --skill grill-with-docs-josippapez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/josippapez/ai-setup/tree/main/claude/plugins/orchestrate/skills/grill-with-docs
Command: npx skills add https://github.com/josippapez/ai-setup --skill grill-with-docs-josippapez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Complex multi-step builds often start with vague plans and unpinned terminology, leading to rework and misaligned implementations. This Skill stress-tests a plan through relentless questioning while capturing every settled decision as written documentation. ## Core Features & Use Cases - Relentless Interviewing: Drives a one-question-at-a-time grilling session via the orchestrate:grilling companion skill to expose gaps and ambiguities in a plan. - Live Domain Modeling: Records settled terms and architectural decisions immediately as glossary entries and ADRs via the orchestrate:domain-modeling skill. - Interleaved Workflow: Alternates between grilling and recording so documentation grows as decisions crystallise rather than being deferred to the end. - Use Case: Before starting a large feature build, invoke this Skill to harden the spec, pin down domain terminology, and produce ADRs that the implementation phase can rely on. ## Quick Start Ask the AI to grill you with docs on your plan for the new feature so the spec and domain model are hardened before building begins.

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 plan before starting a complex build?

Invoke this Skill to run a grilling interview that questions your plan one point at a time. As decisions settle, they are recorded as ADRs and glossary entries so the spec is hardened and documented before implementation begins.

What is the difference between grilling and grill-with-docs?

Use grilling when nothing needs to be written down and you only want the plan challenged. Use grill-with-docs when the domain model, terminology, and architectural decisions must be captured as ADRs and glossary entries during the interview.

When should I write ADRs during plan refinement?

Record an ADR the moment an architectural decision crystallises during the interview, not at the end. This Skill interleaves questioning with recording so no settled decision is lost or deferred.

Does grill-with-docs work as a standalone interview?

It is designed as the intake step of a tracked orchestration and invokes two companion skills, orchestrate:grilling and orchestrate:domain-modeling, via the Skill tool. Both companion skills must be available for it to function.

What outputs does a grilling-with-docs session produce?

The session produces a hardened specification plus written domain model artifacts: glossary entries for pinned terminology and Architecture Decision Records for settled architectural choices, created incrementally throughout the interview.