opencode-conductor-plugin 1.17.0 → 1.17.1

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/index.js

@@ -78,10 +78,10 @@ const ConductorPlugin = async (ctx) => {
         console.log("[Conductor] All components ready. Injecting config...");
         return {
             tool: {
-                "conductor:delegate": createDelegationTool(ctx),
-                "conductor:background_task": createBackgroundTask(backgroundManager),
-                "conductor:background_output": createBackgroundOutput(backgroundManager),
-                "conductor:background_cancel": createBackgroundCancel(backgroundManager),
+                "conductor_delegate": createDelegationTool(ctx),
+                "conductor_background_task": createBackgroundTask(backgroundManager),
+                "conductor_background_output": createBackgroundOutput(backgroundManager),
+                "conductor_background_cancel": createBackgroundCancel(backgroundManager),
             },
             config: async (config) => {
                 if (!config)
@@ -89,27 +89,27 @@ const ConductorPlugin = async (ctx) => {
                 console.log("[Conductor] config handler: Merging commands and agents...");
                 config.command = {
                     ...(config.command || {}),
-                    "conductor:setup": {
+                    "conductor_setup": {
                         template: setup.prompt,
                         description: setup.description,
                         agent: "conductor",
                     },
-                    "conductor:newTrack": {
+                    "conductor_newTrack": {
                         template: newTrack.prompt,
                         description: newTrack.description,
                         agent: "conductor",
                     },
-                    "conductor:implement": {
+                    "conductor_implement": {
                         template: implement.prompt,
                         description: implement.description,
                         agent: "conductor_implementer",
                     },
-                    "conductor:status": {
+                    "conductor_status": {
                         template: status.prompt,
                         description: status.description,
                         agent: "conductor",
                     },
-                    "conductor:revert": {
+                    "conductor_revert": {
                         template: revert.prompt,
                         description: revert.description,
                         agent: "conductor",
@@ -169,10 +169,10 @@ const ConductorPlugin = async (ctx) => {
                             todowrite: true,
                             todoread: true,
                             webfetch: true,
-                            "conductor:delegate": true,
-                            "conductor:background_task": true,
-                            "conductor:background_output": true,
-                            "conductor:background_cancel": true,
+                            "conductor_delegate": true,
+                            "conductor_background_task": true,
+                            "conductor_background_output": true,
+                            "conductor_background_cancel": true,
                         },
                     },
                 };
@@ -182,8 +182,8 @@ const ConductorPlugin = async (ctx) => {
                     "delegate_to_agent",
                     "task",
                     "background_task",
-                    "conductor:delegate",
-                    "conductor:background_task",
+                    "conductor_delegate",
+                    "conductor_background_task",
                 ];
                 if (delegationTools.includes(input.tool)) {
                     const conductorDir = join(ctx.directory, "conductor");

package/dist/prompts/agent/conductor.md

@@ -24,7 +24,7 @@ Your mission is to ensure that every change to the codebase is driven by a forma
 
 ## 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.
+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`, and `workflow.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.

package/dist/prompts/agent/implementer.md

@@ -15,10 +15,10 @@ permission:
   todowrite: allow
   todoread: allow
   webfetch: allow
-  "conductor:delegate": allow
-  "conductor:background_task": allow
-  "conductor:background_output": allow
-  "conductor:background_cancel": allow
+  "conductor_delegate": allow
+  "conductor_background_task": allow
+  "conductor_background_output": allow
+  "conductor_background_cancel": allow
 ---
 # Conductor Implementer Agent
 
@@ -36,5 +36,5 @@ Your mission is to take an approved Specification and Plan and turn them into hi
 ## Operating Principles
 
 - **Spec Adherence**: Always implement exactly what is defined in the `spec.md`. If you find a technical contradiction, stop and ask the user.
-- **Direct Action & Delegation**: Use direct file system tools for core coding. Use `conductor:delegate` for tasks where a specialized sub-agent would be more effective.
+- **Direct Action & Delegation**: Use direct file system tools for core coding. Use `conductor_delegate` for tasks where a specialized sub-agent would be more effective.
 - **Transparency**: Every commit you make MUST include a detailed summary in Git Notes as per the workflow rules.

package/dist/prompts/implement.toml

@@ -19,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.
 
 ---
@@ -27,7 +27,7 @@ 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:** Use the `read` tool to 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." and halt.

package/dist/prompts/newTrack.toml

@@ -17,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.
 
 ---
@@ -139,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.
 

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.
 
@@ -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.
 
 ---

package/dist/tools/background.js

@@ -45,8 +45,8 @@ export class BackgroundManager {
             body: {
                 agent: input.agent,
                 tools: {
-                    "conductor:background_task": false,
-                    "conductor:delegate": false,
+                    "conductor_background_task": false,
+                    "conductor_delegate": false,
                 },
                 parts: [{ type: "text", text: input.prompt }],
             },
@@ -100,7 +100,7 @@ export class BackgroundManager {
         this.notifyParentSession(task);
     }
     async notifyParentSession(task) {
-        const message = `[BACKGROUND TASK COMPLETED] Task "${task.description}" finished. Use conductor:background_output with task_id="${task.id}" to get results.`;
+        const message = `[BACKGROUND TASK COMPLETED] Task "${task.description}" finished. Use conductor_background_output with task_id="${task.id}" to get results.`;
         await this.client.session.prompt({
             path: { id: task.parentSessionID },
             body: {

package/dist/tools/delegate.js

@@ -25,7 +25,7 @@ export function createDelegationTool(ctx) {
                 body: {
                     agent: args.subagent_type,
                     tools: {
-                        "conductor:delegate": false, // Disable this tool for the child session
+                        "conductor_delegate": false, // Disable this tool for the child session
                     },
                     parts: [{ type: "text", text: args.prompt }],
                 },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-conductor-plugin",
-  "version": "1.17.0",
+  "version": "1.17.1",
   "description": "Conductor plugin for OpenCode",
   "type": "module",
   "repository": "derekbar90/opencode-conductor",