sad-mcp 1.1.1 → 1.1.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sad-mcp",
-  "version": "1.1.1",
+  "version": "1.1.2",
   "description": "MCP server for Software Analysis and Design course materials at BGU",
   "type": "module",
   "bin": {

package/skills/uml-use-case-diagram/SKILL.md

@@ -75,27 +75,24 @@ The shared files prepended to this prompt define the layout recipes, model shape
 **Start with zero.** Add «include» or «extend» only when you can explicitly justify it against the tests below. When in doubt, leave it out.
 
 ### «include»
-Allowed only when **all four** hold:
-1. The sub-behavior is **mandatory** every time the base UC runs
-2. The sub-behavior is shared by **2 or more** base UCs — there must be ≥2 incoming «include» arrows
-3. The included UC has **no direct association to any actor** — if any actor connects to it, it is a regular UC, not an included sub-behavior
-4. Extracting it genuinely simplifies the diagram — if the diagram becomes more complex, fold it back in
+«include» means: every time the base UC runs, the included UC **always** runs as part of it — no exceptions, no conditions. It is not "if X happens, then Y" — that is «extend». It is "X always does Y as part of its execution."
+
+However, **always-happens does not automatically mean extract**. A step that always happens inside a UC is usually just part of that UC. Only extract it when:
+1. It is shared by **2 or more** base UCs — there must be ≥2 incoming «include» arrows
+2. The included UC has **no direct association to any actor** — actor-connected UCs are standalone UCs, not sub-behaviors
+3. Extracting it genuinely reduces duplication — not just because it feels like a "step"
 
 Arrow direction: Base UC → Included UC. Dashed line, open arrowhead.
 
-**Immediate disqualifiers — if any apply, do NOT use «include»:**
-- Only one base UC points to it → fold into the parent
-- An actor has an association line to it → it is a standalone UC
-- You added it just to avoid repeating a label → wrong reason; keep behavior inside the UC
+**Immediate disqualifiers:**
+- Only one base UC points to it → fold it into the parent UC
+- An actor connects to it → it is a regular standalone UC, not an «include» target
+- It is conditional or optional → that is «extend», not «include»
 
 ### «extend»
-Allowed only when:
-1. The behavior is **genuinely optional or conditional** (not just infrequent)
-2. The extension would clutter the base UC if included inside it
-
-Arrow direction: Extension UC → Base UC. Use at most once or twice per diagram.
+«extend» means: sometimes, under a specific condition, an additional behavior fires. The base UC runs fine without it.
 
-**If you cannot articulate the exact condition under which the extension fires, do not add it.**
+Arrow direction: Extension UC → Base UC. Use at most once or twice per diagram. If you cannot state the exact condition in one sentence, do not add it.
 
 ---