opencode-conductor-plugin 1.18.0 → 1.19.1

package/dist/index.js

@@ -46,23 +46,12 @@ const ConductorPlugin = async (ctx) => {
                 };
             }
         };
-        // 2. Load Strategies
-        let strategySection = "";
-        try {
-            const strategyFile = "manual.md"; // Force manual strategy for now
-            const strategyPath = join(__dirname, "prompts", "strategies", strategyFile);
-            strategySection = await readFile(strategyPath, "utf-8");
-        }
-        catch (e) {
-            strategySection = "SYSTEM ERROR: Could not load execution strategy.";
-        }
         // 3. Load all Command Prompts (Parallel)
-        const [setup, newTrack, implement, status, revert, workflowMd] = await Promise.all([
+        const [setup, newTrack, implement, status, revert] = await Promise.all([
             loadPrompt("setup.toml"),
             loadPrompt("newTrack.toml", { args: "$ARGUMENTS" }),
             loadPrompt("implement.toml", {
                 track_name: "$ARGUMENTS",
-                strategy_section: strategySection,
             }),
             loadPrompt("status.toml"),
             loadPrompt("revert.toml", { target: "$ARGUMENTS" }),
@@ -78,6 +67,7 @@ const ConductorPlugin = async (ctx) => {
         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),
@@ -122,10 +112,17 @@ const ConductorPlugin = async (ctx) => {
                         mode: "primary",
                         prompt: conductorPrompt,
                         permission: {
+                            "read": {
+                                "*": "allow",
+                                "*.env": "deny",
+                                "*.env.*": "deny",
+                                "*.env.example": "allow"
+                            },
                             bash: "allow",
                             edit: "allow",
                             webfetch: "allow",
                             external_directory: "deny",
+                            list: "allow",
                         },
                         tools: {
                             bash: true,
@@ -145,10 +142,25 @@ const ConductorPlugin = async (ctx) => {
                         mode: "primary",
                         prompt: implementerPrompt,
                         permission: {
+                            "read": {
+                                "*": "allow",
+                                "*.env": "deny",
+                                "*.env.*": "deny",
+                                "*.env.example": "allow"
+                            },
                             bash: "allow",
                             edit: "allow",
                             webfetch: "allow",
                             external_directory: "deny",
+                            list: "allow",
+                            "conductor_delegate": "allow",
+                            "conductor_bg_task": "allow",
+                            "conductor_bg_output": "allow",
+                            "conductor_bg_cancel": "allow",
+                            grep: "allow",
+                            glob: "allow",
+                            todowrite: "allow",
+                            todoread: "allow",
                         },
                         tools: {
                             bash: true,

package/dist/prompts/agent/conductor.md

@@ -36,4 +36,4 @@ Your mission is to ensure that every change to the codebase is driven by a forma
 - **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.
 
-**CRITCAL: YOU MUST FOLLOW THE INSTRUCTIONS PROVIDED IN THE COMMAND TEMPLATES EXACTLY. DO NOT PAUSE IN THE MIDDLE OF A SEQUENCE.**
+**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.**

package/dist/prompts/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.
 
 ---
@@ -29,8 +27,9 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
 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.
+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.    
 
 3.  **Continue:** Immediately proceed to the next step to select a track.
 
@@ -45,10 +44,13 @@ 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 and await further 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.
 
 ---
 
@@ -63,18 +65,19 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
 3.  **Load Track Context:**
     a. **Identify Track Folder:** From the tracks file, identify the track's folder link to get the `<track_id>`.
-    b. **Read Files:** You MUST use the `read` tool to read the content of the following files into your context using their full, absolute paths:
+    b. **Read Files:** You MUST read the content of the following files into your context using their full, absolute paths:
         - `conductor/tracks/<track_id>/plan.md`
         - `conductor/tracks/<track_id>/spec.md`
         - `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>`).
     -   Announce that the track is fully complete and the tracks file has been updated.

package/dist/prompts/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
@@ -90,8 +88,8 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
     > "Now I will create an implementation plan (plan.md) based on the specification."
 
 2.  **Generate Plan:**
-    *   Use the `read` tool to read the confirmed `spec.md` content for this track.
-    *   Use the `read` tool to read the selected workflow file from `conductor/workflow.md`.
+    *   Read the confirmed `spec.md` content for this track.
+    *   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.
@@ -109,7 +107,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, use the `list` tool to 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.
+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.
 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:
@@ -125,8 +123,8 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
     ```
     *   Populate fields with actual values. Use the current timestamp.
 5.  **Write Files:**
-    *   Use the `write` tool to write the confirmed specification content to `conductor/tracks/<track_id>/spec.md`.
-    *   Use the `write` tool to write the confirmed plan content to `conductor/tracks/<track_id>/plan.md`.
+    *   Write the confirmed specification content to `conductor/tracks/<track_id>/spec.md`.
+    *   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:

package/dist/prompts/status.toml

@@ -31,8 +31,8 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 **PROTOCOL: Follow this sequence to provide a status overview.**
 
 ### 2.1 Read Project Plan
-1.  **Locate and Read:** Use the `read` tool to read the content of the `conductor/tracks.md` file.
-2.  **Locate and Read:** List the tracks using the `list` tool on `conductor/tracks`. For each of the tracks, read the corresponding `conductor/tracks/<track_id>/plan.md` file using the `read` tool.
+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.2 Parse and Summarize Plan
 1.  **Parse Content:**

package/package.json

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