ofiere-openclaw-plugin 4.25.0 → 4.26.0

package/package.json

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

@@ -222,6 +222,13 @@ ${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.
+- PLANNING GATE: Before creating ANY task with 3+ execution steps, a due_date, or when the user describes a multi-phase project, ALWAYS ask: "Should I create a Plan first so you can review the structure before I create individual tasks?" If the user says yes, use OFIERE_PLAN_OPS. If they say no or it's a simple one-shot task, proceed directly with OFIERE_TASK_OPS.
+- TASK PLACEMENT — SOP-AWARE ROUTING: When creating a task, the system auto-assigns a PM space. But for FOLDER placement, follow this protocol:
+  1. If the user explicitly provides space_id or folder_id, use those directly.
+  2. If not, and you have active SOPs (loaded via 🔴 COMPLEX assessment), check if any SOP defines an operating structure or folder routing (e.g. "place marketing tasks in Marketing/Campaigns"). Follow the SOP's structure.
+  3. If no SOP guidance exists, check the Space Files tab for an operating map/structure document using OFIERE_FILE_OPS action:"list_files". If found, read it with "read_text_file" and follow its routing rules.
+  4. If no routing guidance exists at all, ask the user: "I can place this task in your default space root, or create a new folder/project for it. Which do you prefer?"
+  5. Do NOT blindly dump all SOPs to check routing — smart-select only SOPs whose title/department matches the task domain.
 
 ## SOP PROTOCOL — Adaptive Complexity Assessment
 

package/src/tools.ts

@@ -441,6 +441,61 @@ async function handleCreateTask(
       cf.assignees = [{ id: assignee, type: "agent" }];
     }
 
+    // ── Intelligent space_id resolution ──────────────────────────────────
+    // Priority: explicit param > agent's default_space_id > first existing space > auto-create
+    let resolvedSpaceId = (params.space_id as string) || null;
+    let resolvedFolderId = (params.folder_id as string) || null;
+    let spaceAutoCreated = false;
+
+    if (!resolvedSpaceId) {
+      try {
+        // 1. Check agent's configured default_space_id
+        if (assignee) {
+          const { data: agentRow } = await supabase
+            .from("agents")
+            .select("default_space_id")
+            .eq("id", assignee)
+            .eq("user_id", userId)
+            .single();
+          if (agentRow?.default_space_id) {
+            resolvedSpaceId = agentRow.default_space_id;
+          }
+        }
+
+        // 2. Fallback: use the first existing space for this user
+        if (!resolvedSpaceId) {
+          const { data: existingSpaces } = await supabase
+            .from("pm_spaces")
+            .select("id")
+            .eq("user_id", userId)
+            .order("created_at", { ascending: true })
+            .limit(1);
+          if (existingSpaces && existingSpaces.length > 0) {
+            resolvedSpaceId = existingSpaces[0].id;
+          }
+        }
+
+        // 3. Nuclear fallback: auto-create a space
+        if (!resolvedSpaceId) {
+          const newSpaceId = crypto.randomUUID();
+          const { error: spaceErr } = await supabase.from("pm_spaces").insert({
+            id: newSpaceId,
+            user_id: userId,
+            name: "Operations",
+            icon: "🏢",
+            icon_color: "#FF6D29",
+            sort_order: 0,
+          });
+          if (!spaceErr) {
+            resolvedSpaceId = newSpaceId;
+            spaceAutoCreated = true;
+          }
+        }
+      } catch {
+        // Non-fatal: task will still be created, just without space context
+      }
+    }
+
     const insertData: Record<string, unknown> = {
       id,
       user_id: userId,
@@ -450,8 +505,8 @@ async function handleCreateTask(
       assignee_type: "agent",
       status: (params.status as string) || "PENDING",
       priority: params.priority !== undefined ? params.priority : 1,
-      space_id: (params.space_id as string) || null,
-      folder_id: (params.folder_id as string) || null,
+      space_id: resolvedSpaceId,
+      folder_id: resolvedFolderId,
       start_date: (params.start_date as string) || null,
       due_date: (params.due_date as string) || (params.start_date as string) || null,
       tags: (params.tags as string[]) || [],
@@ -578,6 +633,17 @@ async function handleCreateTask(
       id,
       message: `Task "${params.title}" created and assigned to ${assignee || "no one"}${extrasStr}`,
       task: insertData,
+      spacePlacement: resolvedSpaceId
+        ? {
+            space_id: resolvedSpaceId,
+            auto_created: spaceAutoCreated,
+            note: spaceAutoCreated
+              ? 'A new "Operations" space was auto-created because no PM spaces existed.'
+              : resolvedFolderId
+                ? `Placed in folder ${resolvedFolderId}`
+                : "Placed in space root. To organize, check your SOPs/operating structure for folder routing, or specify folder_id.",
+          }
+        : undefined,
       scheduledExecution: didSchedule ? `Will auto-execute on ${startDate}` : undefined,
       recurrence: recurrenceInfo,
     });