SKILL.md - AiToEarn

SKILL.md

1	---
2	name: grill-with-docs
3	description: Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
4	---
5
6	<what-to-do>
7
8	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.
9
10	Ask the questions one at a time, waiting for feedback on each question before continuing.
11
12	If a question can be answered by exploring the codebase, explore the codebase instead.
13
14	</what-to-do>
15
16	<supporting-info>
17
18	## Domain awareness
19
20	During codebase exploration, also look for existing documentation:
21
22	### File structure
23
24	Most repos have a single context:
25
26	```
27	/
28	├── CONTEXT.md
29	├── docs/
30	│ └── adr/
31	│ ├── 0001-event-sourced-orders.md
32	│ └── 0002-postgres-for-write-model.md
33	└── src/
34	```
35
36	If a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:
37
38	```
39	/
40	├── CONTEXT-MAP.md
41	├── docs/
42	│ └── adr/ ← system-wide decisions
43	├── src/
44	│ ├── ordering/
45	│ │ ├── CONTEXT.md
46	│ │ └── docs/adr/ ← context-specific decisions
47	│ └── billing/
48	│ ├── CONTEXT.md
49	│ └── docs/adr/
50	```
51
52	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.
53
54	## During the session
55
56	### Challenge against the glossary
57
58	When 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?"
59
60	### Sharpen fuzzy language
61
62	When 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."
63
64	### Discuss concrete scenarios
65
66	When 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.
67
68	### Cross-reference with code
69
70	When 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?"
71
72	### Update CONTEXT.md inline
73
74	When 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).
75
76	Don't couple `CONTEXT.md` to implementation details. Only include terms that are meaningful to domain experts.
77
78	### Offer ADRs sparingly
79
80	Only offer to create an ADR when all three are true:
81
82	1. Hard to reverse — the cost of changing your mind later is meaningful
83	2. Surprising without context — a future reader will wonder "why did they do it this way?"
84	3. The result of a real trade-off — there were genuine alternatives and you picked one for specific reasons
85
86	If any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](./ADR-FORMAT.md).
87
88	</supporting-info>
89

89 lines MARKDOWN