sparkecoder 0.1.83 → 0.1.85

package/dist/agent/index.js

@@ -3649,22 +3649,27 @@ function createTodoTool(options) {
 - "clear": Remove all todo items from the list
 
 ## Plan Actions (for complex, multi-phase work)
-- "save_plan": Create or update a named plan \u2014 a persistent markdown document with hierarchical tasks, subtasks, and notes. Plans survive context compaction and are always available.
+- "save_plan": Create or update a named plan. When saved and no active todos exist, todos are AUTO-CREATED from the first uncompleted phase.
 - "list_plans": List all plans for this session
 - "get_plan": Read a specific plan by name
 - "delete_plan": Remove a plan
 
 ## Plans vs Todos
 - **Plans** are the big picture \u2014 the full spec with phases, subtasks, notes, and decisions. They persist on disk and are always injected into your context, even after old messages are summarized.
-- **Todos** are your current focus \u2014 the immediate steps you're working on right now.
+- **Todos** are your current focus \u2014 the immediate steps you're working on right now, auto-derived from plan phases.
 
 ## Workflow for complex tasks
-1. Create a plan with phases and subtasks (save_plan)
-2. Create todos from the first uncompleted phase (add)
-3. Work through the todos, marking them as you go
-4. When all current todos are done, update the plan (mark completed sections with [x]) and save it
-5. Create new todos from the next uncompleted phase
-6. Repeat until the plan is fully complete
+1. Create a plan with phases and subtasks using checkboxes (save_plan) \u2014 todos are auto-created from Phase 1
+2. Work through the todos, marking them as you go
+3. When all todos are done, update the plan: mark the completed phase heading with [completed] and its items with [x]
+4. Call save_plan again with the updated content \u2014 todos are auto-created from the next uncompleted phase
+5. Repeat until all phases are complete, then delete_plan
+
+## Auto-todo creation rules
+- Only triggers when there are NO active (pending/in_progress) todos
+- Skips phases with [completed] in the heading
+- Skips sections named Overview, Notes, Key Decisions, etc.
+- Only top-level checklist items (- [ ]) become todos \u2014 indented sub-items are task details
 
 ## Plan format
 Plans should be markdown with this structure:
@@ -3748,10 +3753,34 @@ Plans should be markdown with this structure:
                 error: `Todo item not found: ${todoId}`
               };
             }
+            let planContinuation;
+            if (status === "completed") {
+              const allTodos = await todoQueries.getBySession(options.sessionId);
+              const allDone = allTodos.every(
+                (t) => t.status === "completed" || t.status === "cancelled"
+              );
+              if (allDone) {
+                const plansDir = getPlansDir(options.workingDirectory, options.sessionId);
+                if (existsSync9(plansDir)) {
+                  const planFiles = readdirSync(plansDir).filter((f) => f.endsWith(".md"));
+                  for (const f of planFiles) {
+                    try {
+                      const content = await readFile6(join4(plansDir, f), "utf-8");
+                      if (parseNextUncompletedPhase(content) !== null) {
+                        planContinuation = "All todos are done but your plan has remaining phases. Update the plan now: mark the completed phase heading with [completed] and its items with [x], then call save_plan to save \u2014 new todos will be auto-created from the next phase.";
+                        break;
+                      }
+                    } catch {
+                    }
+                  }
+                }
+              }
+            }
             return {
               success: true,
               action: "mark",
-              item: formatTodoItem(updated)
+              item: formatTodoItem(updated),
+              ...planContinuation ? { planContinuation } : {}
             };
           }
           case "clear": {
@@ -3774,13 +3803,32 @@ Plans should be markdown with this structure:
             const filename = `${slugify(planName)}.md`;
             const filePath = join4(dir, filename);
             await writeFile4(filePath, planContent, "utf-8");
+            const existingTodos = await todoQueries.getBySession(options.sessionId);
+            const hasActiveTodos = existingTodos.some(
+              (t) => t.status === "pending" || t.status === "in_progress"
+            );
+            let autoCreatedTodos = [];
+            if (!hasActiveTodos) {
+              const nextPhase = parseNextUncompletedPhase(planContent);
+              if (nextPhase) {
+                const created = await todoQueries.createMany(
+                  options.sessionId,
+                  nextPhase.tasks.map((task, i) => ({ content: task, order: i }))
+                );
+                autoCreatedTodos = created.map(formatTodoItem);
+              }
+            }
             return {
               success: true,
               action: "save_plan",
               planName,
               filename,
               path: filePath,
-              sizeChars: planContent.length
+              sizeChars: planContent.length,
+              ...autoCreatedTodos.length > 0 ? {
+                autoCreatedTodos,
+                autoCreatedFromPhase: "Created todos from the first uncompleted phase. Start working on them!"
+              } : {}
             };
           }
           case "list_plans": {
@@ -3861,6 +3909,47 @@ function formatTodoItem(item) {
     createdAt: item.createdAt.toISOString()
   };
 }
+function parseNextUncompletedPhase(content) {
+  const lines = content.split("\n");
+  let currentPhase = null;
+  let currentTasks = [];
+  let hasUncompletedTask = false;
+  for (const line of lines) {
+    const h2Match = line.match(/^##\s+(.+)/);
+    if (h2Match) {
+      if (currentPhase && hasUncompletedTask && currentTasks.length > 0) {
+        return { phaseName: currentPhase, tasks: currentTasks };
+      }
+      const headingText = h2Match[1].trim();
+      if (/^(overview|notes|key decisions|context|summary|references)\b/i.test(headingText)) {
+        currentPhase = null;
+        currentTasks = [];
+        hasUncompletedTask = false;
+        continue;
+      }
+      if (/\[completed\]/i.test(headingText)) {
+        currentPhase = null;
+        currentTasks = [];
+        hasUncompletedTask = false;
+        continue;
+      }
+      currentPhase = headingText.replace(/\s*\[(in_progress|pending|completed)\]\s*/gi, "").replace(/^Phase\s+\d+[:\s]*/i, "").trim();
+      currentTasks = [];
+      hasUncompletedTask = false;
+      continue;
+    }
+    if (!currentPhase) continue;
+    const uncheckedMatch = line.match(/^[-*]\s+\[\s\]\s+(.+)/);
+    if (uncheckedMatch) {
+      currentTasks.push(uncheckedMatch[1].trim());
+      hasUncompletedTask = true;
+    }
+  }
+  if (currentPhase && hasUncompletedTask && currentTasks.length > 0) {
+    return { phaseName: currentPhase, tasks: currentTasks };
+  }
+  return null;
+}
 async function readSessionPlans(workingDirectory, sessionId) {
   const dir = getPlansDir(workingDirectory, sessionId);
   if (!existsSync9(dir)) return [];
@@ -5595,7 +5684,11 @@ async function buildSystemPrompt(options) {
   const todos = await todoQueries.getBySession(sessionId);
   const todosContext = formatTodosForContext(todos);
   const plans = await readSessionPlans(workingDirectory, sessionId);
-  const plansContext = formatPlansForContext(plans);
+  const allTodosDone = todos.length > 0 && todos.every(
+    (t) => t.status === "completed" || t.status === "cancelled"
+  );
+  const hasNoTodos = todos.length === 0;
+  const plansContext = formatPlansForContext(plans, allTodosDone || hasNoTodos);
   const platform2 = process.platform === "win32" ? "Windows" : process.platform === "darwin" ? "macOS" : "Linux";
   const currentDate = (/* @__PURE__ */ new Date()).toLocaleDateString("en-US", { weekday: "long", year: "numeric", month: "long", day: "numeric" });
   const searchInstructions = getSearchInstructions();
@@ -5628,16 +5721,19 @@ Use the **todo tool** to manage both immediate tasks AND persistent plans:
 
 **For complex, multi-phase tasks:** Create a persistent **plan** first.
 1. Research the codebase to understand what you're working with
-2. Create a plan with save_plan \u2014 a structured markdown document with phases and subtasks
-3. Create todos from the first uncompleted phase
-4. Work through the todos
-5. When done, update the plan (mark completed phases with [x]), save it again
-6. Create new todos from the next uncompleted phase
-7. Repeat until the plan is fully complete
-
-Plans persist on disk and are always injected into your context \u2014 they survive context compaction even in very long sessions. You can have multiple plans active at once (e.g., one for frontend, one for backend).
-
-You can clear the todo list and restart it, and do multiple things inside of one session.
+2. Create a plan with save_plan \u2014 a structured markdown document with phases and subtasks using checkboxes (- [ ] for uncompleted, - [x] for completed)
+3. Todos are **auto-created** from the first uncompleted phase when you save the plan (if no active todos exist)
+4. Work through the todos, marking them as you go
+5. When all todos are done, update the plan: change completed phase heading to include [completed], mark all its items with [x], then call save_plan again \u2014 new todos will be auto-created from the next uncompleted phase
+6. Repeat until all phases are complete, then delete the plan
+
+**Key details:**
+- Plans persist on disk and are always injected into your context \u2014 they survive context compaction even in very long sessions
+- You can have multiple plans active at once (e.g., one for frontend work, one for backend)
+- When you save a plan and there are no active todos, the system automatically creates todos from the first uncompleted phase (phases with [completed] in the heading are skipped)
+- Only top-level checklist items (- [ ]) become todos \u2014 indented sub-items are part of the task detail
+- Sections named Overview, Notes, Key Decisions, etc. are not treated as phases
+- You can clear the todo list and restart it, and do multiple things inside of one session
 
 ### bash Tool
 The bash tool runs commands in the terminal. Every command runs in its own session with logs saved to disk.
@@ -5888,7 +5984,7 @@ function formatTodosForContext(todos) {
 }
 var MAX_PLAN_CHARS = 3e4;
 var MAX_TOTAL_PLANS_CHARS = 6e4;
-function formatPlansForContext(plans) {
+function formatPlansForContext(plans, shouldContinue) {
   if (plans.length === 0) return "";
   let totalChars = 0;
   const sections = [];
@@ -5897,6 +5993,13 @@ function formatPlansForContext(plans) {
   sections.push("These plans persist across context compaction \u2014 they are always available.");
   sections.push("When you finish your current todos, check these plans for the next uncompleted phase,");
   sections.push("update the plan (mark completed items with [x]), then create new todos for the next phase.");
+  if (shouldContinue) {
+    sections.push("");
+    sections.push("**>>> ACTION NEEDED: Your current todos are all done but the plan has remaining phases. To continue:**");
+    sections.push("**1. Update the plan content: change the completed phase heading to include [completed] and mark its items with [x]**");
+    sections.push("**2. Call save_plan with the updated content \u2014 new todos will be auto-created from the next uncompleted phase**");
+    sections.push("**3. Continue working on the new todos <<<**");
+  }
   sections.push("");
   for (const plan of plans) {
     let content = plan.content;