grill-with-docs

Guide one-question-at-a-time design interviews and record outcomes into CONTEXT.md and ADRs.

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/prestarius/jet-skills-stack --skill grill-with-docs-prestarius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/prestarius/jet-skills-stack/tree/main/skills/grill-with-docs
Command: npx skills add https://github.com/prestarius/jet-skills-stack --skill grill-with-docs-prestarius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interview the user one question at a time about a design, capturing the answers into CONTEXT.md and ADRs as you go. Use whenever the user is fleshing out a design and wants the decisions recorded inline, not just discussed.

Core Features & Use Cases

  • Read ./CONTEXT.md first if it exists, so you grill against what's already decided and use the project’s domain language.
  • Grill one sharp question at a time, recommending an answer each time (see grill-me). Go after the highest-leverage unknowns first.
  • Persist each outcome as it settles:
    • Ubiquitous language / conventions → update ./CONTEXT.md (add the term, the convention, the constraint). Don't let a newly-agreed term live only in the chat.
    • A real architectural decision → write an ADR via the adr skill (docs/adr/NNNN-*.md), with its context, the decision, consequences, and the alternatives that lost.
  • Confirm before writing to CONTEXT.md or creating an ADR — show what you're about to record.
  • Close out by listing the artifacts written (which CONTEXT.md sections changed, which ADRs were created) so the user knows exactly what was captured.

Quick Start

Start grilling the design one question at a time, updating CONTEXT.md and creating ADRs as decisions emerge.

Frequently Asked Questions about grill-with-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture design decisions and record architecture choices during a brainstorming session?

You can capture design decisions by running a one-question-at-a-time design interview that records outcomes directly into a CONTEXT.md file and Architecture Decision Records as decisions settle.

What is the best way to document ubiquitous language and architectural constraints while designing?

Documenting ubiquitous language and constraints involves updating a CONTEXT.md file with agreed terms and conventions, while creating ADRs to record the context, decision, and alternatives for architectural choices.

How do I conduct a design interview to surface unknowns and flesh out a software architecture?

A design interview surfaces unknowns by asking one sharp question at a time, targeting the highest-leverage unknowns first, and recommending an answer for each prompt to guide the exploration.

Can I automate ADR creation and update context management files without losing chat history?

Yes, the workflow persists each outcome as it settles by explicitly confirming before writing, ensuring newly agreed terms update CONTEXT.md and architectural decisions generate durable ADR files.

Does this design workflow require an existing CONTEXT.md file to start recording decisions?

No, it reads ./CONTEXT.md first if it exists to grill against already decided terms and domain language, but it can start from scratch to establish new conventions and constraints.

When should I not use an interactive design interview for architecture decisions?

You should avoid this interactive grilling process if your design is fully specified with no unknowns to surface, or if you only need informal discussion without durable ADR or CONTEXT.md artifacts.