skills.rest
hareki
harekiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

grill-with-docs

Runs a structured interview session that challenges plans and produces ADRs and glossary documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions, vague terminology, and unexamined trade-offs that surface too late. This Skill stress-tests a plan through a relentless question-driven interview while capturing the outcomes as durable documentation. ## Core Features & Use Cases - Adversarial Plan Review: Runs a grilling session that probes weaknesses, assumptions, and edge cases in a plan or design. - Documentation as a Byproduct: Creates Architecture Decision Records (ADRs) and a glossary as the interview progresses, so decisions and terminology are captured in context. - Domain Modeling Integration: Delegates to the domain-modeling skill to structure concepts discovered during the session. - Use Case: Before committing to a new system design, run a grilling session to expose gaps in the proposal and walk away with ADRs and a shared glossary for the team. ## Quick Start Ask the assistant to run a grilling session on your current plan or design document and generate ADRs and a glossary 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 design plan with an AI interview?▼

Run a grilling session on your plan or design document. The skill asks probing questions to expose weak assumptions and edge cases, then records the outcomes as ADRs and a glossary as the conversation progresses.

What documentation does a grilling session produce?▼

The session produces Architecture Decision Records (ADRs) capturing key decisions and their rationale, plus a glossary defining domain terms. These documents are created incrementally during the interview rather than afterward.

What is an ADR and when should I write one?▼

An Architecture Decision Record documents a significant design decision, its context, and its consequences. Write one whenever a non-obvious trade-off is made, such as during a design review or grilling session.

Does grill-with-docs work on its own?▼

No, it depends on two other skills: the grilling skill for the interview flow and the domain-modeling skill for structuring concepts. Both 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 decisions are already finalized and documented. The interview format adds the most value for ambiguous, high-stakes designs with unresolved trade-offs.

Related Skills

Explore More Product & Management Skills→
Crispy13Crispy13

brainstorming

Clarify project goals and constraints through guided questioning, then propose design approaches with trade-offs.

Community
Intermediate
cropsggcropsgg
15

domain-context

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

Community
Intermediate
LowyShinLowyShin
33

phase-1-schema

Define project terminology, entities, and relationships into a shared glossary and domain model.

Community
Intermediate
thedotmackthedotmack
92.8k

what-the

Explain technical concepts using who, what, where, why, and when framing.

Community
Basic