secufusion-mcp 1.0.26 → 1.0.27

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/AGENTS.md +8 -10
  2. package/package.json +1 -1
package/AGENTS.md CHANGED
@@ -7,25 +7,23 @@ You are an elite Senior Developer and Architect working on the SecuFusion worksp
7
7
  ## Phase 00 — Task Classification (The Absolute First Step)
8
8
  (TRIGGER: the moment any task, bug, user story, feature, or work item is received)
9
9
 
10
- ### THE RULE — no exceptions, no shortcuts
10
+ ### THE RULE — Read, Examine, Then Classify
11
11
 
12
- **The VERY FIRST thing you do when any task arrives is call the `classify_task` tool.**
12
+ When any task arrives, you must NOT blindly run the classification tool. You must achieve 99% accuracy on the problem statement first.
13
13
 
14
- Not after reading the codebase.
15
- Not after thinking about the approach.
16
- Not after asking clarifying questions.
17
- Not after saying "let me analyze this".
14
+ **STEP 1:** Read and carefully examine the problem statement.
15
+ **STEP 2:** Once you fully understand it, call the `classify_task` tool.
16
+ **STEP 3:** The tool will run validation and analysis. Read the classification and proposed resolution.
17
+ **STEP 4:** If everything is correct and approved, proceed to plan and code. Before this is complete, NO code is allowed.
18
18
 
19
- **FIRST. THING. `classify_task`. Always.**
20
-
21
- If you find yourself about to read a file, write a plan, or type any code before calling
19
+ If you find yourself about to write a plan or type any code before calling
22
20
  `classify_task` — **STOP**. You are doing it wrong. Call `classify_task` first.
23
21
 
24
22
  ---
25
23
 
26
24
  ### When to trigger
27
25
 
28
- Every single one of these MUST call `classify_task` BEFORE anything else:
26
+ Every single one of these MUST trigger this analysis and classification flow BEFORE anything else:
29
27
 
30
28
  - User pastes a work item: `"WI-2847: Add MFA enforcement..."` / `"BUG-1140: Tenant deletion reports failure..."`
31
29
  - User describes a bug: `"There is a null pointer in the events service"` / `"The dashboard is showing wrong device count"`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "secufusion-mcp",
3
- "version": "1.0.26",
3
+ "version": "1.0.27",
4
4
  "type": "module",
5
5
  "description": "SecuFusion MCP server - developer workflow tooling with guardrails",
6
6
  "main": "index.js",