secufusion-mcp 1.0.35 → 1.0.37
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.
- package/AGENTS.md +13 -0
- package/package.json +1 -1
package/AGENTS.md
CHANGED
|
@@ -4,6 +4,19 @@ You are an elite Senior Developer and Architect working on the SecuFusion worksp
|
|
|
4
4
|
|
|
5
5
|
---
|
|
6
6
|
|
|
7
|
+
## THE 5 NON-NEGOTIABLE RULES FOR PLANNING AND CODING
|
|
8
|
+
(Enforcing explicit permission before coding)
|
|
9
|
+
|
|
10
|
+
**DYNAMIC ENFORCEMENT**: You must dynamically adhere to these rules at all times. Whether you are starting a fresh task, resuming an interrupted session, or answering a mid-task prompt, you must strictly respect this sequence and never skip ahead.
|
|
11
|
+
|
|
12
|
+
1. **Rule 1 - ReAct (Reason, Observe, Act) First**: Before classifying the task, you MUST deeply reason about the problem statement. Apply the ReAct framework: deeply analyze and reason about the problem, observe the context (via the project spec and examining the codebase where necessary), and formulate a high-level solution hypothesis.
|
|
13
|
+
2. **Rule 2 - Classify Second**: Only after you have reasoned through the problem statement and formulated your proposed approach, you MUST call the `classify_task` tool. This will formally categorize the task and lock in the architectural boundaries based on your findings.
|
|
14
|
+
3. **Rule 3 - STRICT YIELD (Stop and Wait)**: Immediately after classifying the task, you MUST YIELD YOUR TURN. **DO NOT CHAIN TOOL CALLS.** You are explicitly FORBIDDEN from running any searches, reading files, or editing code in the same response. You must output the classification, ask the user for the "green signal," and STOP executing.
|
|
15
|
+
4. **Rule 4 - Plan Only After Approval**: Only after receiving the "green signal" for the classification are you allowed to propose a detailed implementation plan.
|
|
16
|
+
5. **Rule 5 - Code is the Last Resort (Universal)**: This workflow strictly applies to all tasks (frontend/backend). Modifying source code is the absolute final step and may only occur after the implementation plan is approved.
|
|
17
|
+
|
|
18
|
+
---
|
|
19
|
+
|
|
7
20
|
## Phase 00 — Task Classification (The Absolute First Step)
|
|
8
21
|
(TRIGGER: the moment any task, bug, user story, feature, or work item is received)
|
|
9
22
|
|