@iaforged/context-code 1.3.5 → 1.3.7

package/dist/src/services/orchestration/execution/OrchestrationExecutionRuntime.js

@@ -205,17 +205,17 @@ async function loadRunState(runId) {
     }
     const db = await getOrchestrationDatabase();
     const tasks = db
-        .prepare(`SELECT id, run_id, parent_task_id, scope_type, team_unit_id, assigned_agent_id, title, instructions, status, result_summary, created_at, finished_at
-       FROM orchestration_tasks
-       WHERE run_id = ?
+        .prepare(`SELECT id, run_id, parent_task_id, scope_type, team_unit_id, assigned_agent_id, title, instructions, status, result_summary, created_at, finished_at
+       FROM orchestration_tasks
+       WHERE run_id = ?
        ORDER BY created_at, id`)
         .all(requireText(runId, 'runId'))
         .map(rowToTask)
         .filter((task) => task !== null);
     const messages = db
-        .prepare(`SELECT id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
-       FROM orchestration_messages
-       WHERE run_id = ?
+        .prepare(`SELECT id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
+       FROM orchestration_messages
+       WHERE run_id = ?
        ORDER BY created_at, id`)
         .all(requireText(runId, 'runId'))
         .map(rowToMessage)
@@ -225,8 +225,8 @@ async function loadRunState(runId) {
 async function loadTaskAndRunState(taskId) {
     const db = await getOrchestrationDatabase();
     const row = db
-        .prepare(`SELECT id, run_id, parent_task_id, scope_type, team_unit_id, assigned_agent_id, title, instructions, status, result_summary, created_at, finished_at
-       FROM orchestration_tasks
+        .prepare(`SELECT id, run_id, parent_task_id, scope_type, team_unit_id, assigned_agent_id, title, instructions, status, result_summary, created_at, finished_at
+       FROM orchestration_tasks
        WHERE id = ?`)
         .get(requireText(taskId, 'taskId'));
     const task = rowToTask(row);
@@ -242,8 +242,8 @@ async function loadTaskAndRunState(taskId) {
 async function updateTasksByRun(runId, transform) {
     const db = await getOrchestrationDatabase();
     const rows = db
-        .prepare(`SELECT id, run_id, parent_task_id, scope_type, team_unit_id, assigned_agent_id, title, instructions, status, result_summary, created_at, finished_at
-       FROM orchestration_tasks
+        .prepare(`SELECT id, run_id, parent_task_id, scope_type, team_unit_id, assigned_agent_id, title, instructions, status, result_summary, created_at, finished_at
+       FROM orchestration_tasks
        WHERE run_id = ?`)
         .all(requireText(runId, 'runId'))
         .map(rowToTask)
@@ -253,8 +253,8 @@ async function updateTasksByRun(runId, transform) {
         if (!patch) {
             continue;
         }
-        db.prepare(`UPDATE orchestration_tasks
-       SET status = ?, result_summary = ?, finished_at = ?
+        db.prepare(`UPDATE orchestration_tasks
+       SET status = ?, result_summary = ?, finished_at = ?
        WHERE id = ?`).run(patch.status ?? task.status, patch.result_summary ?? task.resultSummary ?? null, patch.finished_at ?? task.finishedAt ?? null, task.id);
     }
 }
@@ -271,8 +271,8 @@ async function writeRunTransition(runId, nextStatus, options) {
     const finishedAt = options?.finishedAt === undefined
         ? current.finishedAt
         : toNullableText(options.finishedAt);
-    db.prepare(`UPDATE orchestration_runs
-     SET status = ?, started_at = ?, finished_at = ?
+    db.prepare(`UPDATE orchestration_runs
+     SET status = ?, started_at = ?, finished_at = ?
      WHERE id = ?`).run(nextStatus, startedAt, finishedAt, runId);
 }
 async function writeTaskTransition(taskId, nextStatus, options) {
@@ -287,8 +287,8 @@ async function writeTaskTransition(taskId, nextStatus, options) {
             ? nowIso()
             : null
         : toNullableText(options.finishedAt);
-    db.prepare(`UPDATE orchestration_tasks
-     SET status = ?, result_summary = ?, finished_at = ?
+    db.prepare(`UPDATE orchestration_tasks
+     SET status = ?, result_summary = ?, finished_at = ?
      WHERE id = ?`).run(nextStatus, options?.resultSummary === undefined
         ? current.task.resultSummary
         : toNullableText(options.resultSummary), finishedAt, taskId);
@@ -407,20 +407,20 @@ export class OrchestrationExecutionRuntime {
         const changed = runState.run.status !== 'in_progress';
         await withOrchestrationTransaction(async (db) => {
             const startedAt = runState.run.startedAt ?? nowIso();
-            db.prepare(`UPDATE orchestration_runs
-         SET status = ?, started_at = ?, finished_at = NULL
+            db.prepare(`UPDATE orchestration_runs
+         SET status = ?, started_at = ?, finished_at = NULL
          WHERE id = ?`).run('in_progress', startedAt, runId);
             if (input.promotePendingTasks !== false) {
                 for (const task of runState.tasks) {
                     if (task.status === 'pending' || task.status === 'blocked') {
-                        db.prepare(`UPDATE orchestration_tasks
-               SET status = ?, finished_at = NULL
+                        db.prepare(`UPDATE orchestration_tasks
+               SET status = ?, finished_at = NULL
                WHERE id = ?`).run('ready', task.id);
                     }
                 }
             }
-            db.prepare(`INSERT INTO orchestration_messages (
-          id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
+            db.prepare(`INSERT INTO orchestration_messages (
+          id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
         ) VALUES (?, ?, ?, ?, ?, ?, ?, ?)`).run(randomUUID(), runId, null, null, null, 'run.start', nowMessage('start', input.note), nowIso());
         });
         const refreshed = await loadRunState(runId);
@@ -452,20 +452,20 @@ export class OrchestrationExecutionRuntime {
         const changed = runState.run.status !== 'in_progress';
         await withOrchestrationTransaction(async (db) => {
             const startedAt = runState.run.startedAt ?? nowIso();
-            db.prepare(`UPDATE orchestration_runs
-         SET status = ?, started_at = ?, finished_at = NULL
+            db.prepare(`UPDATE orchestration_runs
+         SET status = ?, started_at = ?, finished_at = NULL
          WHERE id = ?`).run('in_progress', startedAt, runId);
             if (input.reactivateBlockedTasks !== false) {
                 for (const task of runState.tasks) {
                     if (task.status === 'blocked' || task.status === 'failed' || task.status === 'pending') {
-                        db.prepare(`UPDATE orchestration_tasks
-               SET status = ?, finished_at = NULL
+                        db.prepare(`UPDATE orchestration_tasks
+               SET status = ?, finished_at = NULL
                WHERE id = ?`).run('ready', task.id);
                     }
                 }
             }
-            db.prepare(`INSERT INTO orchestration_messages (
-          id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
+            db.prepare(`INSERT INTO orchestration_messages (
+          id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
         ) VALUES (?, ?, ?, ?, ?, ?, ?, ?)`).run(randomUUID(), runId, null, null, null, 'run.resume', nowMessage('resume', input.note), nowIso());
         });
         const refreshed = await loadRunState(runId);
@@ -494,20 +494,20 @@ export class OrchestrationExecutionRuntime {
         const changed = runState.run.status !== 'cancelled';
         await withOrchestrationTransaction(async (db) => {
             const finishedAt = nowIso();
-            db.prepare(`UPDATE orchestration_runs
-         SET status = ?, finished_at = ?
+            db.prepare(`UPDATE orchestration_runs
+         SET status = ?, finished_at = ?
          WHERE id = ?`).run('cancelled', finishedAt, runId);
             if (input.blockOpenTasks !== false) {
                 for (const task of runState.tasks) {
                     if (task.status !== 'completed') {
-                        db.prepare(`UPDATE orchestration_tasks
-               SET status = ?, finished_at = ?
+                        db.prepare(`UPDATE orchestration_tasks
+               SET status = ?, finished_at = ?
                WHERE id = ?`).run('blocked', finishedAt, task.id);
                     }
                 }
             }
-            db.prepare(`INSERT INTO orchestration_messages (
-          id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
+            db.prepare(`INSERT INTO orchestration_messages (
+          id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
         ) VALUES (?, ?, ?, ?, ?, ?, ?, ?)`).run(randomUUID(), runId, null, null, null, 'run.cancel', nowMessage('cancel', input.reason), nowIso());
         });
         const refreshed = await loadRunState(runId);
@@ -529,16 +529,16 @@ export class OrchestrationExecutionRuntime {
         const changed = current.status !== input.status;
         await withOrchestrationTransaction(async (db) => {
             validateRunTransition(current.status, input.status);
-            db.prepare(`UPDATE orchestration_runs
-         SET status = ?, started_at = ?, finished_at = ?
+            db.prepare(`UPDATE orchestration_runs
+         SET status = ?, started_at = ?, finished_at = ?
          WHERE id = ?`).run(input.status, input.startedAt === undefined
                 ? current.startedAt
                 : toNullableText(input.startedAt), input.finishedAt === undefined
                 ? current.finishedAt
                 : toNullableText(input.finishedAt), runId);
             if (input.note) {
-                db.prepare(`INSERT INTO orchestration_messages (
-            id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
+                db.prepare(`INSERT INTO orchestration_messages (
+            id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
           ) VALUES (?, ?, ?, ?, ?, ?, ?, ?)`).run(randomUUID(), runId, null, null, null, 'run.transition', nowMessage('transition-run', input.note), nowIso());
             }
         });
@@ -561,8 +561,8 @@ export class OrchestrationExecutionRuntime {
         const changed = loaded.task.status !== input.status;
         await withOrchestrationTransaction(async (db) => {
             validateTaskTransition(loaded.task.status, input.status);
-            db.prepare(`UPDATE orchestration_tasks
-         SET status = ?, result_summary = ?, finished_at = ?
+            db.prepare(`UPDATE orchestration_tasks
+         SET status = ?, result_summary = ?, finished_at = ?
          WHERE id = ?`).run(input.status, input.resultSummary === undefined
                 ? loaded.task.resultSummary
                 : toNullableText(input.resultSummary), input.finishedAt === undefined
@@ -571,8 +571,8 @@ export class OrchestrationExecutionRuntime {
                     : null
                 : toNullableText(input.finishedAt), taskId);
             if (input.note) {
-                db.prepare(`INSERT INTO orchestration_messages (
-            id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
+                db.prepare(`INSERT INTO orchestration_messages (
+            id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
           ) VALUES (?, ?, ?, ?, ?, ?, ?, ?)`).run(randomUUID(), loaded.run.id, taskId, null, null, 'task.transition', nowMessage('transition-task', input.note), nowIso());
             }
         });
@@ -844,11 +844,11 @@ export class OrchestrationExecutionRuntime {
                 continue;
             }
             await withOrchestrationTransaction(async (db) => {
-                db.prepare(`UPDATE orchestration_tasks
-           SET status = ?, assigned_agent_id = ?, finished_at = NULL
+                db.prepare(`UPDATE orchestration_tasks
+           SET status = ?, assigned_agent_id = ?, finished_at = NULL
            WHERE id = ?`).run('in_progress', selectedAgentId, task.id);
-                db.prepare(`INSERT INTO orchestration_messages (
-            id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
+                db.prepare(`INSERT INTO orchestration_messages (
+            id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
           ) VALUES (?, ?, ?, ?, ?, ?, ?, ?)`).run(randomUUID(), runId, task.id, initial.run.globalOrchestratorAgentId, selectedAgentId, 'task.dispatch', `Equipo ${domainName}: tarea enviada a ${agent.name}.`, nowIso());
             });
             input.onProgress?.({
@@ -1010,11 +1010,11 @@ export class OrchestrationExecutionRuntime {
             ? report.generatedAt
             : null;
         await withOrchestrationTransaction(async (db) => {
-            db.prepare(`UPDATE orchestration_runs
-         SET status = ?, finished_at = ?
+            db.prepare(`UPDATE orchestration_runs
+         SET status = ?, finished_at = ?
          WHERE id = ?`).run(report.status, finishedAt, runId);
-            db.prepare(`INSERT INTO orchestration_messages (
-          id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
+            db.prepare(`INSERT INTO orchestration_messages (
+          id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
         ) VALUES (?, ?, ?, ?, ?, ?, ?, ?)`).run(randomUUID(), runId, null, null, state.run.globalOrchestratorAgentId, 'global.consolidated-report', report.summary, report.generatedAt);
         });
         await upsertOrchestrationRunReport({
@@ -1052,12 +1052,12 @@ export class OrchestrationExecutionRuntime {
         const db = await getOrchestrationDatabase();
         const id = randomUUID();
         const createdAt = nowIso();
-        db.prepare(`INSERT INTO orchestration_messages (
-        id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
+        db.prepare(`INSERT INTO orchestration_messages (
+        id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
       ) VALUES (?, ?, ?, ?, ?, ?, ?, ?)`).run(id, requireText(runId, 'runId'), toNullableText(taskId), toNullableText(fromAgentId), toNullableText(toAgentId), requireText(messageType, 'messageType'), requireText(content, 'content'), createdAt);
         const row = db
-            .prepare(`SELECT id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
-         FROM orchestration_messages
+            .prepare(`SELECT id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
+         FROM orchestration_messages
          WHERE id = ?`)
             .get(id);
         const created = rowToMessage(row);
@@ -1080,11 +1080,11 @@ export class OrchestrationExecutionRuntime {
                     finished_at: finishedAt,
                     result_summary: task.resultSummary ?? null,
                 });
-            db.prepare(`INSERT INTO orchestration_messages (
-          id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
+            db.prepare(`INSERT INTO orchestration_messages (
+          id, run_id, task_id, from_agent_id, to_agent_id, message_type, content, created_at
         ) VALUES (?, ?, ?, ?, ?, ?, ?, ?)`).run(randomUUID(), runId, null, null, null, 'run.block', nowMessage('cancel', reason), nowIso());
-            db.prepare(`UPDATE orchestration_runs
-         SET status = ?, finished_at = ?
+            db.prepare(`UPDATE orchestration_runs
+         SET status = ?, finished_at = ?
          WHERE id = ?`).run('cancelled', finishedAt, runId);
         });
         const refreshed = await loadRunState(runId);

package/dist/src/services/toolUseSummary/toolUseSummaryGenerator.js

@@ -10,15 +10,15 @@ import { logError } from '../../utils/log.js';
 import { jsonStringify } from '../../utils/slowOperations.js';
 import { asSystemPrompt } from '../../utils/systemPromptType.js';
 import { queryHaiku } from '../api/claude.js';
-const TOOL_USE_SUMMARY_SYSTEM_PROMPT = `Write a short summary label describing what these tool calls accomplished. It appears as a single-line row in a mobile app and truncates around 30 characters, so think git-commit-subject, not sentence.
-
-Keep the verb in past tense and the most distinctive noun. Drop articles, connectors, and long location context first.
-
-Examples:
-- Searched in auth/
-- Fixed NPE in UserService
-- Created signup endpoint
-- Read config.json
+const TOOL_USE_SUMMARY_SYSTEM_PROMPT = `Write a short summary label describing what these tool calls accomplished. It appears as a single-line row in a mobile app and truncates around 30 characters, so think git-commit-subject, not sentence.
+
+Keep the verb in past tense and the most distinctive noun. Drop articles, connectors, and long location context first.
+
+Examples:
+- Searched in auth/
+- Fixed NPE in UserService
+- Created signup endpoint
+- Read config.json
 - Ran failing tests`;
 /**
  * Generates a human-readable summary of completed tools.

package/dist/src/skills/bundled/batch.js

@@ -7,89 +7,89 @@ import { getIsGit } from '../../utils/git.js';
 import { registerBundledSkill } from '../bundledSkills.js';
 const MIN_AGENTS = 5;
 const MAX_AGENTS = 30;
-const WORKER_INSTRUCTIONS = `After you finish implementing the change:
-1. **Simplify** — Invoke the \`${SKILL_TOOL_NAME}\` tool with \`skill: "simplify"\` to review and clean up your changes.
-2. **Run unit tests** — Run the project's test suite (check for package.json scripts, Makefile targets, or common commands like \`npm test\`, \`bun test\`, \`pytest\`, \`go test\`). If tests fail, fix them.
-3. **Test end-to-end** — Follow the e2e test recipe from the coordinator's prompt (below). If the recipe says to skip e2e for this unit, skip it.
-4. **Commit and push** — Commit all changes with a clear message, push the branch, and create a PR with \`gh pr create\`. Use a descriptive title. If \`gh\` is not available or the push fails, note it in your final message.
+const WORKER_INSTRUCTIONS = `After you finish implementing the change:
+1. **Simplify** — Invoke the \`${SKILL_TOOL_NAME}\` tool with \`skill: "simplify"\` to review and clean up your changes.
+2. **Run unit tests** — Run the project's test suite (check for package.json scripts, Makefile targets, or common commands like \`npm test\`, \`bun test\`, \`pytest\`, \`go test\`). If tests fail, fix them.
+3. **Test end-to-end** — Follow the e2e test recipe from the coordinator's prompt (below). If the recipe says to skip e2e for this unit, skip it.
+4. **Commit and push** — Commit all changes with a clear message, push the branch, and create a PR with \`gh pr create\`. Use a descriptive title. If \`gh\` is not available or the push fails, note it in your final message.
 5. **Report** — End with a single line: \`PR: <url>\` so the coordinator can track it. If no PR was created, end with \`PR: none — <reason>\`.`;
 function buildPrompt(instruction) {
-    return `# Batch: Parallel Work Orchestration
-
-You are orchestrating a large, parallelizable change across this codebase.
-
-## User Instruction
-
-${instruction}
-
-## Phase 1: Research and Plan (Plan Mode)
-
-Call the \`${ENTER_PLAN_MODE_TOOL_NAME}\` tool now to enter plan mode, then:
-
-1. **Understand the scope.** Launch one or more subagents (in the foreground — you need their results) to deeply research what this instruction touches. Find all the files, patterns, and call sites that need to change. Understand the existing conventions so the migration is consistent.
-
-2. **Decompose into independent units.** Break the work into ${MIN_AGENTS}–${MAX_AGENTS} self-contained units. Each unit must:
-   - Be independently implementable in an isolated git worktree (no shared state with sibling units)
-   - Be mergeable on its own without depending on another unit's PR landing first
-   - Be roughly uniform in size (split large units, merge trivial ones)
-
-   Scale the count to the actual work: few files → closer to ${MIN_AGENTS}; hundreds of files → closer to ${MAX_AGENTS}. Prefer per-directory or per-module slicing over arbitrary file lists.
-
-3. **Determine the e2e test recipe.** Figure out how a worker can verify its change actually works end-to-end — not just that unit tests pass. Look for:
-   - A \`claude-in-chrome\` skill or browser-automation tool (for UI changes: click through the affected flow, screenshot the result)
-   - A \`tmux\` or CLI-verifier skill (for CLI changes: launch the app interactively, exercise the changed behavior)
-   - A dev-server + curl pattern (for API changes: start the server, hit the affected endpoints)
-   - An existing e2e/integration test suite the worker can run
-
-   If you cannot find a concrete e2e path, use the \`${ASK_USER_QUESTION_TOOL_NAME}\` tool to ask the user how to verify this change end-to-end. Offer 2–3 specific options based on what you found (e.g., "Screenshot via chrome extension", "Run \`bun run dev\` and curl the endpoint", "No e2e — unit tests are sufficient"). Do not skip this — the workers cannot ask the user themselves.
-
-   Write the recipe as a short, concrete set of steps that a worker can execute autonomously. Include any setup (start a dev server, build first) and the exact command/interaction to verify.
-
-4. **Write the plan.** In your plan file, include:
-   - A summary of what you found during research
-   - A numbered list of work units — for each: a short title, the list of files/directories it covers, and a one-line description of the change
-   - The e2e test recipe (or "skip e2e because …" if the user chose that)
-   - The exact worker instructions you will give each agent (the shared template)
-
-5. Call \`${EXIT_PLAN_MODE_TOOL_NAME}\` to present the plan for approval.
-
-## Phase 2: Spawn Workers (After Plan Approval)
-
-Once the plan is approved, spawn one background agent per work unit using the \`${AGENT_TOOL_NAME}\` tool. **All agents must use \`isolation: "worktree"\` and \`run_in_background: true\`.** Launch them all in a single message block so they run in parallel.
-
-For each agent, the prompt must be fully self-contained. Include:
-- The overall goal (the user's instruction)
-- This unit's specific task (title, file list, change description — copied verbatim from your plan)
-- Any codebase conventions you discovered that the worker needs to follow
-- The e2e test recipe from your plan (or "skip e2e because …")
-- The worker instructions below, copied verbatim:
-
-\`\`\`
-${WORKER_INSTRUCTIONS}
-\`\`\`
-
-Use \`subagent_type: "general-purpose"\` unless a more specific agent type fits.
-
-## Phase 3: Track Progress
-
-After launching all workers, render an initial status table:
-
-| # | Unit | Status | PR |
-|---|------|--------|----|
-| 1 | <title> | running | — |
-| 2 | <title> | running | — |
-
-As background-agent completion notifications arrive, parse the \`PR: <url>\` line from each agent's result and re-render the table with updated status (\`done\` / \`failed\`) and PR links. Keep a brief failure note for any agent that did not produce a PR.
-
-When all agents have reported, render the final table and a one-line summary (e.g., "22/24 units landed as PRs").
+    return `# Batch: Parallel Work Orchestration
+
+You are orchestrating a large, parallelizable change across this codebase.
+
+## User Instruction
+
+${instruction}
+
+## Phase 1: Research and Plan (Plan Mode)
+
+Call the \`${ENTER_PLAN_MODE_TOOL_NAME}\` tool now to enter plan mode, then:
+
+1. **Understand the scope.** Launch one or more subagents (in the foreground — you need their results) to deeply research what this instruction touches. Find all the files, patterns, and call sites that need to change. Understand the existing conventions so the migration is consistent.
+
+2. **Decompose into independent units.** Break the work into ${MIN_AGENTS}–${MAX_AGENTS} self-contained units. Each unit must:
+   - Be independently implementable in an isolated git worktree (no shared state with sibling units)
+   - Be mergeable on its own without depending on another unit's PR landing first
+   - Be roughly uniform in size (split large units, merge trivial ones)
+
+   Scale the count to the actual work: few files → closer to ${MIN_AGENTS}; hundreds of files → closer to ${MAX_AGENTS}. Prefer per-directory or per-module slicing over arbitrary file lists.
+
+3. **Determine the e2e test recipe.** Figure out how a worker can verify its change actually works end-to-end — not just that unit tests pass. Look for:
+   - A \`claude-in-chrome\` skill or browser-automation tool (for UI changes: click through the affected flow, screenshot the result)
+   - A \`tmux\` or CLI-verifier skill (for CLI changes: launch the app interactively, exercise the changed behavior)
+   - A dev-server + curl pattern (for API changes: start the server, hit the affected endpoints)
+   - An existing e2e/integration test suite the worker can run
+
+   If you cannot find a concrete e2e path, use the \`${ASK_USER_QUESTION_TOOL_NAME}\` tool to ask the user how to verify this change end-to-end. Offer 2–3 specific options based on what you found (e.g., "Screenshot via chrome extension", "Run \`bun run dev\` and curl the endpoint", "No e2e — unit tests are sufficient"). Do not skip this — the workers cannot ask the user themselves.
+
+   Write the recipe as a short, concrete set of steps that a worker can execute autonomously. Include any setup (start a dev server, build first) and the exact command/interaction to verify.
+
+4. **Write the plan.** In your plan file, include:
+   - A summary of what you found during research
+   - A numbered list of work units — for each: a short title, the list of files/directories it covers, and a one-line description of the change
+   - The e2e test recipe (or "skip e2e because …" if the user chose that)
+   - The exact worker instructions you will give each agent (the shared template)
+
+5. Call \`${EXIT_PLAN_MODE_TOOL_NAME}\` to present the plan for approval.
+
+## Phase 2: Spawn Workers (After Plan Approval)
+
+Once the plan is approved, spawn one background agent per work unit using the \`${AGENT_TOOL_NAME}\` tool. **All agents must use \`isolation: "worktree"\` and \`run_in_background: true\`.** Launch them all in a single message block so they run in parallel.
+
+For each agent, the prompt must be fully self-contained. Include:
+- The overall goal (the user's instruction)
+- This unit's specific task (title, file list, change description — copied verbatim from your plan)
+- Any codebase conventions you discovered that the worker needs to follow
+- The e2e test recipe from your plan (or "skip e2e because …")
+- The worker instructions below, copied verbatim:
+
+\`\`\`
+${WORKER_INSTRUCTIONS}
+\`\`\`
+
+Use \`subagent_type: "general-purpose"\` unless a more specific agent type fits.
+
+## Phase 3: Track Progress
+
+After launching all workers, render an initial status table:
+
+| # | Unit | Status | PR |
+|---|------|--------|----|
+| 1 | <title> | running | — |
+| 2 | <title> | running | — |
+
+As background-agent completion notifications arrive, parse the \`PR: <url>\` line from each agent's result and re-render the table with updated status (\`done\` / \`failed\`) and PR links. Keep a brief failure note for any agent that did not produce a PR.
+
+When all agents have reported, render the final table and a one-line summary (e.g., "22/24 units landed as PRs").
 `;
 }
 const NOT_A_GIT_REPO_MESSAGE = `This is not a git repository. The \`/batch\` command requires a git repo because it spawns agents in isolated git worktrees and creates PRs from each. Initialize a repo first, or run this from inside an existing one.`;
-const MISSING_INSTRUCTION_MESSAGE = `Provide an instruction describing the batch change you want to make.
-
-Examples:
-  /batch migrate from react to vue
-  /batch replace all uses of lodash with native equivalents
+const MISSING_INSTRUCTION_MESSAGE = `Provide an instruction describing the batch change you want to make.
+
+Examples:
+  /batch migrate from react to vue
+  /batch replace all uses of lodash with native equivalents
   /batch add type annotations to all untyped function parameters`;
 export function registerBatchSkill() {
     registerBundledSkill({

package/dist/src/skills/bundled/claudeApi.js

@@ -60,40 +60,40 @@ function buildInlineReference(filePaths, content) {
     }
     return sections.join('\n\n');
 }
-const INLINE_READING_GUIDE = `## Reference Documentation
-
-The relevant documentation for your detected language is included below in \`<doc>\` tags. Each tag has a \`path\` attribute showing its original file path. Use this to find the right section:
-
-### Quick Task Reference
-
-**Single text classification/summarization/extraction/Q&A:**
-→ Refer to \`{lang}/claude-api/README.md\`
-
-**Chat UI or real-time response display:**
-→ Refer to \`{lang}/claude-api/README.md\` + \`{lang}/claude-api/streaming.md\`
-
-**Long-running conversations (may exceed context window):**
-→ Refer to \`{lang}/claude-api/README.md\` — see Compaction section
-
-**Prompt caching / optimize caching / "why is my cache hit rate low":**
-→ Refer to \`shared/prompt-caching.md\` + \`{lang}/claude-api/README.md\` (Prompt Caching section)
-
-**Function calling / tool use / agents:**
-→ Refer to \`{lang}/claude-api/README.md\` + \`shared/tool-use-concepts.md\` + \`{lang}/claude-api/tool-use.md\`
-
-**Batch processing (non-latency-sensitive):**
-→ Refer to \`{lang}/claude-api/README.md\` + \`{lang}/claude-api/batches.md\`
-
-**File uploads across multiple requests:**
-→ Refer to \`{lang}/claude-api/README.md\` + \`{lang}/claude-api/files-api.md\`
-
-**Agent with built-in tools (file/web/terminal) (Python & TypeScript only):**
-→ Refer to \`{lang}/agent-sdk/README.md\` + \`{lang}/agent-sdk/patterns.md\`
-
-**Error handling:**
-→ Refer to \`shared/error-codes.md\`
-
-**Latest docs via WebFetch:**
+const INLINE_READING_GUIDE = `## Reference Documentation
+
+The relevant documentation for your detected language is included below in \`<doc>\` tags. Each tag has a \`path\` attribute showing its original file path. Use this to find the right section:
+
+### Quick Task Reference
+
+**Single text classification/summarization/extraction/Q&A:**
+→ Refer to \`{lang}/claude-api/README.md\`
+
+**Chat UI or real-time response display:**
+→ Refer to \`{lang}/claude-api/README.md\` + \`{lang}/claude-api/streaming.md\`
+
+**Long-running conversations (may exceed context window):**
+→ Refer to \`{lang}/claude-api/README.md\` — see Compaction section
+
+**Prompt caching / optimize caching / "why is my cache hit rate low":**
+→ Refer to \`shared/prompt-caching.md\` + \`{lang}/claude-api/README.md\` (Prompt Caching section)
+
+**Function calling / tool use / agents:**
+→ Refer to \`{lang}/claude-api/README.md\` + \`shared/tool-use-concepts.md\` + \`{lang}/claude-api/tool-use.md\`
+
+**Batch processing (non-latency-sensitive):**
+→ Refer to \`{lang}/claude-api/README.md\` + \`{lang}/claude-api/batches.md\`
+
+**File uploads across multiple requests:**
+→ Refer to \`{lang}/claude-api/README.md\` + \`{lang}/claude-api/files-api.md\`
+
+**Agent with built-in tools (file/web/terminal) (Python & TypeScript only):**
+→ Refer to \`{lang}/agent-sdk/README.md\` + \`{lang}/agent-sdk/patterns.md\`
+
+**Error handling:**
+→ Refer to \`shared/error-codes.md\`
+
+**Latest docs via WebFetch:**
 → Refer to \`shared/live-sources.md\` for URLs`;
 function buildPrompt(lang, args, content) {
     // Take the SKILL.md content up to the "Reading Guide" section

package/dist/src/skills/bundled/claudeInChrome.js

@@ -3,10 +3,10 @@ import { BASE_CHROME_PROMPT } from '../../utils/claudeInChrome/prompt.js';
 import { shouldAutoEnableClaudeInChrome } from '../../utils/claudeInChrome/setup.js';
 import { registerBundledSkill } from '../bundledSkills.js';
 const CLAUDE_IN_CHROME_MCP_TOOLS = BROWSER_TOOLS.map(tool => `mcp__claude-in-chrome__${tool.name}`);
-const SKILL_ACTIVATION_MESSAGE = `
-Now that this skill is invoked, you have access to Chrome browser automation tools. You can now use the mcp__claude-in-chrome__* tools to interact with web pages.
-
-IMPORTANT: Start by calling mcp__claude-in-chrome__tabs_context_mcp to get information about the user's current browser tabs.
+const SKILL_ACTIVATION_MESSAGE = `
+Now that this skill is invoked, you have access to Chrome browser automation tools. You can now use the mcp__claude-in-chrome__* tools to interact with web pages.
+
+IMPORTANT: Start by calling mcp__claude-in-chrome__tabs_context_mcp to get information about the user's current browser tabs.
 `;
 export function registerClaudeInChromeSkill() {
     registerBundledSkill({

package/dist/src/skills/bundled/debug.js

@@ -55,43 +55,43 @@ export function registerDebugSkill() {
             }
             const justEnabledSection = wasAlreadyLogging
                 ? ''
-                : `
-## Debug Logging Just Enabled
-
-Debug logging was OFF for this session until now. Nothing prior to this /debug invocation was captured.
-
-Tell the user that debug logging is now active at \`${debugLogPath}\`, ask them to reproduce the issue, then re-read the log. If they can't reproduce, they can also restart with \`claude --debug\` to capture logs from startup.
+                : `
+## Debug Logging Just Enabled
+
+Debug logging was OFF for this session until now. Nothing prior to this /debug invocation was captured.
+
+Tell the user that debug logging is now active at \`${debugLogPath}\`, ask them to reproduce the issue, then re-read the log. If they can't reproduce, they can also restart with \`claude --debug\` to capture logs from startup.
 `;
-            const prompt = `# Debug Skill
-
-Help the user debug an issue they're encountering in this current Context Code session.
-${justEnabledSection}
-## Session Debug Log
-
-The debug log for the current session is at: \`${debugLogPath}\`
-
-${logInfo}
-
-For additional context, grep for [ERROR] and [WARN] lines across the full file.
-
-## Issue Description
-
-${args || 'The user did not describe a specific issue. Read the debug log and summarize any errors, warnings, or notable issues.'}
-
-## Settings
-
-Remember that settings are in:
-* user - ${getSettingsFilePathForSource('userSettings')}
-* project - ${getSettingsFilePathForSource('projectSettings')}
-* local - ${getSettingsFilePathForSource('localSettings')}
-
-## Instructions
-
-1. Review the user's issue description
-2. The last ${DEFAULT_DEBUG_LINES_READ} lines show the debug file format. Look for [ERROR] and [WARN] entries, stack traces, and failure patterns across the file
-3. Consider launching the ${CLAUDE_CODE_GUIDE_AGENT_TYPE} subagent to understand the relevant Context Code features
-4. Explain what you found in plain language
-5. Suggest concrete fixes or next steps
+            const prompt = `# Debug Skill
+
+Help the user debug an issue they're encountering in this current Context Code session.
+${justEnabledSection}
+## Session Debug Log
+
+The debug log for the current session is at: \`${debugLogPath}\`
+
+${logInfo}
+
+For additional context, grep for [ERROR] and [WARN] lines across the full file.
+
+## Issue Description
+
+${args || 'The user did not describe a specific issue. Read the debug log and summarize any errors, warnings, or notable issues.'}
+
+## Settings
+
+Remember that settings are in:
+* user - ${getSettingsFilePathForSource('userSettings')}
+* project - ${getSettingsFilePathForSource('projectSettings')}
+* local - ${getSettingsFilePathForSource('localSettings')}
+
+## Instructions
+
+1. Review the user's issue description
+2. The last ${DEFAULT_DEBUG_LINES_READ} lines show the debug file format. Look for [ERROR] and [WARN] entries, stack traces, and failure patterns across the file
+3. Consider launching the ${CLAUDE_CODE_GUIDE_AGENT_TYPE} subagent to understand the relevant Context Code features
+4. Explain what you found in plain language
+5. Suggest concrete fixes or next steps
 `;
             return [{ type: 'text', text: prompt }];
         },