grill-with-docs

Cantos conventions (read first). This skill uses generic doc names; map them to this repo:

• Glossary (CONTEXT.md) → inside a Cantos project, keep the ubiquitous-language glossary as a ## Ubiquitous Language section in projects/<name>/context.md (it already loads before every task, so the shared language stays in context). Standalone/external repo: use a root CONTEXT.md as written.
• ADRs (docs/adr/) → append to decisions/log.md (append-only, never deleted) — one short, dated entry per decision using ADR-FORMAT.md, prefixed [<project>]. Standalone/external repo: use docs/adr/.
• The glossary-entry shape and the three-question ADR test below are unchanged.

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.