ofiere-openclaw-plugin 4.19.1 → 4.20.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ofiere-openclaw-plugin",
-  "version": "4.19.1",
+  "version": "4.20.0",
   "type": "module",
   "description": "OpenClaw plugin for Ofiere PM - 13 meta-tools covering tasks, agents, projects, scheduling, knowledge, workflows, notifications, memory, prompts, constellation, space file management, execution plan builder, and SOP management",
   "keywords": ["openclaw", "ofiere", "project-management", "agents", "plugin"],

package/src/prompt.ts

@@ -134,15 +134,16 @@ const TOOL_DOCS: Record<string, string> = {
   OFIERE_SOP_OPS: `- **OFIERE_SOP_OPS** — Standard Operating Procedures for department chiefs (action: "list_templates", "create", "list", "get", "update", "delete", "list_subagents", "apply_template")
     - list_templates: See available SOP templates (built-in + user-created)
     - create: Create a new SOP. Required: agent_id, title, sop_data. Optional: department, status
-    - list: List SOPs. Optional: agent_id to filter by department chief
-    - get: Full SOP details with structured content. Required: sop_id
+    - list: List SOPs. Optional: agent_id to filter by department chief. RUNTIME READ PATH: use this to discover your active SOPs when complexity is 🔴 COMPLEX
+    - get: Full SOP details with structured content. Required: sop_id. RUNTIME READ PATH: use this after "list" to load full SOP content for execution guidance
     - update: Modify SOP content/status. Required: sop_id. Optional: title, sop_data, status, department
     - delete: Remove an SOP. Required: sop_id
     - list_subagents: View staff under a chief. Required: chief_agent_id
     - apply_template: Create SOP from a saved template. Required: agent_id, template_id
     - sop_data is a JSON object: { title, objective, scope, prerequisites[{text,checked}], steps[{name,action,owner,output}], deliverables[], escalationRules[{trigger,escalateTo,priority}], successCriteria[{text,checked}], notes }
     - Status values: draft, active, archived
-    - SOPs appear in the SOP Manager page immediately via real-time sync`,
+    - SOPs appear in the SOP Manager page immediately via real-time sync
+    - ADAPTIVE PROTOCOL: Do NOT always load SOPs. See the SOP PROTOCOL section in Rules for when to load vs skip`,
 };
 
 export function getSystemPrompt(state: {
@@ -214,6 +215,50 @@ ${toolDocs}
 - When creating SOPs for department chiefs (Thalia=CMO, Ivy=COO, Daisy=CTO-Intel, Celia=CTO-Eng), tailor content to their domain expertise.
 - Prerequisites should be actionable checklist items. Success criteria should be measurable outcomes.
 - After creating an SOP, suggest the agent set it to "active" status when ready for execution.
+
+## SOP PROTOCOL — Adaptive Complexity Assessment
+
+Before executing any user request, classify its complexity to decide whether to load your SOPs:
+
+### User Override (HIGHEST PRIORITY — always check first)
+- If user says "apply full SOP", "use SOP", "follow the SOP", "full protocol" → treat as 🔴 COMPLEX regardless of your classification
+- If user says "no SOP", "skip SOP", "just do it", "keep it simple", "quick" → treat as 🟢 SIMPLE regardless of your classification
+- User explicit intent ALWAYS overrides your classification
+
+### 🟢 SIMPLE (Skip SOPs — zero overhead)
+Single tool call, direct data retrieval, simple CRUD, status checks, quick answers.
+Criteria: Can be completed with ≤2 tool calls, no cross-agent coordination, no multi-phase execution.
+Examples: "Check my email", "List tasks", "Create a quick task", "What's the project status?", "Tell me about X"
+Action: Execute directly. Do NOT call OFIERE_SOP_OPS. Do NOT mention SOPs.
+
+### 🟡 MODERATE (Ask User)
+Multi-step work but clear execution path, no subagent delegation required, single-department scope.
+Criteria: 3-5 tool calls, single department, no escalation risk, no staff/subagent coordination needed.
+Examples: "Draft a marketing plan", "Set up a new workflow", "Analyze this report"
+Action: Ask the user briefly: "This task has moderate complexity. Do we need to apply full SOPs for this?"
+- If user says yes → escalate to 🔴 COMPLEX behavior
+- If user says no → proceed without SOPs
+
+### 🔴 COMPLEX (Auto-Load SOPs)
+Multi-phase execution, cross-department coordination, subagent delegation, production impact, escalation risk.
+Criteria: 5+ tool calls, multiple departments involved, needs staff/subagent coordination, or has escalation risk.
+Examples: "Launch full marketing campaign", "Execute deployment pipeline", "Restructure operations", "Full audit"
+Action:
+1. Call OFIERE_SOP_OPS action:"list" agent_id:"YOUR_NAME" to discover your active SOPs (returns titles + IDs)
+2. Review the SOP titles — select ONLY the SOPs relevant to the current task. Skip unrelated SOPs entirely. Do NOT load all SOPs blindly.
+3. For each RELEVANT SOP only: call OFIERE_SOP_OPS action:"get" sop_id:"..." to load full content
+4. Follow loaded SOPs as your execution framework:
+   - Prerequisites → validate ALL are met before starting (gate check)
+   - Steps → use as your execution plan (follow in order, each step has name/action/owner/output)
+   - Escalation Rules → apply when blockers arise or scope changes (P1=critical, P2=scope, P3=advisory)
+   - Success Criteria → verify ALL are met before marking task DONE
+5. If an SOP step assigns an "owner" that maps to one of your subagents, coordinate with that subagent
+6. Announce: "Applying [SOP_TITLE] protocol for this execution." (only name the SOPs you actually loaded)
+
+### Classification Transparency
+- When you load SOPs (🔴): state which SOP(s) you're following
+- When you ask about SOPs (🟡): keep the question brief and direct
+- When you skip SOPs (🟢): do NOT mention SOPs at all — just execute silently
 </ofiere-pm>`;
   }
 

package/src/tools.ts

@@ -4715,16 +4715,16 @@ async function handleSOPGet(supabase: SupabaseClient, userId: string, params: Re
       .from("agent_sops")
       .select("*")
       .eq("id", params.sop_id as string)
-      .eq("user_id", userId)
-      .maybeSingle();
+      .eq("user_id", userId);
     if (error) return err(error.message);
-    if (!data) return err("SOP not found");
+    if (!data || data.length === 0) return err("SOP not found");
 
+    const sop = data[0];
     // Parse the content to return structured data
     let parsedContent: any = {};
-    try { parsedContent = JSON.parse(data.content || "{}"); } catch { /* leave empty */ }
+    try { parsedContent = JSON.parse(sop.content || "{}"); } catch { /* leave empty */ }
 
-    return ok({ sop: { ...data, content: parsedContent } });
+    return ok({ sop: { ...sop, content: parsedContent } });
   } catch (e) { return err(e instanceof Error ? e.message : String(e)); }
 }