opencode-conductor-plugin 1.26.0 → 1.27.0

package/dist/commands/implement.js

@@ -6,8 +6,8 @@ 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.",
+    name: "legacy/conductor/commands/conductor/implement.toml",
+    description: "Implements a feature or fixes a bug following a strict Plan and Spec.",
     args: {
         track_name: tool.schema.string().optional().describe("Specific track to implement. If omitted, selects the next incomplete track."),
     },

package/dist/commands/newTrack.js

@@ -1,8 +1,8 @@
 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.",
+    name: "legacy/conductor/commands/conductor/newTrack.toml",
+    description: "Creates a new Development Track (feature/bug/chore) with proper scaffolding.",
     args: {
         description: tool.schema.string().optional().describe("Brief description of the track."),
     },

package/dist/commands/revert.js

@@ -1,9 +1,14 @@
 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.",
+    name: "legacy/conductor/commands/conductor/revert.toml",
+    description: "Reverts the last commit in the current track and updates the plan.",
     args: {
         target: tool.schema.string().optional().describe("ID or description of what to revert."),
-    }
+    },
+    additionalContext: async (ctx, args) => {
+        return {
+            target: args.target || "",
+        };
+    },
 });

package/dist/commands/setup.js

@@ -1,8 +1,8 @@
 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.",
+    name: "legacy/conductor/commands/conductor/setup.toml",
+    description: "Initializes the Conductor in the current project, creating necessary directories and the workflow file.",
     args: {
         user_input: tool.schema.string().optional().describe("The user's response to a previous question, if applicable."),
     },

package/dist/commands/status.js

@@ -1,6 +1,6 @@
 import { createConductorCommand } from "../utils/commandFactory.js";
 export const statusCommand = createConductorCommand({
-    name: "status.toml",
-    description: "Shows the status of Conductor tracks.",
+    name: "legacy/conductor/commands/conductor/status.toml",
+    description: "Displays the current Conductor status, active tracks, and project health.",
     args: {}
 });

package/dist/index.js

@@ -28,12 +28,12 @@ const ConductorPlugin = async (ctx) => {
     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),
+        commands: {
+            setup: setupCommand(extendedCtx),
+            newTrack: newTrackCommand(extendedCtx),
+            implement: implementCommand(extendedCtx),
+            status: statusCommand(extendedCtx),
+            revert: revertCommand(extendedCtx),
         },
         "tool.execute.before": async (input, output) => {
             // INTERCEPT: Sisyphus Delegation Hook
@@ -64,7 +64,7 @@ const ConductorPlugin = async (ctx) => {
                     // 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 implementToml = await safeRead(join(promptsDir, "definitions", "implement.toml"));
                     const workflowMd = await safeRead(join(conductorDir, "workflow.md"));
                     // Construct the injection block
                     let injection = "\n\n--- [SYSTEM INJECTION: CONDUCTOR CONTEXT PACKET] ---\n";

package/dist/prompts/agent.md

@@ -19,5 +19,5 @@ Your mission is to ensure that software development follows a rigorous, context-
 - **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.
 
-## Loop Protection Directive (CRITICAL)
+## 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/{implement.toml → legacy/conductor/commands/conductor/implement.toml}

@@ -3,8 +3,6 @@ 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.
 
 ---
@@ -69,19 +67,21 @@ 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.
 
-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}}
+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.
 
-6. **Finalize Track:**
+5.  **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>`).
+    -   **Commit Changes:** Stage `conductor/tracks.md` and commit with the message `chore(conductor): Mark track '<track_description>' as complete`.
     -   Announce that the track is fully complete and the tracks file has been updated.
 
 ---
 
-## 6.0 SYNCHRONIZE PROJECT DOCUMENTATION
+## 4.0 SYNCHRONIZE PROJECT DOCUMENTATION
 **PROTOCOL: Update project-level documentation based on the completed track.**
 
 1.  **Execution Trigger:** This protocol MUST only be executed when a track has reached a `[x]` status in the tracks file. DO NOT execute this protocol for any other track status changes.
@@ -128,6 +128,9 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
 6.  **Final Report:** Announce the completion of the synchronization process and provide a summary of the actions taken.
     - **Construct the Message:** Based on the records of which files were changed, construct a summary message.
+    - **Commit Changes:**
+        - If any files were changed (`product.md`, `tech-stack.md`, or `product-guidelines.md`), you MUST stage them and commit them.
+        - **Commit Message:** `docs(conductor): Synchronize docs for track '<track_description>'`
     - **Example (if product.md was changed, but others were not):**
         > "Documentation synchronization is complete.
         > - **Changes made to `product.md`:** The user-facing description of the product was updated to include the new feature.
@@ -138,7 +141,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
 ---
 
-## 7.0 TRACK CLEANUP
+## 5.0 TRACK CLEANUP
 **PROTOCOL: Offer to archive or delete the completed track.**
 
 1.  **Execution Trigger:** This protocol MUST only be executed after the current track has been successfully implemented and the `SYNCHRONIZE PROJECT DOCUMENTATION` step is complete.
@@ -155,7 +158,8 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
         i.   **Create Archive Directory:** Check for the existence of `conductor/archive/`. If it does not exist, create it.
         ii.  **Archive Track Folder:** Move the track's folder from `conductor/tracks/<track_id>` to `conductor/archive/<track_id>`.
         iii. **Remove from Tracks File:** Read the content of `conductor/tracks.md`, remove the entire section for the completed track (the part that starts with `---` and contains the track description), and write the modified content back to the file.
-        iv.  **Announce Success:** Announce: "Track '<track_description>' has been successfully archived."
+        iv.  **Commit Changes:** Stage `conductor/tracks.md` and `conductor/archive/`. Commit with the message `chore(conductor): Archive track '<track_description>'`.
+        v.   **Announce Success:** Announce: "Track '<track_description>' has been successfully archived."
     *   **If user chooses "B" (Delete):**
         i. **CRITICAL WARNING:** Before proceeding, you MUST ask for a final confirmation due to the irreversible nature of the action.
             > "WARNING: This will permanently delete the track folder and all its contents. This action cannot be undone. Are you sure you want to proceed? (yes/no)"
@@ -163,7 +167,8 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
             - **If 'yes'**:
                 a. **Delete Track Folder:** Permanently delete the track's folder from `conductor/tracks/<track_id>`.
                 b. **Remove from Tracks File:** Read the content of `conductor/tracks.md`, remove the entire section for the completed track, and write the modified content back to the file.
-                c. **Announce Success:** Announce: "Track '<track_description>' has been permanently deleted."
+                c. **Commit Changes:** Stage `conductor/tracks.md` and the deletion of `conductor/tracks/<track_id>`. Commit with the message `chore(conductor): Delete track '<track_description>'`.
+                d. **Announce Success:** Announce: "Track '<track_description>' has been permanently deleted."
             - **If 'no' (or anything else)**:
                 a. **Announce Cancellation:** Announce: "Deletion cancelled. The track has not been changed."
     *   **If user chooses "C" (Skip) or provides any other input:**

package/dist/prompts/{newTrack.toml → legacy/conductor/commands/conductor/newTrack.toml}

@@ -3,8 +3,6 @@ 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
@@ -94,7 +92,9 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
     *   Read the selected workflow file from `conductor/workflow.md`.
     *   Generate a `plan.md` with a hierarchical list of Phases, Tasks, and Sub-tasks.
     *   **CRITICAL:** The plan structure MUST adhere to the methodology in the workflow file (e.g., TDD tasks for "Write Tests" and "Implement").
-    *   Include status markers `[ ]` for each task/sub-task.
+    *   Include status markers `[ ]` for **EVERY** task and sub-task. The format must be:
+        - Parent Task: `- [ ] Task: ...`
+        - Sub-task: `    - [ ] ...`
     *   **CRITICAL: Inject Phase Completion Tasks.** Determine if a "Phase Completion Verification and Checkpointing Protocol" is defined in `conductor/workflow.md`. If this protocol exists, then for each **Phase** that you generate in `plan.md`, you MUST append a final meta-task to that phase. The format for this meta-task is: `- [ ] Task: Conductor - User Manual Verification '<Phase Name>' (Protocol in workflow.md)`.
 
 3.  **User Confirmation:** Present the drafted `plan.md` to the user for review and approval.
@@ -129,13 +129,10 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
     *   Write the confirmed plan content to `conductor/tracks/<track_id>/plan.md`.
 6.  **Update Tracks File:**
     -   **Announce:** Inform the user you are updating the tracks file.
-    -   **Append Section:** Append a new section for the track to the end of `conductor/tracks.md`. The format MUST be:
+    -   **Append Section:** Append a new item to the track list in `conductor/tracks.md`. The format MUST be:
         ```markdown
-
-        ---
-
-        ## [ ] Track: <Track Description>
-        *Link: [./conductor/tracks/<track_id>/](./conductor/tracks/<track_id>/)*
+        - [ ] **Track: <Track Description>**
+          *Link: [./conductor/tracks/<track_id>/](./conductor/tracks/<track_id>/)*
         ```
         (Replace placeholders with actual values)
 7.  **Announce Completion:** Inform the user:

package/dist/prompts/{revert.toml → legacy/conductor/commands/conductor/revert.toml}

@@ -84,7 +84,8 @@ Your workflow MUST anticipate and handle common non-linear Git histories, such a
 
 3.  **Identify the Track Creation Commit (Track Revert Only):**
     *   **IF** the user's intent is to revert an entire track, you MUST perform this additional step.
-    *   **Method:** Use `git log -- conductor/tracks.md` and search for the commit that first introduced the `## [ ] Track: <Track Description>` line for the target track into the tracks file.
+    *   **Method:** Use `git log -- conductor/tracks.md` and search for the commit that first introduced the track entry.
+        *   Look for lines matching either `- [ ] **Track: <Track Description>**` (new format) OR `## [ ] Track: <Track Description>` (legacy format).
     *   Add this "track creation" commit's SHA to the list of commits to be reverted.
 
 4.  **Compile and Analyze Final List:**

package/dist/prompts/{setup.toml → legacy/conductor/commands/conductor/setup.toml}

@@ -3,8 +3,6 @@ prompt = """
 ## 1.0 SYSTEM DIRECTIVE
 You are an AI agent. Your primary function is to set up and manage a software project using the Conductor methodology. This document is your operational protocol. Adhere to these instructions precisely and sequentially. Do not make assumptions.
 
-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 setup. If forced to respond, state: "I am in an interactive Conductor setup 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.
 
 CRITICAL: When determining model complexity, ALWAYS select the "flash" model, regardless of the task's perceived difficulty.
@@ -277,7 +275,7 @@ CRITICAL: When determining model complexity, ALWAYS select the "flash" model, re
 ### 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 running `ls {{templatesDir}}/code_styleguides/`.
+    -   List the available style guides by running `ls ~/.gemini/extensions/conductor/templates/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:
@@ -292,13 +290,13 @@ CRITICAL: When determining model complexity, ALWAYS select the "flash" model, re
             - Ask the user for a simple confirmation to proceed with options like:
                     A) Yes, I want to proceed with the suggested code style guides.
                     B) No, I want to add more code style guides.
-    -   **Action:** Construct and execute a command to create the directory and copy all selected files. For example: `mkdir -p conductor/code_styleguides && cp {{templatesDir}}/code_styleguides/python.md {{templatesDir}}/code_styleguides/javascript.md conductor/code_styleguides/`
+    -   **Action:** Construct and execute a command to create the directory and copy all selected files. For example: `mkdir -p conductor/code_styleguides && cp ~/.gemini/extensions/conductor/templates/code_styleguides/python.md ~/.gemini/extensions/conductor/templates/code_styleguides/javascript.md conductor/code_styleguides/`
     -   **Commit State:** Upon successful completion of the copy command, you MUST immediately write to `conductor/setup_state.json` with the exact content:
         `{"last_successful_step": "2.4_code_styleguides"}`
 
 ### 2.5 Select Workflow (Interactive)
 1.  **Copy Initial Workflow:**
-    -   Copy `{{templatesDir}}/workflow.md` to `conductor/workflow.md`.
+    -   Copy `~/.gemini/extensions/conductor/templates/workflow.md` to `conductor/workflow.md`.
 2.  **Customize Workflow:**
     -   Ask the user: "Do you want to use the default workflow or customize it?"
         The default workflow includes:
@@ -387,8 +385,8 @@ CRITICAL: When determining model complexity, ALWAYS select the "flash" model, re
 
     ---
 
-    ## [ ] Track: <Track Description>
-    *Link: [./conductor/tracks/<track_id>/](./conductor/tracks/<track_id>/)*
+    - [ ] **Track: <Track Description>**
+      *Link: [./conductor/tracks/<track_id>/](./conductor/tracks/<track_id>/)*
     ```
 3.  **Generate Track Artifacts:**
     a. **Define Track:** The approved title is the track description.
@@ -396,6 +394,9 @@ CRITICAL: When determining model complexity, ALWAYS select the "flash" model, re
         i. Automatically generate a detailed `spec.md` for this track.
         ii. Automatically generate a `plan.md` for this track.
             - **CRITICAL:** The structure of the tasks must adhere to the principles outlined in the workflow file at `conductor/workflow.md`. For example, if the workflow specificies Test-Driven Development, each feature task must be broken down into a "Write Tests" sub-task followed by an "Implement Feature" sub-task.
+            - **CRITICAL:** Include status markers `[ ]` for **EVERY** task and sub-task. The format must be:
+                - Parent Task: `- [ ] Task: ...`
+                - Sub-task: `    - [ ] ...`
             - **CRITICAL: Inject Phase Completion Tasks.** You MUST read the `conductor/workflow.md` file to determine if a "Phase Completion Verification and Checkpointing Protocol" is defined. If this protocol exists, then for each **Phase** that you generate in `plan.md`, you MUST append a final meta-task to that phase. The format for this meta-task is: `- [ ] Task: Conductor - User Manual Verification '<Phase Name>' (Protocol in workflow.md)`. You MUST replace `<Phase Name>` with the actual name of the phase.
     c. **Create Track Artifacts:**
         i. **Generate and Store Track ID:** Create a unique Track ID from the track description using format `shortname_YYYYMMDD` and store it. You MUST use this exact same ID for all subsequent steps for this track.

package/dist/prompts/{status.toml → legacy/conductor/commands/conductor/status.toml}

@@ -33,6 +33,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`. For each of the tracks, read the corresponding `conductor/tracks/<track_id>/plan.md` file.
+    *   **Parsing Logic:** When reading `conductor/tracks.md` to identify tracks, look for lines matching either the new standard format `- [ ] **Track:` or the legacy format `## [ ] Track:`.
 
 ### 2.2 Parse and Summarize Plan
 1.  **Parse Content:**

package/dist/tools/commands.js

@@ -6,12 +6,12 @@ import { readFile } from "fs/promises";
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = dirname(__filename);
 export const setupCommand = createConductorCommand({
-    name: "setup.toml",
+    name: "legacy/conductor/commands/conductor/setup.toml",
     description: "Directives lookup tool for scaffolding the project and setting up the Conductor environment",
     args: {},
 });
 export const newTrackCommand = createConductorCommand({
-    name: "newTrack.toml",
+    name: "legacy/conductor/commands/conductor/newTrack.toml",
     description: "Directives lookup tool for planning a track, generating track-specific spec documents and updating the tracks file",
     args: {
         description: tool.schema.string().optional().describe("Brief description of the track (feature, bug fix, chore, etc.)"),
@@ -23,7 +23,7 @@ export const newTrackCommand = createConductorCommand({
     },
 });
 export const implementCommand = createConductorCommand({
-    name: "implement.toml",
+    name: "legacy/conductor/commands/conductor/implement.toml",
     description: "Directives lookup tool for executing the tasks defined in the specified track's plan",
     args: {
         track_name: tool.schema.string().optional().describe("Name or description of the track to implement"),
@@ -47,12 +47,12 @@ export const implementCommand = createConductorCommand({
     },
 });
 export const statusCommand = createConductorCommand({
-    name: "status.toml",
+    name: "legacy/conductor/commands/conductor/status.toml",
     description: "Directives lookup tool for displaying the current progress of the project",
     args: {},
 });
 export const revertCommand = createConductorCommand({
-    name: "revert.toml",
+    name: "legacy/conductor/commands/conductor/revert.toml",
     description: "Directives lookup tool for reverting previous work",
     args: {
         target: tool.schema.string().optional().describe("Target to revert (e.g., 'track <track_id>', 'phase <phase_name>', 'task <task_name>')"),

package/dist/utils/commandFactory.js

@@ -6,9 +6,31 @@ 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 src/prompts first, then relative to project root
+    const pathsToTry = [
+        join(__dirname, "..", "prompts", filename),
+        join(__dirname, "..", "..", filename)
+    ];
+    let content = "";
+    let successPath = "";
+    for (const p of pathsToTry) {
+        try {
+            content = await readFile(p, "utf-8");
+            successPath = p;
+            break;
+        }
+        catch (e) {
+            continue;
+        }
+    }
+    if (!content) {
+        console.error(`[Conductor] Error loading prompt ${filename}: Not found in any tried paths`);
+        return {
+            prompt: `SYSTEM ERROR: Failed to load prompt ${filename}`,
+            description: "Error loading command",
+        };
+    }
     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]*?)"""/);
@@ -25,10 +47,10 @@ async function loadPrompt(filename, replacements = {}) {
         return { prompt: promptText, description: description };
     }
     catch (error) {
-        console.error(`[Conductor] Error loading prompt ${filename}:`, error);
+        console.error(`[Conductor] Error parsing prompt ${filename}:`, error);
         return {
-            prompt: `SYSTEM ERROR: Failed to load prompt ${filename}`,
-            description: "Error loading command",
+            prompt: `SYSTEM ERROR: Failed to parse prompt ${filename}`,
+            description: "Error parsing command",
         };
     }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-conductor-plugin",
-  "version": "1.26.0",
+  "version": "1.27.0",
   "description": "Conductor plugin for OpenCode",
   "type": "module",
   "repository": "derekbar90/opencode-conductor",
@@ -31,7 +31,7 @@
     "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/commands && cp src/prompts/commands/*.md dist/prompts/commands/ && mkdir -p dist/prompts/strategies && cp src/prompts/strategies/*.md dist/prompts/strategies/",
+    "copy-prompts": "mkdir -p dist/prompts && cp 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/ && mkdir -p dist/prompts/legacy/conductor/commands/conductor && cp legacy/conductor/commands/conductor/*.toml dist/prompts/legacy/conductor/commands/conductor/",
     "copy-templates": "mkdir -p dist/templates && cp -r src/templates/* dist/templates/",
     "prepublishOnly": "npm run build"
   },

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

@@ -1,4 +0,0 @@
----
-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

@@ -1,4 +0,0 @@
----
-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

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

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

@@ -1,4 +0,0 @@
----
-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

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