grill-with-docs · wayfinder-cli

Fixture. This page is the stdout of wayfinder skill grill-with-docs, run against a config with tracker value github cli and two registered ticket skills (grill-design, pre-mortem). Change either and this render changes with it.

Supporting files. The ## Disclosed files block below names 2 ids an agent can fetch on its own. Each is served here too: domain-modeling/adr-format, domain-modeling/context-format.

$ wayfinder skill grill-with-docs82 lines

1Interview me relentlessly about every aspect of this until we reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
2
3Ask the questions one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering.
4
5If a *fact* can be found by exploring the environment (filesystem, tools, etc.), look it up rather than asking me. The *decisions*, though, are mine — put each one to me and wait for my answer.
6
7Do not act on it until I confirm we have reached a shared understanding.
8
9## Domain Modeling
10
11Actively build and sharpen the project's domain model as you design. This is the *active* discipline — challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise. (Merely *reading* `CONTEXT.md` for vocabulary is not this skill — that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.)
12
13### File structure
14
15Most repos have a single context:
16
17```
18/
19├── CONTEXT.md
20├── docs/
21│   └── adr/
22│       ├── 0001-event-sourced-orders.md
23│       └── 0002-postgres-for-write-model.md
24└── src/
25```
26
27If a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:
28
29```
30/
31├── CONTEXT-MAP.md
32├── docs/
33│   └── adr/                          ← system-wide decisions
34├── src/
35│   ├── ordering/
36│   │   ├── CONTEXT.md
37│   │   └── docs/adr/                 ← context-specific decisions
38│   └── billing/
39│       ├── CONTEXT.md
40│       └── docs/adr/
41```
42
43Create 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.
44
45### During the session
46
47#### Challenge against the glossary
48
49When the user uses a term that conflicts with the existing language in `CONTEXT.md`, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"
50
51#### Sharpen fuzzy language
52
53When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account' — do you mean the Customer or the User? Those are different things."
54
55#### Discuss concrete scenarios
56
57When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.
58
59#### Cross-reference with code
60
61When the user states how something works, check whether the code agrees. If you find a contradiction, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible — which is right?"
62
63#### Update CONTEXT.md inline
64
65When a term is resolved, update `CONTEXT.md` right there. Don't batch these up — capture them as they happen. Use the format in [CONTEXT-FORMAT.md](./CONTEXT-FORMAT.md).
66
67`CONTEXT.md` should be totally devoid of implementation details. Do not treat `CONTEXT.md` as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.
68
69#### Offer ADRs sparingly
70
71Only offer to create an ADR when all three are true:
72
731. **Hard to reverse** — the cost of changing your mind later is meaningful
742. **Surprising without context** — a future reader will wonder "why did they do it this way?"
753. **The result of a real trade-off** — there were genuine alternatives and you picked one for specific reasons
76
77If any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](./ADR-FORMAT.md).
78
79## Disclosed files
80
81- `wayfinder skill domain-modeling/adr-format` — when you are recording an architectural decision
82- `wayfinder skill domain-modeling/context-format` — when you are writing or updating the glossary