create-conductor-flow 0.0.1 → 0.0.2

package/dist/conductor/commands/conductor/implement.toml

@@ -15,7 +15,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
     -   **Tech Stack**
     -   **Workflow**
 
-2.  **Handle Failure:** If ANY of these are missing (or their resolved paths do not exist), Announce: "Conductor is not set up. Please run `/conductor-setup`." and HALT.
+2.  **Handle Failure:** If ANY of these are missing (or their resolved paths do not exist), Announce: "Conductor is not set up. Please run `/conductor:setup`." and HALT.
 
 
 ---
@@ -23,7 +23,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.  **Locate and Parse Tracks Registry:**
     -   Resolve the **Tracks Registry**.
@@ -156,7 +156,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
 3.  **Handle User Response:**
     *   **If user chooses "A" (Review):**
-        *   Announce: "Please run `/conductor-review` to verify your changes. You will be able to archive or delete the track after the review."
+        *   Announce: "Please run `/conductor:review` to verify your changes. You will be able to archive or delete the track after the review."
     *   **If user chooses "B" (Archive):**
         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 its current location (resolved via the **Tracks Directory**) to `conductor/archive/<track_id>`.

package/dist/conductor/commands/conductor/newTrack.toml

@@ -17,7 +17,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
 2.  **Handle Failure:**
     -   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.
 
 ---
@@ -152,6 +152,6 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
     -   **Announce:** Inform the user you are committing the **Tracks Registry** changes.
     -   **Commit Changes:** Stage the **Tracks Registry** files and commit with the message `chore(conductor): Add new track '<track_description>'`.
 8.  **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/conductor/commands/conductor/revert.toml

@@ -20,7 +20,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
 2.  **Verify Track Exists:** Check if the **Tracks Registry** is not empty.
 
-3.  **Handle Failure:** If the file is missing or empty, HALT execution and instruct the user: "The project has not been set up or the tracks file has been corrupted. Please run `/conductor-setup` to set up the plan, or restore the tracks file."
+3.  **Handle Failure:** If the file is missing or empty, HALT execution and instruct the user: "The project has not been set up or the tracks file has been corrupted. Please run `/conductor:setup` to set up the plan, or restore the tracks file."
 
 ---
 
@@ -29,7 +29,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
 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/conductor/commands/conductor/review.toml

@@ -26,7 +26,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
 2.  **Handle Failure:**
     -   If ANY of these files are missing, list the missing files, then 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 Review Protocol.
 
 ---

package/dist/conductor/commands/conductor/setup.toml

@@ -26,7 +26,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.
 
@@ -452,5 +452,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/conductor/commands/conductor/status.toml

@@ -19,7 +19,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
 2.  **Handle Failure:**
     -   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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-conductor-flow",
-  "version": "0.0.1",
+  "version": "0.0.2",
   "description": "Conductor Scaffolding CLI - Generate spec-driven, portable Gemini Conductor workflows for any coding agent",
   "license": "Apache-2.0",
   "keywords": [
@@ -45,6 +45,7 @@
   },
   "type": "module",
   "bin": {
+    "create-conductor-flow": "dist/index.js",
     "conductor-init": "dist/index.js"
   },
   "files": [