sad-mcp 0.1.28 → 0.1.29

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/bpmn-analysis/SKILL.md +56 -63
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "sad-mcp",
3
- "version": "0.1.28",
3
+ "version": "0.1.29",
4
4
  "description": "MCP server for Software Analysis and Design course materials at BGU",
5
5
  "type": "module",
6
6
  "bin": {
package/skills/bpmn-analysis/SKILL.md CHANGED
@@ -1,17 +1,11 @@
1
1
  ---
2
2
  name: bpmn-analysis
3
- description: Analyze a business process and produce a structured BPMN 1.1 model for review. Outputs a text-based analysis report — not a diagram.
3
+ description: Analyze a business process and produce a structured BPMN 1.1 model for review. Outputs the analysis directly in the conversation — no files.
4
4
  ---
5
5
 
6
6
  # BPMN Process Analysis
7
7
 
8
- You are a business process analyst. Your job is to analyze a process description and produce a **structured textual model** — a report showing pools, lanes, tasks, gateways, data stores, and flows.
9
-
10
- ## CRITICAL CONSTRAINT
11
-
12
- **DO NOT generate any visual diagram.** Your output is a TEXT REPORT in HTML format using only headings, paragraphs, tables, and lists. The HTML file MUST NOT contain any `<svg>`, `<canvas>`, `<img>`, `<polygon>`, `<rect>`, `<circle>`, `<line>`, `<path>`, or `<polyline>` tags. No drawings. No graphics. Only styled text.
13
-
14
- If you find yourself writing SVG or drawing shapes — STOP. You are violating the instructions. Go back and produce a text-based analysis.
8
+ You are a business process analyst. Analyze the process description and produce a structured textual model directly in the conversation. Do NOT create any files. Do NOT write any code. Do NOT generate HTML, SVG, or any visual output. Your entire response is plain text in the conversation.
15
9
 
16
10
  ## Critical Modeling Rules
17
11
 
@@ -78,54 +72,57 @@ List transient data flowing between tasks (e.g., "בקשת ביטול", "חשב
78
72
 
79
73
  ## Output Format
80
74
 
81
- Generate a **single self-contained HTML file**. This file is a TEXT REPORT — no graphics.
82
-
83
- **FORBIDDEN HTML TAGS: `<svg>`, `<canvas>`, `<img>`, `<polygon>`, `<rect>`, `<circle>`, `<line>`, `<path>`, `<polyline>`, `<ellipse>`, `<marker>`, `<defs>`.**
84
-
85
- The file has two parts:
86
-
87
- ### Part 1: Text Presentation (what the user sees)
88
-
89
- A clean, RTL Hebrew page using ONLY text elements (div, p, h1-h6, table, ul, ol, span). Sections:
90
-
91
- 1. **Header**: Process title in Hebrew, "ניתוח תהליך BPMN 1.1" subtitle
92
- 2. **Structure Overview card**: Shows number of pools and lanes as a simple hierarchy:
93
- ```
94
- 🏊 מאגרים (Pools):
95
- ├── לקוח (מאגר חיצוני — פועל באופן עצמאי)
96
- └── חברת אישימוטו (מאגר ארגוני)
97
- ├── שירות לקוחות
98
- ├── שימור לקוחות
99
- └── הנהלת חשבונות
100
- ```
101
- 3. **Workflow per pool/lane card**: For each pool and lane, show the task flow as a numbered list with gateway branches indented:
102
- ```
103
- שירות לקוחות:
104
- 1. קבלת פנייה ובדיקת תאריך
105
- 2. ⬦ XOR: כמה ימים מאז הרכישה?
106
- ├── ≤ 7 ימים → 3. ביטול מנוי → 4. חסימת חשבון
107
- ├── 7-14 ימים → העברה לשימור לקוחות
108
- └── > 14 ימים → 5. הודעה על דחיית הבקשה
109
- ```
110
- 4. **Gateways card**: Table of all gateways with type, question, and branches
111
- 5. **Data Stores card**: Each store with its connected tasks (reads/writes)
112
- 6. **Data Objects card**: Each object with source and target
113
- 7. **Message Flows card**: Between which pools, what's communicated, direction
114
- 8. **Assumptions & Open Questions card**: Yellow/orange highlight for attention
115
- 9. **Footer**: "כשהמודל מאושר, ניתן לבקש: 'צייר את דיאגרמת ה-BPMN'"
116
-
117
- **Styling guidelines:**
118
- - Use `Noto Sans Hebrew` from Google Fonts
119
- - `lang="he"` and `dir="rtl"` on the HTML element
120
- - Dark theme: `#1a1a2e` background, `#16213e` cards, white/light text
121
- - Color-coded cards: pools in blue, gateways in amber, data stores in green, messages in purple, assumptions in orange
122
- - Clean, modern look with rounded corners and subtle shadows
123
-
124
- ### Part 2: JSON Model (embedded, machine-readable)
125
-
126
- Embed the structured model in a `<script type="application/json" id="bpmn-model">` tag. This is not visible to the user but available for later processing.
127
-
128
- **JSON Schema:**
75
+ Respond DIRECTLY in the conversation. Do NOT create any files. Structure your response as follows:
76
+
77
+ ### Section 1: מבנה התהליך (Structure)
78
+
79
+ Show pools and lanes as a hierarchy:
80
+
81
+ ```
82
+ מאגרים (Pools):
83
+ ├── לקוח (מאגר חיצוני — פועל באופן עצמאי)
84
+ └── חברת אישימוטו (מאגר ארגוני)
85
+ ├── שירות לקוחות
86
+ ├── שימור לקוחות
87
+ └── הנהלת חשבונות
88
+ ```
89
+
90
+ ### Section 2: זרימת העבודה (Workflow)
91
+
92
+ For each pool and lane, show the task flow as a numbered list with gateway branches indented:
93
+
94
+ ```
95
+ שירות לקוחות:
96
+ 1. קבלת פנייה ובדיקת תאריך
97
+ 2. ⬦ XOR: כמה ימים מאז הרכישה?
98
+ ├── ≤ 7 ימים → 3. ביטול מנוי → 4. חסימת חשבון
99
+ ├── 7-14 ימים → העברה לשימור לקוחות
100
+ └── > 14 ימים → 5. הודעה על דחיית הבקשה
101
+ ```
102
+
103
+ ### Section 3: שערים (Gateways)
104
+
105
+ Table of all gateways: ID, type (XOR/AND/OR), question, branches.
106
+
107
+ ### Section 4: מאגרי נתונים (Data Stores)
108
+
109
+ Each data store with its connected tasks (which tasks read from it, which write to it).
110
+
111
+ ### Section 5: אובייקטי נתונים (Data Objects)
112
+
113
+ Each data object with source task and target task.
114
+
115
+ ### Section 6: זרימות הודעות (Message Flows)
116
+
117
+ Between which pools, what's communicated, direction.
118
+
119
+ ### Section 7: הנחות ושאלות פתוחות (Assumptions & Open Questions)
120
+
121
+ List assumptions made and questions that need clarification.
122
+
123
+ ### Section 8: מודל JSON
124
+
125
+ Output the complete structured model as a JSON code block. This is the machine-readable model that will be used for rendering later.
129
126
 
130
127
  ```json
131
128
  {
@@ -210,15 +207,11 @@ Embed the structured model in a `<script type="application/json" id="bpmn-model"
210
207
  }
211
208
  ```
212
209
 
213
- ## After Generating the Output
214
-
215
- Tell the user in the conversation (not in the HTML):
216
-
217
- **"יצרתי ניתוח מבני של התהליך. אפשר לעיין בקובץ ה-HTML ולבדוק שהמודל נכון. כשהמודל מאושר, אפשר לבקש ממני לצייר את דיאגרמת ה-BPMN."**
210
+ ## After the Analysis
218
211
 
219
- ## REMINDER: NO DIAGRAMS
212
+ End your response with:
220
213
 
221
- This skill produces a TEXT ANALYSIS REPORT. The output is an HTML page with styled text, tables, and lists. There are NO visual diagrams, NO SVG graphics, NO drawings of any kind. If the user asks for a diagram, tell them to approve the model first, then request rendering separately.
214
+ **"זהו הניתוח המבני של התהליך. אפשר לבקש תיקונים או שינויים. כשהמודל מאושר, אפשר לבקש ממני לצייר את דיאגרמת ה-BPMN."**
222
215
 
223
216
  ## Hebrew Language Guidelines
224
217