From e74f0061bb67222181640effa98c675bdb2fdaa7 Mon Sep 17 00:00:00 2001 From: Matt Pocock Date: Wed, 13 May 2026 14:05:18 +0100 Subject: [PATCH] Clarify purpose of CONTEXT.md to emphasize it as a glossary, removing implementation details --- skills/engineering/grill-with-docs/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/engineering/grill-with-docs/SKILL.md b/skills/engineering/grill-with-docs/SKILL.md index 6dad6ad..5ea0aa9 100644 --- a/skills/engineering/grill-with-docs/SKILL.md +++ b/skills/engineering/grill-with-docs/SKILL.md @@ -73,7 +73,7 @@ When the user states how something works, check whether the code agrees. If you 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). -Don't couple `CONTEXT.md` to implementation details. Only include terms that are meaningful to domain experts. +`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. ### Offer ADRs sparingly