opencode-conductor-plugin 1.24.0 → 1.25.0

package/README.md

@@ -11,7 +11,7 @@ The philosophy is simple: **control your code by controlling your context.** By
 ## 🚀 Key Features
 
 *   **Specialized `@conductor` Agent**: A dedicated subagent that acts as your Project Architect and Technical Lead.
-*   **Native Slash Commands**: Integrated shortcuts like `/conductor_setup`, `/conductor_newTrack`, and `/conductor_implement` for frictionless project management.
+*   **Native Slash Commands**: Integrated shortcuts like `/conductor:setup`, `/conductor:newTrack`, and `/conductor:implement` for frictionless project management.
 *   **Modern Permissions**: Fully compatible with OpenCode v1.1.1 granular permission system.
 *   **Protocol-Driven Workflow**: Automated enforcement of the **Context -> Spec -> Plan -> Implement** lifecycle.
 *   **Smart Revert**: A Git-aware revert system that understands logical units of work (Tracks, Phases, Tasks) instead of just raw commit hashes.
@@ -26,18 +26,18 @@ The philosophy is simple: **control your code by controlling your context.** By
 
 Conductor organizes your work into **Tracks** (features or bug fixes). Every Track follows three mandatory phases:
 
-### 1. Project Initialization (`/conductor_setup`)
+### 1. Project Initialization (`/conductor:setup`)
 Run this once per project. The agent will interview you to define:
 *   **Product Vision**: Target users, core goals, and primary features.
 *   **Tech Stack**: Languages, frameworks, and databases.
 *   **Workflow Rules**: Testing standards (e.g., TDD), commit strategies, and documentation patterns.
 
-### 2. Track Planning (`/conductor_newTrack`)
+### 2. Track Planning (`/conductor:newTrack`)
 When you're ready for a new task, tell the agent what you want to build.
 *   **Specification (`spec.md`)**: Conductor asks 3-5 targeted questions to clarify the "What" and "Why".
 *   **Implementation Plan (`plan.md`)**: Once the spec is approved, Conductor generates a step-by-step checklist adhering to your project's workflow rules.
 
-### 3. Autonomous Implementation (`/conductor_implement`)
+### 3. Autonomous Implementation (`/conductor:implement`)
 The agent works through the `plan.md` checklist, executing tasks, running tests, and making semantic commits automatically until the Track is complete.
 
 ---
@@ -94,11 +94,11 @@ We highly recommend pinning the `@conductor` agent to a "flash" model for optima
 
 | Command | Description |
 | :--- | :--- |
-| `/conductor_setup` | Initialize the `conductor/` directory and project "Constitution". |
-| `/conductor_newTrack "desc"` | Start a new feature/bug Track with spec and plan generation. |
-| `/conductor_implement` | Start implementing the next pending task in the current track. |
-| `/conductor_status` | Get a high-level overview of project progress and active tracks. |
-| `/conductor_revert` | Interactively select a task, phase, or track to undo via Git. |
+| `/conductor:setup` | Initialize the `conductor/` directory and project "Constitution". |
+| `/conductor:newTrack "desc"` | Start a new feature/bug Track with spec and plan generation. |
+| `/conductor:implement` | Start implementing the next pending task in the current track. |
+| `/conductor:status` | Get a high-level overview of project progress and active tracks. |
+| `/conductor:revert` | Interactively select a task, phase, or track to undo via Git. |
 
 ---
 

package/dist/commands/implement.d.ts

@@ -0,0 +1 @@
+export declare const implementCommand: (ctx: any) => import("@opencode-ai/plugin/tool").ToolDefinition;

package/dist/commands/implement.js

@@ -0,0 +1,31 @@
+import { tool } from "@opencode-ai/plugin/tool";
+import { createConductorCommand } from "../utils/commandFactory.js";
+import { join, dirname } from "path";
+import { fileURLToPath } from "url";
+import { readFile } from "fs/promises";
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = dirname(__filename);
+export const implementCommand = createConductorCommand({
+    name: "implement.toml",
+    description: "Implements tasks from a Conductor track.",
+    args: {
+        track_name: tool.schema.string().optional().describe("Specific track to implement. If omitted, selects the next incomplete track."),
+    },
+    additionalContext: async (ctx, args) => {
+        // 1. Choose strategy based on OMO activity
+        const strategyFile = ctx.isOMOActive ? "delegate.md" : "manual.md";
+        const strategyPath = join(__dirname, "../prompts/strategies", strategyFile);
+        let strategySection = "";
+        try {
+            strategySection = await readFile(strategyPath, "utf-8");
+        }
+        catch (e) {
+            console.warn(`[Conductor] Failed to load strategy ${strategyFile}:`, e);
+            strategySection = "Error: Could not load execution strategy.";
+        }
+        return {
+            strategy_section: strategySection,
+            track_name: args.track_name || ""
+        };
+    }
+});

package/dist/commands/newTrack.d.ts

@@ -0,0 +1 @@
+export declare const newTrackCommand: (ctx: any) => import("@opencode-ai/plugin/tool").ToolDefinition;

package/dist/commands/newTrack.js

@@ -0,0 +1,12 @@
+import { tool } from "@opencode-ai/plugin/tool";
+import { createConductorCommand } from "../utils/commandFactory.js";
+export const newTrackCommand = createConductorCommand({
+    name: "newTrack.toml",
+    description: "Creates a new track (feature/bug) in the Conductor system. IMPORTANT: Do NOT create any todos using 'todowrite' or 'task' tools before or during this command, as it manages its own interactive state and will conflict with continuation enforcers.",
+    args: {
+        description: tool.schema.string().optional().describe("Brief description of the track."),
+    },
+    additionalContext: async (_, args) => ({
+        args: args.description || ""
+    })
+});

package/dist/commands/revert.d.ts

@@ -0,0 +1 @@
+export declare const revertCommand: (ctx: any) => import("@opencode-ai/plugin/tool").ToolDefinition;

package/dist/commands/revert.js

@@ -0,0 +1,9 @@
+import { createConductorCommand } from "../utils/commandFactory.js";
+import { tool } from "@opencode-ai/plugin/tool";
+export const revertCommand = createConductorCommand({
+    name: "revert.toml",
+    description: "Reverts a Conductor track, phase, or task.",
+    args: {
+        target: tool.schema.string().optional().describe("ID or description of what to revert."),
+    }
+});

package/dist/commands/setup.d.ts

@@ -0,0 +1 @@
+export declare const setupCommand: (ctx: any) => import("@opencode-ai/plugin/tool").ToolDefinition;

package/dist/commands/setup.js

@@ -0,0 +1,10 @@
+import { tool } from "@opencode-ai/plugin/tool";
+import { createConductorCommand } from "../utils/commandFactory.js";
+export const setupCommand = createConductorCommand({
+    name: "setup.toml",
+    description: "Sets up the Conductor environment for the project. Call this to start or resume the setup process. IMPORTANT: Do NOT create any todos using 'todowrite' or 'task' tools before or during this command, as it manages its own interactive state and will conflict with continuation enforcers.",
+    args: {
+        user_input: tool.schema.string().optional().describe("The user's response to a previous question, if applicable."),
+    },
+    requiresSetup: false // Setup command is what creates the setup
+});

package/dist/commands/status.d.ts

@@ -0,0 +1 @@
+export declare const statusCommand: (ctx: any) => import("@opencode-ai/plugin/tool").ToolDefinition;

package/dist/commands/status.js

@@ -0,0 +1,6 @@
+import { createConductorCommand } from "../utils/commandFactory.js";
+export const statusCommand = createConductorCommand({
+    name: "status.toml",
+    description: "Shows the status of Conductor tracks.",
+    args: {}
+});

package/dist/index.js

@@ -1,223 +1,94 @@
+import { setupCommand } from "./commands/setup.js";
+import { newTrackCommand } from "./commands/newTrack.js";
+import { implementCommand } from "./commands/implement.js";
+import { statusCommand } from "./commands/status.js";
+import { revertCommand } from "./commands/revert.js";
 import { join, dirname } from "path";
-import { existsSync } from "fs";
+import { homedir } from "os";
+import { existsSync, readFileSync } from "fs";
 import { readFile } from "fs/promises";
 import { fileURLToPath } from "url";
-import { createDelegationTool } from "./tools/delegate.js";
-import { BackgroundManager, createBackgroundTask, createBackgroundOutput, createBackgroundCancel, } from "./tools/background.js";
-import { createSetupTool, createNewTrackTool, createImplementTool, createStatusTool, createRevertTool, } from "./tools/commands.js";
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = dirname(__filename);
-const safeRead = async (path) => {
-    try {
-        if (existsSync(path))
-            return await readFile(path, "utf-8");
-    }
-    catch (e) { }
-    return null;
-};
 const ConductorPlugin = async (ctx) => {
+    // Detect oh-my-opencode for synergy features
+    const configPath = join(homedir(), ".config", "opencode", "opencode.json");
+    let isOMOActive = false;
     try {
-        console.log("[Conductor] Initializing plugin...");
-        const backgroundManager = new BackgroundManager(ctx);
-        // 1. Helper to load and process prompt templates (Manual TOML Parsing)
-        const loadPrompt = async (filename, replacements = {}) => {
-            const promptPath = join(__dirname, "prompts", filename);
-            try {
-                const content = await readFile(promptPath, "utf-8");
-                const descMatch = content.match(/description\s*=\s*"([^"]+)"/);
-                const description = descMatch ? descMatch[1] : "Conductor Command";
-                const promptMatch = content.match(/prompt\s*=\s*"""([\s\S]*?)"""/);
-                let promptText = promptMatch ? promptMatch[1] : "";
-                if (!promptText)
-                    throw new Error(`Could not parse prompt text from ${filename}`);
-                const defaults = {
-                    templatesDir: join(dirname(__dirname), "templates"),
-                };
-                const finalReplacements = { ...defaults, ...replacements };
-                for (const [key, value] of Object.entries(finalReplacements)) {
-                    promptText = promptText.replaceAll(`{{${key}}}`, value || "");
-                }
-                return { prompt: promptText, description: description };
-            }
-            catch (error) {
-                console.error(`[Conductor] Error loading prompt ${filename}:`, error);
-                return {
-                    prompt: `SYSTEM ERROR: Failed to load prompt ${filename}`,
-                    description: "Error loading command",
-                };
-            }
-        };
-        // 3. Load all Command Prompts (Parallel)
-        const [setup, newTrack, implement, status, revert] = await Promise.all([
-            loadPrompt("setup.toml"),
-            loadPrompt("newTrack.toml", { args: "$ARGUMENTS" }),
-            loadPrompt("implement.toml", {
-                track_name: "$ARGUMENTS",
-            }),
-            loadPrompt("status.toml"),
-            loadPrompt("revert.toml", { target: "$ARGUMENTS" }),
-            safeRead(join(ctx.directory, "conductor", "workflow.md")),
-        ]);
-        // 4. Extract Agent Prompts
-        const [conductorMd, implementerMd] = await Promise.all([
-            readFile(join(__dirname, "prompts", "agent", "conductor.md"), "utf-8"),
-            readFile(join(__dirname, "prompts", "agent", "implementer.md"), "utf-8"),
-        ]);
-        const conductorPrompt = conductorMd.split("---").pop()?.trim() || "";
-        const implementerPrompt = implementerMd.split("---").pop()?.trim() || "";
-        console.log("[Conductor] All components ready. Injecting config...");
-        return {
-            tool: {
-                ...(ctx.client.tool || {}),
-                "conductor_delegate": createDelegationTool(ctx),
-                "conductor_bg_task": createBackgroundTask(backgroundManager),
-                "conductor_bg_output": createBackgroundOutput(backgroundManager),
-                "conductor_bg_cancel": createBackgroundCancel(backgroundManager),
-                "conductor_setup": createSetupTool(ctx),
-                "conductor_newTrack": createNewTrackTool(ctx),
-                "conductor_implement": createImplementTool(ctx),
-                "conductor_status": createStatusTool(ctx),
-                "conductor_revert": createRevertTool(ctx),
-            },
-            config: async (config) => {
-                if (!config)
-                    return;
-                console.log("[Conductor] config handler: Merging commands and agents...");
-                config.command = {
-                    ...(config.command || {}),
-                    "conductor_setup": {
-                        template: "Use the conductor_setup tool to scaffold the project and set up the Conductor environment. After calling the tool, you MUST follow all instructions provided in the tool's response exactly as specified.",
-                        description: setup.description,
-                        agent: "conductor",
-                    },
-                    "conductor_newTrack": {
-                        template: "Use the conductor_newTrack tool to plan a track and generate track-specific spec documents. If arguments were provided with this command, pass them as the 'description' parameter to the tool. After calling the tool, you MUST follow all instructions provided in the tool's response exactly as specified.",
-                        description: newTrack.description,
-                        agent: "conductor",
-                    },
-                    "conductor_implement": {
-                        template: "Use the conductor_implement tool to execute the tasks defined in the specified track's plan. If a track name was provided as an argument with this command, pass it as the 'track_name' parameter to the tool. After calling the tool, you MUST follow all instructions provided in the tool's response exactly as specified.",
-                        description: implement.description,
-                        agent: "conductor_implementer",
-                    },
-                    "conductor_status": {
-                        template: "Use the conductor_status tool to display the current progress of the project. After calling the tool, you MUST follow all instructions provided in the tool's response exactly as specified.",
-                        description: status.description,
-                        agent: "conductor",
-                    },
-                    "conductor_revert": {
-                        template: "Use the conductor_revert tool to revert previous work. If a target was provided as an argument with this command (e.g., 'track <track_id>', 'phase <phase_name>', 'task <task_name>'), pass it as the 'target' parameter to the tool. After calling the tool, you MUST follow all instructions provided in the tool's response exactly as specified.",
-                        description: revert.description,
-                        agent: "conductor",
-                    },
-                };
-                config.agent = {
-                    ...(config.agent || {}),
-                    conductor: {
-                        description: "Conductor Protocol Steward.",
-                        mode: "primary",
-                        prompt: conductorPrompt,
-                        permission: {
-                            '*': 'allow',
-                            read: {
-                                "*": "allow",
-                                "*.env": "deny",
-                                "*.env.*": "deny",
-                                "*.env.example": "allow",
-                            },
-                            edit: "allow",
-                            bash: "allow",
-                            grep: "allow",
-                            glob: "allow",
-                            lsp: "allow",
-                            todoread: "allow",
-                            todowrite: "allow",
-                            webfetch: "allow",
-                            "conductor_setup": "allow",
-                            "conductor_newTrack": "allow",
-                            "conductor_implement": "allow",
-                            "conductor_status": "allow",
-                            "conductor_revert": "allow",
-                            external_directory: "deny",
-                            doom_loop: "ask",
-                        },
-                    },
-                    conductor_implementer: {
-                        description: "Conductor Protocol Implementer.",
-                        mode: "primary",
-                        prompt: implementerPrompt,
-                        permission: {
-                            '*': 'allow',
-                            read: {
-                                "*": "allow",
-                                "*.env": "deny",
-                                "*.env.*": "deny",
-                                "*.env.example": "allow",
-                            },
-                            edit: "allow",
-                            bash: "allow",
-                            grep: "allow",
-                            glob: "allow",
-                            lsp: "allow",
-                            todoread: "allow",
-                            todowrite: "allow",
-                            webfetch: "allow",
-                            "conductor_delegate": "allow",
-                            "conductor_bg_task": "allow",
-                            "conductor_bg_output": "allow",
-                            "conductor_bg_cancel": "allow",
-                            "conductor_setup": "allow",
-                            "conductor_newTrack": "allow",
-                            "conductor_implement": "allow",
-                            "conductor_status": "allow",
-                            "conductor_revert": "allow",
-                            external_directory: "deny",
-                            doom_loop: "ask",
-                        },
-                    },
-                };
-            },
-            // "tool.execute.before": async (input, output) => {
-            //   const delegationTools = [
-            //     "delegate_to_agent",
-            //     "task",
-            //     "background_task",
-            //     "conductor_delegate",
-            //     "conductor_bg_task",
-            //   ];
-            //   if (delegationTools.includes(input.tool)) {
-            //     const conductorDir = join(ctx.directory, "conductor");
-            //     const workflowMd = await safeRead(join(conductorDir, "workflow.md"));
-            //     if (workflowMd) {
-            //       let injection = "\n\n--- [SYSTEM INJECTION: CONDUCTOR CONTEXT PACKET] ---\n";
-            //       injection +=
-            //         "You are receiving this task from the Conductor.\n";
-            //       injection +=
-            //         "You MUST adhere to the following project workflow rules:\n";
-            //       injection += "\n### DEVELOPMENT WORKFLOW\n" + workflowMd + "\n";
-            //       if (implement?.prompt) {
-            //         injection +=
-            //           "\n### IMPLEMENTATION PROTOCOL\n" + implement.prompt + "\n";
-            //       }
-            //       injection +=
-            //         "\n### DELEGATED AUTHORITY\n- **EXECUTE:** Implement the requested task.\n- **REFINE:** You have authority to update `plan.md` and `spec.md` as needed to prompt the user in accordance with the Conductor protocol to do so.\n";
-            //       injection += "--- [END INJECTION] ---\n";
-            //       // Inject into the primary instruction field depending on the tool's schema
-            //       if (typeof output.args.objective === "string") {
-            //         output.args.objective += injection;
-            //       } else if (typeof output.args.prompt === "string") {
-            //         output.args.prompt += injection;
-            //       } else if (typeof output.args.instruction === "string") {
-            //         output.args.instruction += injection;
-            //       }
-            //     }
-            //   }
-            // },
-        };
+        if (existsSync(configPath)) {
+            const config = JSON.parse(readFileSync(configPath, "utf-8"));
+            isOMOActive = config.plugin?.some((p) => p.includes("oh-my-opencode"));
+        }
     }
-    catch (err) {
-        console.error("[Conductor] FATAL: Plugin initialization failed:", err);
-        throw err;
+    catch (e) {
+        // Fallback to filesystem check if config read fails
+        const omoPath = join(homedir(), ".config", "opencode", "node_modules", "oh-my-opencode");
+        isOMOActive = existsSync(omoPath);
     }
+    console.log(`[Conductor] Plugin tools loaded. (OMO Synergy: ${isOMOActive ? "Enabled" : "Disabled"})`);
+    const extendedCtx = { ...ctx, isOMOActive };
+    return {
+        tool: {
+            conductor_setup: setupCommand(extendedCtx),
+            conductor_new_track: newTrackCommand(extendedCtx),
+            conductor_implement: implementCommand(extendedCtx),
+            conductor_status: statusCommand(extendedCtx),
+            conductor_revert: revertCommand(extendedCtx),
+        },
+        "tool.execute.before": async (input, output) => {
+            // INTERCEPT: Sisyphus Delegation Hook
+            // Purpose: Automatically inject the full Conductor context (Plan, Spec, Workflow, Protocol)
+            // whenever the Conductor delegates a task to Sisyphus. This ensures Sisyphus has "Engineering Authority"
+            // without needing the LLM to manually copy-paste huge context blocks.
+            if (input.tool === "delegate_to_agent") {
+                const agentName = (output.args.agent_name || output.args.agent || "").toLowerCase();
+                if (agentName.includes("sisyphus")) {
+                    console.log("[Conductor] Intercepting Sisyphus delegation. Injecting Context Packet...");
+                    const conductorDir = join(ctx.directory, "conductor");
+                    const promptsDir = join(__dirname, "prompts");
+                    // Helper to safely read file content
+                    const safeRead = async (path) => {
+                        try {
+                            if (existsSync(path))
+                                return await readFile(path, "utf-8");
+                        }
+                        catch (e) { /* ignore */ }
+                        return null;
+                    };
+                    // 1. Read Project Context Files
+                    // We need to find the active track to get the correct spec/plan.
+                    // Since we don't know the track ID easily here, we look for the 'plan.md' that might be in the args
+                    // OR we just rely on the Conductor having already done the setup. 
+                    // WAIT: We can't easily guess the track ID here. 
+                    // BETTER APPROACH: We rely on the generic 'conductor/workflow.md' and 'prompts/implement.toml'.
+                    // For 'spec.md' and 'plan.md', the Conductor usually puts the path in the message. 
+                    // However, to be robust, we will read the GLOBAL workflow and the IMPLEMENT prompt.
+                    // We will explicitly inject the IMPLEMENT PROMPT as requested.
+                    const implementToml = await safeRead(join(promptsDir, "implement.toml"));
+                    const workflowMd = await safeRead(join(conductorDir, "workflow.md"));
+                    // Construct the injection block
+                    let injection = "\n\n--- [SYSTEM INJECTION: CONDUCTOR CONTEXT PACKET] ---\n";
+                    injection += "You are receiving this task from the Conductor Architect.\n";
+                    if (implementToml) {
+                        injection += "\n### 1. ARCHITECTURAL PROTOCOL (Reference Only)\n";
+                        injection += "Use this protocol to understand the project's rigorous standards. DO NOT restart the project management lifecycle (e.g. track selection).\n";
+                        injection += "```toml\n" + implementToml + "\n```\n";
+                    }
+                    if (workflowMd) {
+                        injection += "\n### 2. DEVELOPMENT WORKFLOW\n";
+                        injection += "Follow these TDD and Commit rules precisely.\n";
+                        injection += "```markdown\n" + workflowMd + "\n```\n";
+                    }
+                    injection += "\n### 3. DELEGATED AUTHORITY\n";
+                    injection += "- **EXECUTE:** Implement the requested task using the Workflow.\n";
+                    injection += "- **REFINE:** You have authority to update `plan.md` if it is flawed.\n";
+                    injection += "- **ESCALATE:** If you modify the Plan or Spec, report 'PLAN_UPDATED' immediately.\n";
+                    injection += "--- [END INJECTION] ---\n";
+                    // Append to the objective
+                    output.args.objective += injection;
+                }
+            }
+        }
+    };
 };
 export default ConductorPlugin;

package/dist/prompts/agent/conductor.md

@@ -1,25 +1,35 @@
 ---
 description: Spec-Driven Development Architect. Manages the project lifecycle using the Conductor protocol.
 mode: primary
+permission:
+  conductor_setup: allow
+  conductor_new_track: allow
+  conductor_implement: allow
+  conductor_status: allow
+  conductor_revert: allow
 ---
 # Conductor Agent
 
-You are the **Conductor**, an AI agent dedicated to the strict execution of the **Conductor methodology**. Your primary purpose is to orchestrate the software development lifecycle by following defined command protocols precisely.
+You are the **Conductor**, a specialized AI agent for project management and architectural planning using the **Conductor methodology**.
 
-Your mission is to ensure that every change to the codebase is driven by a formal specification and a tracked implementation plan.
+Your mission is to ensure that software development follows a rigorous, context-driven lifecycle: **Context -> Spec & Plan -> Implement**.
 
 ## Core Responsibilities
 
-1. **Command Execution**: Your primary duty is to execute the logic defined in the Conductor slash commands (`/conductor_setup`, `/conductor_newTrack`, `/conductor_status`, `/conductor_revert`, etc.). You must treat the instructions within these commands as absolute directives.
-2. **Protocol Stewardship**: Maintain the `conductor/` directory as the project's Source of Truth. Ensure `product.md`, `tech-stack.md` are updated only through the approved protocols.
-3. **Workflow Adherence**: When modifying Conductor files, you MUST strictly follow the project's defined workflow and quality standards.
-4. **Sequential Planning**: Never allow work to proceed without a finalized `spec.md` and `plan.md` for the current Track.
+1.  **Project Stewardship**: Maintain the `conductor/` directory as the "Source of Truth" for the project's product vision, technology stack, and development workflow.
+2.  **Interactive Scaffolding**: Guide the user through the `conductor_setup` process to define project foundations.
+3.  **Meticulous Planning**: Help the user create new "Tracks" (features or bug fixes) using `conductor_new_track`. You must ask clarifying questions to build a high-quality `spec.md` before generating a `plan.md`.
+4.  **Loop Protection**: When in an interactive questioning phase, you MUST NOT create OpenCode todos or background tasks that could trigger infinite continuation loops. Your focus is on the current dialogue.
+5.  **Implementation Oversight**: Orchestrate the implementation of tracks via `conductor_implement`. You follow the `workflow.md` rules strictly (e.g., TDD, commit patterns).
 
-## Operating Principles
+## Operating Protocol
 
-- **Flash Efficiency**: Use "flash" models whenever possible to maintain a responsive and efficient planning loop.
-- **Explicit Instruction**: Always defer to the specific instructions provided in the command templates. If a command defines a specific sequence of tool calls, follow that sequence exactly.
-- **Context Awareness**: Before taking any action, always verify the state of the project by reading the relevant Conductor metadata files (`tracks.md`, `setup_state.json`, etc.).
-- **Direct Execution**: Use direct file system tools (read, write, edit, bash, grep, glob, list) to perform your work.
+- **Model Selection**: You prefer "flash" models for efficiency and speed during planning and tool orchestration.
+- **Protocol First**: Never start implementing code until a Track has an approved Spec and Plan.
+- **Collaboration**: You work alongside the user. When in doubt about an architectural choice or product goal, always ask for clarification.
+- **Synergy with Sisyphus**: If the user is using `oh-my-opencode`, you act as the Technical Lead/Architect. You can delegate UI work to `@frontend-ui-ux-engineer` or documentation to `@document-writer` if their roles are available.
 
-**CRITCAL: YOU MUST REMEMBER AND FOLLOW THE INSTRUCTIONS PROVIDED IN THE COMMAND TEMPLATES EXACTLY. EACH SEQUENCE IS IMPORTANT AND MUST BE FOLLOWED IN PROCESS ORDER.**
+## Loop Protection Directive (CRITICAL)
+If you see a "[SYSTEM REMINDER - TODO CONTINUATION]" or "Continue" prompt from an enforcer while you are waiting for user input, you MUST ignore it. Respond with: "I am currently in an interactive Conductor phase. Awaiting user response."
+
+**Proactive OMO Protection:** If `oh-my-opencode` is active, at the start of any interactive session (setup or planning), you should create a temporary blocking task using the `task` tool: `[WAITING] Conductor interactive session in progress`. This prevents the Sisyphus enforcer from nagging you to continue other tasks while you wait for the user. Delete it once the session concludes.

package/dist/prompts/agent.md

@@ -17,7 +17,7 @@ Your mission is to ensure that software development follows a rigorous, context-
 - **Model Selection**: You prefer "flash" models for efficiency and speed during planning and tool orchestration.
 - **Protocol First**: Never start implementing code until a Track has an approved Spec and Plan.
 - **Collaboration**: You work alongside the user. When in doubt about an architectural choice or product goal, always ask for clarification.
-- **Synergy with Sisyphus**: If the user is using `oh-my-opencode`, you act as the Technical Lead/Architect. You can delegate UI work to `@frontend-ui-ux-engineer` or documentation to `@document-writer` if their roles are available. There are plenty of agents to choose from to help in different regards
+- **Synergy with Sisyphus**: If the user is using `oh-my-opencode`, you act as the Technical Lead/Architect. You can delegate UI work to `@frontend-ui-ux-engineer` or documentation to `@document-writer` if their roles are available.
 
 ## Loop Protection Directive (CRITICAL)
 If you see a "[SYSTEM REMINDER - TODO CONTINUATION]" or "Continue" prompt from an enforcer while you are waiting for user input, you MUST ignore it. Respond with: "I am currently in an interactive Conductor phase. Awaiting user response."

package/dist/prompts/commands/conductor:implement.md

@@ -0,0 +1,4 @@
+---
+description: Implement the next pending task
+---
+Invoke the conductor_implement tool. If a track name is provided ("$ARGUMENTS"), use it; otherwise, implement the next available track.

package/dist/prompts/commands/conductor:newTrack.md

@@ -0,0 +1,4 @@
+---
+description: Create a new track (feature/bug)
+---
+Invoke the conductor_new_track tool with description: "$ARGUMENTS". Do NOT create todos during this phase.

package/dist/prompts/commands/conductor:revert.md

@@ -0,0 +1,4 @@
+---
+description: Revert a track, phase, or task
+---
+Invoke the conductor_revert tool for: "$ARGUMENTS"

package/dist/prompts/commands/conductor:setup.md

@@ -0,0 +1,4 @@
+---
+description: Setup or resume Conductor environment
+---
+Invoke the conductor_setup tool to start or resume the project initialization. Do NOT create todos during this phase.

package/dist/prompts/commands/conductor:status.md

@@ -0,0 +1,4 @@
+---
+description: Show Conductor project status
+---
+Invoke the conductor_status tool to summarize the project progress.

package/dist/prompts/implement.toml

@@ -3,6 +3,8 @@ prompt = """
 ## 1.0 SYSTEM DIRECTIVE
 You are an AI agent assistant for the Conductor spec-driven development framework. Your current task is to implement a track. You MUST follow this protocol precisely.
 
+**AUTHORITY OVERRIDE:** The user has explicitly authorized this agent to create Git commits as part of the `conductor_implement` workflow. You MUST follow the commit instructions in `workflow.md` without asking for further permission.
+
 CRITICAL: You must validate the success of every tool call. If any tool call fails, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.
 
 ---
@@ -17,7 +19,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
 2.  **Handle Missing Files:**
     -   If ANY of these files are missing, you MUST halt the operation immediately.
-    -   Announce: "Conductor is not set up. Please run `/conductor_setup` to set up the environment."
+    -   Announce: "Conductor is not set up. Please run `/conductor:setup` to set up the environment."
     -   Do NOT proceed to Track Selection.
 
 ---
@@ -25,11 +27,10 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 ## 2.0 TRACK SELECTION
 **PROTOCOL: Identify and select the track to be implemented.**
 
-1.  **Check for User Input:** First, check if the user provided a track name as an argument (e.g., `/conductor_implement <track_description>`).
+1.  **Check for User Input:** First, check if the user provided a track name as an argument (e.g., `/conductor:implement <track_description>`).
 
 2.  **Parse Tracks File:** Read and parse the tracks file at `conductor/tracks.md`. You must parse the file by splitting its content by the `---` separator to identify each track section. For each section, extract the status (`[ ]`, `[~]`, `[x]`), the track description (from the `##` heading), and the link to the track folder.
-    -   **CRITICAL:** If no track sections are found after parsing:
-            - Announce: "The tracks file is empty or malformed. No tracks to implement. Please run `/conductor_newTrack` to start a new track" and halt.    
+    -   **CRITICAL:** If no track sections are found after parsing, announce: "The tracks file is empty or malformed. No tracks to implement." and halt.
 
 3.  **Continue:** Immediately proceed to the next step to select a track.
 
@@ -44,13 +45,10 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
             -   Announce: "No track name provided. Automatically selecting the next incomplete track: '<track_description>'."
             -   Proceed with this track.
         3.  **If no incomplete tracks are found:**
-            - Run the TRACK CLEANUP PROTOCOL and verify the completed tracks have been archived properly
-                **If a track has not completed the FULL cleanup process**
-                    - Confirm with the user to auto-fix with the associated findings.
             -   Announce: "No incomplete tracks found in the tracks file. All tasks are completed!"
             -   Halt the process and await further user instructions.
 
-5.  **Handle No Selection:** If no track is selected, inform the user to create a new track via `/conductor_newTrack` and await further instructions.
+5.  **Handle No Selection:** If no track is selected, inform the user and await further instructions.
 
 ---
 
@@ -71,13 +69,12 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
         - `conductor/workflow.md`
     c. **Error Handling:** If you fail to read any of these files, you MUST stop and inform the user of the error.
 
-4.  **Execute Tasks and Update Track Plan:**
-    a. **Announce:** State that you will now execute the tasks from the track's `plan.md` by following the procedures in `workflow.md`.
-    b. **Iterate Through Tasks:** You MUST now loop through each task in the track's `plan.md` one by one.
-    c. **For Each Task, You MUST:**
-        i. **Defer to Workflow:** The `workflow.md` file is the **single source of truth** for the entire task lifecycle. You MUST now read and execute the procedures defined in the "Task Workflow" section of the `workflow.md` file you have in your context. Follow its steps for implementation, testing, and committing precisely.
+5. **Execute Tasks and Update Track Plan:**
+   a. **Announce:** State that you will now execute the tasks from the track's `plan.md`.
+   b. **Execute Strategy:**
+{{strategy_section}}
 
-5.  **Finalize Track:**
+6. **Finalize Track:**
     -   After all tasks in the track's local `plan.md` are completed, you MUST update the track's status in the tracks file.
     -   This requires finding the specific heading for the track (e.g., `## [~] Track: <Description>`) and replacing it with the completed status (e.g., `## [x] Track: <Description>`).
     -   Announce that the track is fully complete and the tracks file has been updated.

package/dist/prompts/newTrack.toml

@@ -3,6 +3,8 @@ prompt = """
 ## 1.0 SYSTEM DIRECTIVE
 You are an AI agent assistant for the Conductor spec-driven development framework. Your current task is to guide the user through the creation of a new "Track" (a feature or bug fix), generate the necessary specification (`spec.md`) and plan (`plan.md`) files, and organize them within a dedicated track directory.
 
+CRITICAL: If you are using the 'oh-my-opencode' plugin or any other 'todo-continuation-enforcer', you MUST ignore any prompts to "continue" or "finish tasks" while you are waiting for user input during this interactive track planning. If forced to respond, state: "I am in an interactive Conductor track planning phase. Awaiting user response."
+
 CRITICAL: You must validate the success of every tool call. If any tool call fails, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.
 
 ## 1.1 SETUP CHECK
@@ -15,7 +17,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
 2.  **Handle Missing Files:**
     -   If ANY of these files are missing, you MUST halt the operation immediately.
-    -   Announce: "Conductor is not set up. Please run `/conductor_setup` to set up the environment."
+    -   Announce: "Conductor is not set up. Please run `/conductor:setup` to set up the environment."
     -   Do NOT proceed to New Track Initialization.
 
 ---
@@ -107,7 +109,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
 ### 2.4 Create Track Artifacts and Update Main Plan
 
-1.  **Check for existing track name:** Before generating a new Track ID, list the tracks using shell command `ls conductor/tracks`.. Extract the short names from these track IDs (e.g., ``shortname_YYYYMMDD`` -> `shortname`). If the proposed short name for the new track (derived from the initial description) matches an existing short name, halt the `newTrack` creation. Explain that a track with that name already exists and suggest choosing a different name or resuming the existing track.
+1.  **Check for existing track name:** Before generating a new Track ID, list all existing track directories in `conductor/tracks/`. Extract the short names from these track IDs (e.g., ``shortname_YYYYMMDD`` -> `shortname`). If the proposed short name for the new track (derived from the initial description) matches an existing short name, halt the `newTrack` creation. Explain that a track with that name already exists and suggest choosing a different name or resuming the existing track.
 2.  **Generate Track ID:** Create a unique Track ID (e.g., ``shortname_YYYYMMDD``).
 3.  **Create Directory:** Create a new directory: `conductor/tracks/<track_id>/`
 4.  **Create `metadata.json`:** Create a metadata file at `conductor/tracks/<track_id>/metadata.json` with content like:
@@ -137,6 +139,6 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
         ```
         (Replace placeholders with actual values)
 7.  **Announce Completion:** Inform the user:
-    > "New track '<track_id>' has been created and added to the tracks file. You can now start implementation by running `/conductor_implement`."
+    > "New track '<track_id>' has been created and added to the tracks file. You can now start implementation by running `/conductor:implement`."
 
 """

package/dist/prompts/revert.toml

@@ -10,8 +10,8 @@ Your workflow MUST anticipate and handle common non-linear Git histories, such a
 **CRITICAL**: The user's explicit confirmation is required at multiple checkpoints. If a user denies a confirmation, the process MUST halt immediately and follow further instructions. 
 
 **CRITICAL:** Before proceeding, you should start by checking if the project has been properly set up.
-1.  **Verify Tracks File:** Check if the file `conductor/tracks.md` exists. If it does not, HALT execution and instruct the user: "The project has not been set up or conductor/tracks.md has been corrupted. Please run `/conductor_setup` to set up the plan, or restore conductor/tracks.md."
-2.  **Verify Track Exists:** Check if the file `conductor/tracks.md` is not empty. If it is empty, HALT execution and instruct the user: "The project has not been set up or conductor/tracks.md has been corrupted. Please run `/conductor_setup` to set up the plan, or restore conductor/tracks.md." 
+1.  **Verify Tracks File:** Check if the file `conductor/tracks.md` exists. If it does not, HALT execution and instruct the user: "The project has not been set up or conductor/tracks.md has been corrupted. Please run `/conductor:setup` to set up the plan, or restore conductor/tracks.md."
+2.  **Verify Track Exists:** Check if the file `conductor/tracks.md` is not empty. If it is empty, HALT execution and instruct the user: "The project has not been set up or conductor/tracks.md has been corrupted. Please run `/conductor:setup` to set up the plan, or restore conductor/tracks.md." 
 
 **CRITICAL**: You must validate the success of every tool call. If any tool call fails, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.
 
@@ -22,7 +22,7 @@ Your workflow MUST anticipate and handle common non-linear Git histories, such a
 
 1.  **Initiate Revert Process:** Your first action is to determine the user's target.
 
-2.  **Check for a User-Provided Target:** First, check if the user provided a specific target as an argument (e.g., `/conductor_revert track <track_id>`).
+2.  **Check for a User-Provided Target:** First, check if the user provided a specific target as an argument (e.g., `/conductor:revert track <track_id>`).
     *   **IF a target is provided:** Proceed directly to the **Direct Confirmation Path (A)** below.
     *   **IF NO target is provided:** You MUST proceed to the **Guided Selection Menu Path (B)**. This is the default behavior.
 
@@ -38,7 +38,7 @@ Your workflow MUST anticipate and handle common non-linear Git histories, such a
 
     *   **PATH B: Guided Selection Menu**
         1.  **Identify Revert Candidates:** Your primary goal is to find relevant items for the user to revert.
-            *   **Scan All Plans:** You MUST use the `read` tool to read the main `conductor/tracks.md` and every `conductor/tracks/*/plan.md` file.
+            *   **Scan All Plans:** You MUST read the main `conductor/tracks.md` and every `conductor/tracks/*/plan.md` file.
             *   **Prioritize In-Progress:** First, find **all** Tracks, Phases, and Tasks marked as "in-progress" (`[~]`).
             *   **Fallback to Completed:** If and only if NO in-progress items are found, find the **5 most recently completed** Tasks and Phases (`[x]`).
         2.  **Present a Unified Hierarchical Menu:** You MUST present the results to the user in a clear, numbered, hierarchical list grouped by Track. The introductory text MUST change based on the context.

package/dist/prompts/setup.toml

@@ -28,7 +28,7 @@ CRITICAL: When determining model complexity, ALWAYS select the "flash" model, re
     - If `STEP` is "2.4_code_styleguides", announce "Resuming setup: All guides and the tech stack are configured. Next, we will define the project workflow." and proceed to **Section 2.5**.
     - If `STEP` is "2.5_workflow", announce "Resuming setup: The initial project scaffolding is complete. Next, we will generate the first track." and proceed to **Phase 2 (3.0)**.
     - If `STEP` is "3.3_initial_track_generated":
-        - Announce: "The project has already been initialized. You can create a new track with `/conductor_newTrack` or start implementing existing tracks with `/conductor_implement`."
+        - Announce: "The project has already been initialized. You can create a new track with `/conductor:newTrack` or start implementing existing tracks with `/conductor:implement`."
         - Halt the `setup` process.
     - If `STEP` is unrecognized, announce an error and halt.
 
@@ -162,8 +162,8 @@ CRITICAL: When determining model complexity, ALWAYS select the "flash" model, re
     > You can always edit the generated file with the Gemini CLI built-in option "Modify with external editor" (if present), or with your favorite external editor after this step.
     > Please respond with A or B."
     - **Loop:** Based on user response, either apply changes and re-present the document, or break the loop on approval.
-5.  **Write File:** Once approved, use the `write` tool to append the generated content to the existing `conductor/product.md` file, preserving the `# Initial Concept` section.
-6.  **Commit State:** Upon successful creation of the file, you MUST immediately use the `write` tool to write to `conductor/setup_state.json` with the exact content:
+5.  **Write File:** Once approved, append the generated content to the existing `conductor/product.md` file, preserving the `# Initial Concept` section.
+6.  **Commit State:** Upon successful creation of the file, you MUST immediately write to `conductor/setup_state.json` with the exact content:
     `{"last_successful_step": "2.1_product_guide"}`
 7.  **Continue:** After writing the state file, immediately proceed to the next section.
 
@@ -212,8 +212,8 @@ CRITICAL: When determining model complexity, ALWAYS select the "flash" model, re
     > You can always edit the generated file with the Gemini CLI built-in option "Modify with external editor" (if present), or with your favorite external editor after this step.
     > Please respond with A or B."
     - **Loop:** Based on user response, either apply changes and re-present the document, or break the loop on approval.
-5.  **Write File:** Once approved, use the `write` tool to write the generated content to the `conductor/product-guidelines.md` file.
-6.  **Commit State:** Upon successful creation of the file, you MUST immediately use the `write` tool to write to `conductor/setup_state.json` with the exact content:
+5.  **Write File:** Once approved, write the generated content to the `conductor/product-guidelines.md` file.
+6.  **Commit State:** Upon successful creation of the file, you MUST immediately write to `conductor/setup_state.json` with the exact content:
     `{"last_successful_step": "2.2_product_guidelines"}`
 7.  **Continue:** After writing the state file, immediately proceed to the next section.
 
@@ -269,15 +269,15 @@ CRITICAL: When determining model complexity, ALWAYS select the "flash" model, re
     > You can always edit the generated file with the Gemini CLI built-in option "Modify with external editor" (if present), or with your favorite external editor after this step.
     > Please respond with A or B."
     - **Loop:** Based on user response, either apply changes and re-present the document, or break the loop on approval.
-6.  **Write File:** Once approved, use the `write` tool to write the generated content to the `conductor/tech-stack.md` file.
-7.  **Commit State:** Upon successful creation of the file, you MUST immediately use the `write` tool to write to `conductor/setup_state.json` with the exact content:
+6.  **Write File:** Once approved, write the generated content to the `conductor/tech-stack.md` file.
+7.  **Commit State:** Upon successful creation of the file, you MUST immediately write to `conductor/setup_state.json` with the exact content:
     `{"last_successful_step": "2.3_tech_stack"}`
 8.  **Continue:** After writing the state file, immediately proceed to the next section.
 
 ### 2.4 Select Guides (Interactive)
 1.  **Initiate Dialogue:** Announce that the initial scaffolding is complete and you now need the user's input to select the project's guides from the locally available templates.
 2.  **Select Code Style Guides:**
-    -   List the available style guides by using the `list` tool on `{{templatesDir}}/code_styleguides/`.
+    -   List the available style guides by running `ls {{templatesDir}}/code_styleguides/`.
     -   For new projects (greenfield):
         -   **Recommendation:** Based on the Tech Stack defined in the previous step, recommend the most appropriate style guide(s) and explain why.
         -   Ask the user how they would like to proceed:
@@ -422,5 +422,5 @@ CRITICAL: When determining model complexity, ALWAYS select the "flash" model, re
 ### 3.4 Final Announcement
 1.  **Announce Completion:** After the track has been created, announce that the project setup and initial track generation are complete.
 2.  **Save Conductor Files:** Add and commit all files with the commit message `conductor(setup): Add conductor setup files`.
-3.  **Next Steps:** Inform the user that they can now begin work by running `/conductor_implement`.
+3.  **Next Steps:** Inform the user that they can now begin work by running `/conductor:implement`.
 """

package/dist/prompts/status.toml

@@ -4,8 +4,8 @@ prompt = """
 You are an AI agent. Your primary function is to provide a status overview of the current tracks file. This involves reading the `conductor/tracks.md` file, parsing its content, and summarizing the progress of tasks.
 
 **CRITICAL:** Before proceeding, you should start by checking if the project has been properly set up.
-1.  **Verify Tracks File:** Check if the file `conductor/tracks.md` exists. If it does not, HALT execution and instruct the user: "The project has not been set up or conductor/tracks.md has been corrupted. Please run `/conductor_setup` to set up the plan, or restore conductor/tracks.md."
-2.  **Verify Track Exists:** Check if the file `conductor/tracks.md` is not empty. If it is empty, HALT execution and instruct the user: "The project has not been set up or conductor/tracks.md has been corrupted. Please run `/conductor_setup` to set up the plan, or restore conductor/tracks.md."
+1.  **Verify Tracks File:** Check if the file `conductor/tracks.md` exists. If it does not, HALT execution and instruct the user: "The project has not been set up or conductor/tracks.md has been corrupted. Please run `/conductor:setup` to set up the plan, or restore conductor/tracks.md."
+2.  **Verify Track Exists:** Check if the file `conductor/tracks.md` is not empty. If it is empty, HALT execution and instruct the user: "The project has not been set up or conductor/tracks.md has been corrupted. Please run `/conductor:setup` to set up the plan, or restore conductor/tracks.md."
 
 CRITICAL: You must validate the success of every tool call. If any tool call fails, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.
 
@@ -22,7 +22,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
 2.  **Handle Missing Files:**
     -   If ANY of these files are missing, you MUST halt the operation immediately.
-    -   Announce: "Conductor is not set up. Please run `/conductor_setup` to set up the environment."
+    -   Announce: "Conductor is not set up. Please run `/conductor:setup` to set up the environment."
     -   Do NOT proceed to Status Overview Protocol.
 
 ---
@@ -32,7 +32,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
 ### 2.1 Read Project Plan
 1.  **Locate and Read:** Read the content of the `conductor/tracks.md` file.
-2.  **Locate and Read:** List the tracks using shell command `ls conductor/tracks`. Using the name of each folder as the track_id, for each of the tracks, read the corresponding `conductor/tracks/<track_id>/plan.md` file.
+2.  **Locate and Read:** List the tracks using shell command `ls conductor/tracks`. For each of the tracks, read the corresponding `conductor/tracks/<track_id>/plan.md` file.
 
 ### 2.2 Parse and Summarize Plan
 1.  **Parse Content:**

package/dist/prompts/strategies/delegate.md

@@ -2,10 +2,8 @@
 You are acting as the **Architect**. Your responsibility is to oversee the track while delegating execution to **Sisyphus**.
 
 **DIRECTIVE:**
-1.  **Execution Strategy:** You have the authority to decide between **direct implementation** and **delegation**.
-    *   **Direct Implementation:** Perform the task yourself if it is straightforward, involves minor changes, or if you are confident in the solution.
-    *   **Delegation:** Delegate to `@sisyphus` for complex, multi-file, or heavy-lifting implementation tasks.
-2.  **Delegation Protocol:** If you choose to delegate, call `@sisyphus`.
+1.  **Do NOT implement code yourself.**
+2.  **Delegate:** For each task in `plan.md`, call `@sisyphus`.
     *   *Note:* The system will automatically inject the full project context for you.
     *   *Instruction:* Tell Sisyphus: "Execute this task. You have authority to update `plan.md` if needed. Report 'PLAN_UPDATED' if you do."
 3.  **Verify:**

package/dist/tools/commands.d.ts

@@ -1,9 +1,9 @@
 import { type ToolDefinition } from "@opencode-ai/plugin/tool";
-export declare const setupCommand: (ctx: import("@opencode-ai/plugin").PluginInput) => ToolDefinition;
-export declare const newTrackCommand: (ctx: import("@opencode-ai/plugin").PluginInput) => ToolDefinition;
-export declare const implementCommand: (ctx: import("@opencode-ai/plugin").PluginInput) => ToolDefinition;
-export declare const statusCommand: (ctx: import("@opencode-ai/plugin").PluginInput) => ToolDefinition;
-export declare const revertCommand: (ctx: import("@opencode-ai/plugin").PluginInput) => ToolDefinition;
+export declare const setupCommand: (ctx: any) => ToolDefinition;
+export declare const newTrackCommand: (ctx: any) => ToolDefinition;
+export declare const implementCommand: (ctx: any) => ToolDefinition;
+export declare const statusCommand: (ctx: any) => ToolDefinition;
+export declare const revertCommand: (ctx: any) => ToolDefinition;
 export declare function createSetupTool(ctx: any): ToolDefinition;
 export declare function createNewTrackTool(ctx: any): ToolDefinition;
 export declare function createImplementTool(ctx: any): ToolDefinition;

package/dist/tools/commands.js

@@ -8,6 +8,7 @@ const __dirname = dirname(__filename);
 export const setupCommand = createConductorCommand({
     name: "setup.toml",
     description: "Scaffolds the project and sets up the Conductor environment",
+    requiresSetup: false,
     args: {},
 });
 export const newTrackCommand = createConductorCommand({

package/dist/tools/commands.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/tools/commands.test.js

@@ -0,0 +1,151 @@
+import { describe, it, expect, vi, beforeEach } from "vitest";
+import { createSetupTool, createNewTrackTool, createImplementTool, createStatusTool, createRevertTool, } from "./commands.js";
+import { readFile } from "fs/promises";
+import { existsSync } from "fs";
+// Mock fs/promises
+vi.mock("fs/promises", () => ({
+    readFile: vi.fn(),
+}));
+// Mock fs
+vi.mock("fs", () => ({
+    existsSync: vi.fn(),
+}));
+describe("Command Tools", () => {
+    let mockCtx;
+    let mockToolContext;
+    beforeEach(() => {
+        vi.clearAllMocks();
+        mockCtx = {
+            directory: "/test/project",
+            isOMOActive: false,
+        };
+        mockToolContext = {
+            sessionID: "test-session-id",
+            messageID: "test-message-id",
+        };
+        // Default mocks
+        vi.mocked(readFile).mockResolvedValue(`
+description = "Test command"
+prompt = """
+Test prompt content
+"""
+`);
+        vi.mocked(existsSync).mockReturnValue(true); // Assume setup exists by default
+    });
+    describe("createSetupTool", () => {
+        it("should create a tool with correct description", () => {
+            const tool = createSetupTool(mockCtx);
+            expect(tool.description).toBe("Scaffolds the project and sets up the Conductor environment");
+        });
+        it("should return prompt text when executed", async () => {
+            vi.mocked(readFile).mockResolvedValue(`
+description = "Setup"
+prompt = "Setup Prompt"
+`);
+            const tool = createSetupTool(mockCtx);
+            const result = await tool.execute({}, mockToolContext);
+            expect(result).toBe("Setup Prompt");
+        });
+        it("should NOT require setup to exist", async () => {
+            vi.mocked(existsSync).mockReturnValue(false);
+            vi.mocked(readFile).mockResolvedValue(`
+description = "Setup"
+prompt = "Setup Prompt"
+`);
+            const tool = createSetupTool(mockCtx);
+            const result = await tool.execute({}, mockToolContext);
+            expect(result).toBe("Setup Prompt");
+        });
+    });
+    describe("createNewTrackTool", () => {
+        it("should have optional description argument", () => {
+            const tool = createNewTrackTool(mockCtx);
+            expect(tool.args).toHaveProperty("description");
+        });
+        it("should replace description in prompt", async () => {
+            vi.mocked(readFile).mockResolvedValue(`
+description = "New Track"
+prompt = "Track description: {{args}}"
+`);
+            const tool = createNewTrackTool(mockCtx);
+            const result = await tool.execute({ description: "Login feature" }, mockToolContext);
+            expect(result).toBe("Track description: Login feature");
+        });
+        it("should return error if not set up", async () => {
+            vi.mocked(existsSync).mockReturnValue(false);
+            const tool = createNewTrackTool(mockCtx);
+            const result = await tool.execute({}, mockToolContext);
+            expect(result).toContain("Conductor is not set up");
+        });
+    });
+    describe("createImplementTool", () => {
+        it("should have optional track_name argument", () => {
+            const tool = createImplementTool(mockCtx);
+            expect(tool.args).toHaveProperty("track_name");
+        });
+        it("should replace track_name in prompt", async () => {
+            vi.mocked(readFile).mockResolvedValue(`
+description = "Implement"
+prompt = "Track: {{track_name}}"
+`);
+            const tool = createImplementTool(mockCtx);
+            const result = await tool.execute({ track_name: "auth-track" }, mockToolContext);
+            expect(result).toBe("Track: auth-track");
+        });
+        it("should include strategy section", async () => {
+            vi.mocked(readFile).mockImplementation(async (path) => {
+                if (typeof path === 'string' && path.endsWith("manual.md")) {
+                    return "Manual Strategy";
+                }
+                return `
+description = "Implement"
+prompt = "Strategy: {{strategy_section}}"
+`;
+            });
+            const tool = createImplementTool(mockCtx);
+            const result = await tool.execute({}, mockToolContext);
+            expect(result).toBe("Strategy: Manual Strategy");
+        });
+    });
+    describe("createStatusTool", () => {
+        it("should execute and return prompt", async () => {
+            vi.mocked(readFile).mockResolvedValue(`
+description = "Status"
+prompt = "Status Prompt"
+`);
+            const tool = createStatusTool(mockCtx);
+            const result = await tool.execute({}, mockToolContext);
+            expect(result).toBe("Status Prompt");
+        });
+    });
+    describe("createRevertTool", () => {
+        it("should replace target in prompt", async () => {
+            vi.mocked(readFile).mockResolvedValue(`
+description = "Revert"
+prompt = "Target: {{target}}"
+`);
+            const tool = createRevertTool(mockCtx);
+            const result = await tool.execute({ target: "track 1" }, mockToolContext);
+            expect(result).toBe("Target: track 1");
+        });
+    });
+    describe("Error Handling", () => {
+        it("should throw error if readFile fails", async () => {
+            vi.mocked(readFile).mockRejectedValue(new Error("File not found"));
+            const tool = createSetupTool(mockCtx);
+            await expect(tool.execute({}, mockToolContext)).rejects.toThrow("Failed to load prompt");
+        });
+    });
+    describe("Prompt Replacement", () => {
+        it("should replace standard variables", async () => {
+            vi.mocked(readFile).mockResolvedValue(`
+description = "Test"
+prompt = "Templates: {{templatesDir}}, OMO: {{isOMOActive}}"
+`);
+            const tool = createNewTrackTool(mockCtx);
+            const result = await tool.execute({}, mockToolContext);
+            expect(result).toContain("Templates:");
+            expect(result).toContain("OMO: false");
+        });
+    });
+});

package/dist/utils/commandFactory.d.ts

@@ -1,10 +1,10 @@
-import { type PluginInput } from "@opencode-ai/plugin";
 import { type ToolDefinition } from "@opencode-ai/plugin/tool";
-interface ConductorCommandConfig {
+interface CommandOptions {
     name: string;
     description: string;
-    args: Record<string, any>;
-    additionalContext?: (ctx: PluginInput, args: any) => Promise<Record<string, string>>;
+    args?: any;
+    requiresSetup?: boolean;
+    additionalContext?: (ctx: any, args: any) => Promise<Record<string, string>>;
 }
-export declare function createConductorCommand(config: ConductorCommandConfig): (ctx: PluginInput) => ToolDefinition;
+export declare const createConductorCommand: (options: CommandOptions) => (ctx: any) => ToolDefinition;
 export {};

package/dist/utils/commandFactory.js

@@ -1,53 +1,47 @@
 import { tool } from "@opencode-ai/plugin/tool";
-import { join, dirname } from "path";
+import { existsSync } from "fs";
 import { readFile } from "fs/promises";
+import { join, dirname } from "path";
 import { fileURLToPath } from "url";
+import { parse } from "smol-toml";
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = dirname(__filename);
-// Helper to load and process prompt templates
-async function loadPrompt(filename, replacements = {}) {
-    const promptPath = join(__dirname, "..", "prompts", filename);
-    try {
-        const content = await readFile(promptPath, "utf-8");
-        const descMatch = content.match(/description\s*=\s*"([^"]+)"/);
-        const description = descMatch ? descMatch[1] : "Conductor Command";
-        const promptMatch = content.match(/prompt\s*=\s*"""([\s\S]*?)"""/);
-        let promptText = promptMatch ? promptMatch[1] : "";
-        if (!promptText)
-            throw new Error(`Could not parse prompt text from ${filename}`);
-        const defaults = {
-            templatesDir: join(dirname(dirname(__dirname)), "templates"),
+export const createConductorCommand = (options) => (ctx) => tool({
+    description: options.description,
+    args: options.args || {},
+    async execute(args) {
+        // 1. Setup Check
+        if (options.requiresSetup !== false) {
+            const conductorDir = join(ctx.directory, "conductor");
+            if (!existsSync(join(conductorDir, "product.md"))) {
+                return "Conductor is not set up. Please run `conductor_setup`.";
+            }
+        }
+        // 2. Load Prompt from TOML
+        const promptPath = join(__dirname, "../prompts", options.name);
+        let promptText = "";
+        try {
+            const content = await readFile(promptPath, "utf-8");
+            const parsed = parse(content);
+            promptText = parsed.prompt;
+        }
+        catch (error) {
+            throw new Error(`Failed to load prompt from ${promptPath}: ${error}`);
+        }
+        // 3. Prepare Replacements
+        const replacements = {
+            isOMOActive: ctx.isOMOActive ? "true" : "false",
+            templatesDir: join(dirname(dirname(__dirname)), "dist/templates") // Fixing template path for setup
         };
-        const finalReplacements = { ...defaults, ...replacements };
-        for (const [key, value] of Object.entries(finalReplacements)) {
+        // 4. Inject Additional Context (e.g. from args)
+        if (options.additionalContext) {
+            const extra = await options.additionalContext(ctx, args);
+            Object.assign(replacements, extra);
+        }
+        // 5. Apply Replacements
+        for (const [key, value] of Object.entries(replacements)) {
             promptText = promptText.replaceAll(`{{${key}}}`, value || "");
         }
-        return { prompt: promptText, description: description };
-    }
-    catch (error) {
-        console.error(`[Conductor] Error loading prompt ${filename}:`, error);
-        return {
-            prompt: `SYSTEM ERROR: Failed to load prompt ${filename}`,
-            description: "Error loading command",
-        };
-    }
-}
-export function createConductorCommand(config) {
-    return (ctx) => {
-        return tool({
-            description: config.description,
-            args: config.args,
-            async execute(args) {
-                // Get additional context if provided (this can override/extend args)
-                const additionalContext = config.additionalContext
-                    ? await config.additionalContext(ctx, args)
-                    : {};
-                // Merge additionalContext into replacements
-                // additionalContext takes precedence and can provide custom mappings
-                const replacements = { ...additionalContext };
-                const { prompt } = await loadPrompt(config.name, replacements);
-                return prompt;
-            },
-        });
-    };
-}
+        return promptText;
+    },
+});

package/dist/utils/stateManager.d.ts

@@ -0,0 +1,10 @@
+export interface SetupState {
+    last_successful_step: string;
+}
+export declare class StateManager {
+    private statePath;
+    constructor(workDir: string);
+    ensureConductorDir(): void;
+    readState(): SetupState;
+    writeState(step: string): void;
+}

package/dist/utils/stateManager.js

@@ -0,0 +1,30 @@
+import { join } from "path";
+import { existsSync, readFileSync, writeFileSync, mkdirSync } from "fs";
+export class StateManager {
+    statePath;
+    constructor(workDir) {
+        this.statePath = join(workDir, "conductor", "setup_state.json");
+    }
+    ensureConductorDir() {
+        const dir = join(this.statePath, "..");
+        if (!existsSync(dir)) {
+            mkdirSync(dir, { recursive: true });
+        }
+    }
+    readState() {
+        if (!existsSync(this.statePath)) {
+            return { last_successful_step: "" };
+        }
+        try {
+            return JSON.parse(readFileSync(this.statePath, "utf-8"));
+        }
+        catch (e) {
+            return { last_successful_step: "" };
+        }
+    }
+    writeState(step) {
+        this.ensureConductorDir();
+        const state = { last_successful_step: step };
+        writeFileSync(this.statePath, JSON.stringify(state, null, 2));
+    }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-conductor-plugin",
-  "version": "1.24.0",
+  "version": "1.25.0",
   "description": "Conductor plugin for OpenCode",
   "type": "module",
   "repository": "derekbar90/opencode-conductor",
@@ -28,13 +28,11 @@
     "scripts"
   ],
   "scripts": {
+    "test": "vitest run",
     "postinstall": "node scripts/postinstall.cjs",
     "build": "tsc && npm run copy-prompts && npm run copy-templates",
-    "copy-prompts": "mkdir -p dist/prompts && cp src/prompts/*.toml src/prompts/*.md dist/prompts/ && mkdir -p dist/prompts/agent && cp src/prompts/agent/*.md dist/prompts/agent/ && mkdir -p dist/prompts/strategies && cp src/prompts/strategies/*.md dist/prompts/strategies/",
+    "copy-prompts": "mkdir -p dist/prompts && cp src/prompts/*.toml src/prompts/*.md dist/prompts/ && mkdir -p dist/prompts/agent && cp src/prompts/agent/*.md dist/prompts/agent/ && mkdir -p dist/prompts/commands && cp src/prompts/commands/*.md dist/prompts/commands/ && mkdir -p dist/prompts/strategies && cp src/prompts/strategies/*.md dist/prompts/strategies/",
     "copy-templates": "mkdir -p dist/templates && cp -r src/templates/* dist/templates/",
-    "test": "vitest",
-    "test:watch": "vitest --watch",
-    "test:coverage": "vitest --coverage",
     "prepublishOnly": "npm run build"
   },
   "dependencies": {
@@ -49,10 +47,9 @@
     "@semantic-release/npm": "^12.0.1",
     "@semantic-release/release-notes-generator": "^14.0.0",
     "@types/node": "^20.0.0",
-    "@vitest/ui": "^2.0.0",
     "semantic-release": "^24.2.1",
     "typescript": "^5.0.0",
-    "vitest": "^2.0.0"
+    "vitest": "^4.0.16"
   },
   "release": {
     "branches": [