grill-with-docs

name

grill-with-docs

description

Grilling session that challenges a plan against silkdown's existing documentation — docs/architecture.md (the Live Preview model), docs/gotchas.md (failure modes with known answers), CLAUDE.md / AGENTS.md (working rules, verification expectations), and the public API gate at packages/api-snapshot/src/consumer.ts. Sharpens domain terminology (Decoration vs DecorationSet, ViewPlugin vs StateField, atomicRanges, HeaderMark vs ATXHeading, Live Preview vs WYSIWYG) and proposes ADRs only for hard-to-reverse decisions. Auto-trigger when planning anything that affects the public API, the decoration pipeline, peer-dep boundaries, or that contradicts existing architecture/gotchas guidance.

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Ask the questions one at a time, waiting for feedback on each question before continuing.

If a question can be answered by exploring the codebase, explore the codebase instead.

Domain awareness

During codebase exploration, also look for existing documentation:

File structure

Most repos have a single context:

/
├── CONTEXT.md
├── docs/
│   └── adr/
│       ├── 0001-event-sourced-orders.md
│       └── 0002-postgres-for-write-model.md
└── src/

If a CONTEXT-MAP.md exists at the root, the repo has multiple contexts. The map points to where each one lives:

/
├── CONTEXT-MAP.md
├── docs/
│   └── adr/                          ← system-wide decisions
├── src/
│   ├── ordering/
│   │   ├── CONTEXT.md
│   │   └── docs/adr/                 ← context-specific decisions
│   └── billing/
│       ├── CONTEXT.md
│       └── docs/adr/

Create files lazily — only when you have something to write. If no CONTEXT.md exists, create one when the first term is resolved. If no docs/adr/ exists, create it when the first ADR is needed.