ofiere-openclaw-plugin 4.19.2 → 4.21.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ofiere-openclaw-plugin",
-  "version": "4.19.2",
+  "version": "4.21.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

@@ -67,11 +67,11 @@ const TOOL_DOCS: Record<string, string> = {
     - mark_read: Mark one notification read by ID
     - mark_all_read: Mark all as read
     - send_report: Send a PM progress report to YOUR connected channels (Telegram, Discord, Slack, etc.)
-      - Required: scope_type (space|folder|project|task|all)
+      - Required: scope_type (space|folder|project|task|all), agent_id (YOUR name, e.g. "thalia")
       - Optional: scope_id, channel_types[] (filter to specific channels), include_completed
       - The report is automatically generated from current PM data and sent through YOUR channel bindings ONLY
     - schedule_report: Create a recurring/scheduled report
-      - Required: scope_type, recurrence_type (hourly|daily|weekly|monthly)
+      - Required: scope_type, recurrence_type (hourly|daily|weekly|monthly), agent_id (YOUR name)
       - Optional: scope_id, scope_label, channel_types[], recurrence_time (HH:MM UTC, default 09:00), recurrence_interval, recurrence_days_of_week (e.g. "mon,wed,fri"), include_completed
     - list_schedules: View all your active report schedules
     - delete_schedule: Remove a scheduled report by schedule_id`,
@@ -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: {
@@ -201,8 +202,8 @@ ${toolDocs}
 - When task instructions or system prompts contain file references like @[filename](file:FILE_ID), use OFIERE_FILE_OPS action:"read_text_file" file_id:"FILE_ID" to read the file content. Do NOT ask the user for the file — retrieve it yourself.
 - Use OFIERE_FILE_OPS to create output files (reports, data, configs) in the Space Files explorer. Prefer create_text_file for text-based outputs.
 - To save task output as a file, call OFIERE_FILE_OPS action:"create_text_file" with the space_id from the task context.
-- CHANNEL REPORTS: When the user asks you to "send a report", "send progress", "update me on Telegram/Discord/Slack/WhatsApp", use OFIERE_NOTIFY_OPS action:"send_report". The report is generated from live PM data and sent through YOUR connected channels ONLY — not other agents' channels.
-- To set up recurring reports (e.g. "send me a daily report at 9am"), use OFIERE_NOTIFY_OPS action:"schedule_report" with scope_type and recurrence_type.
+- CHANNEL REPORTS: When the user asks you to "send a report", "send progress", "update me on Telegram/Discord/Slack/WhatsApp", use OFIERE_NOTIFY_OPS action:"send_report" with agent_id set to YOUR name. ALWAYS include agent_id — without it the report will fail. The report is generated from live PM data and sent through YOUR connected channels ONLY — not other agents' channels.
+- To set up recurring reports (e.g. "send me a daily report at 9am"), use OFIERE_NOTIFY_OPS action:"schedule_report" with scope_type, recurrence_type, and agent_id set to YOUR name.
 - If a report is too long for the channel's message limit, save the full report as a markdown file using OFIERE_FILE_OPS action:"create_text_file" and send a summary to the channel instead.
 - PLANNING WORKFLOW: Use OFIERE_PLAN_OPS to build complex multi-step execution flows BEFORE creating individual tasks. Build the plan → let the user review in the Planning Tab → execute when approved.
 - When creating a plan with nodes, nest children inside each node's children[] array. Sequential children execute in order; set parallel: true on a parent node to fork its children into parallel branches.
@@ -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

@@ -2143,14 +2143,8 @@ function registerNotifyOps(
   api: any,
   supabase: SupabaseClient,
   userId: string,
+  resolveAgent: (explicitId?: string) => Promise<string | null>,
 ): void {
-  // Helper: resolve the agent's own ID for agent-scoped operations
-  const resolveAgentId = (): string => {
-    try {
-      const state = api.getState?.() || {};
-      return state.agentId || process.env.OFIERE_AGENT_ID || "";
-    } catch { return process.env.OFIERE_AGENT_ID || ""; }
-  };
 
   api.registerTool({
     name: "OFIERE_NOTIFY_OPS",
@@ -2163,10 +2157,10 @@ function registerNotifyOps(
       `- "mark_all_read": Mark all as read\n` +
       `- "delete": Delete a notification. Required: id\n` +
       `- "send_report": Send a PM progress report to YOUR connected channels (Telegram, Discord, etc.)\n` +
-      `    Required: scope_type (space|folder|project|task|all)\n` +
+      `    Required: scope_type (space|folder|project|task|all), agent_id (YOUR name e.g. "thalia")\n` +
       `    Optional: scope_id, channel_types[] (filter specific channels), include_completed (default true)\n` +
       `- "schedule_report": Create a recurring/scheduled report\n` +
-      `    Required: scope_type, recurrence_type (hourly|daily|weekly|monthly)\n` +
+      `    Required: scope_type, recurrence_type (hourly|daily|weekly|monthly), agent_id (YOUR name)\n` +
       `    Optional: scope_id, scope_label, channel_types[], recurrence_time (HH:MM UTC, default 09:00),\n` +
       `             recurrence_interval (default 1), recurrence_days_of_week (e.g. "mon,wed,fri"), include_completed\n` +
       `- "list_schedules": List your active report schedules\n` +
@@ -2176,6 +2170,7 @@ function registerNotifyOps(
       required: ["action"],
       properties: {
         action: { type: "string", enum: ["list", "mark_read", "mark_all_read", "delete", "send_report", "schedule_report", "list_schedules", "delete_schedule"] },
+        agent_id: { type: "string", description: "Your agent name or ID (required for send_report/schedule_report)" },
         id: { type: "string", description: "Notification ID" },
         schedule_id: { type: "string", description: "Schedule ID (for delete_schedule)" },
         unread_only: { type: "boolean", description: "Only show unread" },
@@ -2228,8 +2223,8 @@ function registerNotifyOps(
           const scopeId = params.scope_id as string | undefined;
           const channelTypes = (params.channel_types as string[]) || [];
           const includeCompleted = params.include_completed !== false;
-          const agentId = resolveAgentId();
-          if (!agentId) return err("Cannot resolve your agent ID. Ensure OFIERE_AGENT_ID is configured.");
+          const agentId = await resolveAgent(params.agent_id as string | undefined);
+          if (!agentId) return err("Cannot resolve your agent ID. Pass agent_id with your name (e.g. 'thalia', 'ivy').");
 
           // Call the dashboard API to generate + dispatch
           const supabaseUrl = (supabase as any).supabaseUrl || process.env.OFIERE_SUPABASE_URL || process.env.SUPABASE_URL || "";
@@ -2266,8 +2261,8 @@ function registerNotifyOps(
         case "schedule_report": {
           const scopeType = (params.scope_type as string) || "all";
           const recurrenceType = (params.recurrence_type as string) || "daily";
-          const agentId = resolveAgentId();
-          if (!agentId) return err("Cannot resolve your agent ID.");
+          const agentId = await resolveAgent(params.agent_id as string | undefined);
+          if (!agentId) return err("Cannot resolve your agent ID. Pass agent_id with your name (e.g. 'thalia', 'ivy').");
 
           const recurrenceTime = (params.recurrence_time as string) || "09:00";
           const recurrenceInterval = (params.recurrence_interval as number) || 1;
@@ -4869,7 +4864,7 @@ export function registerTools(
   registerScheduleOps(api, supabase, userId);                 // 4
   registerKnowledgeOps(api, supabase, userId);                // 5
   registerWorkflowOps(api, supabase, userId);                 // 6
-  registerNotifyOps(api, supabase, userId);                   // 7
+  registerNotifyOps(api, supabase, userId, resolveAgent);     // 7
   registerMemoryOps(api, supabase, userId);                   // 8
   registerPromptOps(api, supabase, userId);                   // 9
   registerConstellationOps(api, supabase, userId);            // 10