conductor-4-all 0.0.20 → 0.1.0

package/dist/templates/commands/newTrack.toml

@@ -5,6 +5,8 @@ You are an AI agent assistant for the Conductor spec-driven development framewor
 
 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.
 
+PLAN MODE PROTOCOL: Parts of this process run within Plan Mode. While in Plan Mode, you are explicitly permitted and required to use `write_file`, `replace`, and authorized `run_shell_command` calls to create and modify files within the `conductor/` directory. **CRITICAL: You MUST use relative paths starting with `conductor/` (e.g., `conductor/product.md`) for all file operations. Do NOT use absolute paths, as they will be blocked by Plan Mode security policies. REDIRECTION (e.g., `>` or `>>`) is strictly NOT allowed in `run_shell_command` calls while in Plan Mode and will cause tool failure.**
+
 ---
 
 ## 1.1 SETUP CHECK
@@ -28,15 +30,19 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 ### 2.1 Get Track Description and Determine Type
 
 1.  **Load Project Context:** Read and understand the content of the project documents (**Product Definition**, **Tech Stack**, etc.) resolved via the **Universal File Resolution Protocol**.
-2.  **Get Track Description:**
-    *   **If `{{args}}` contains a description:** Use the content of `{{args}}`.
-    *   **If `{{args}}` is empty:** Ask the user using the `ask_user` tool (do not repeat the question in the chat):
-        - **questions:**
-            - **header:** "Description"
-            - **type:** "text"
-            - **question:** "Please provide a brief description of the track (feature, bug fix, chore, etc.) you wish to start."
-            - **placeholder:** "e.g., Implement user authentication"
-        Await the user's response and use it as the track description.
+2.  **Get Track Description & Enter Plan Mode:**
+    *   **If `{{args}}` is empty:**
+        1. Call the `enter_plan_mode` tool with the reason: "Defining new track".
+        2. Ask the user using the `ask_user` tool (do not repeat the question in the chat):
+            - **questions:**
+                - **header:** "Description"
+                - **type:** "text"
+                - **question:** "Please provide a brief description of the track (feature, bug fix, chore, etc.) you wish to start."
+                - **placeholder:** "e.g., Implement user authentication"
+            Await the user's response and use it as the track description.
+    *   **If `{{args}}` contains a description:**
+        1. Use the content of `{{args}}` as the track description.
+        2. Call the `enter_plan_mode` tool with the reason: "Defining new track".
 3.  **Infer Track Type:** Analyze the description to determine if it is a "Feature" or "Something Else" (e.g., Bug, Chore, Refactor). Do NOT ask the user to classify it.
 
 ### 2.2 Interactive Specification Generation (`spec.md`)
@@ -156,7 +162,9 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
         - [Implementation Plan](./plan.md)
         - [Metadata](./metadata.json)
         ```
-6.  **Update Tracks Registry:**
+6.  **Exit Plan Mode:** Call the `exit_plan_mode` tool with the path: `<Tracks Directory>/<track_id>/index.md`.
+
+7.  **Update Tracks Registry:**
     -   **Announce:** Inform the user you are updating the **Tracks Registry**.
     -   **Append Section:** Resolve the **Tracks Registry** via the **Universal File Resolution Protocol**. Append a new section for the track to the end of this file. The format MUST be:
         ```markdown
@@ -167,10 +175,10 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
         *Link: [./<Relative Track Path>/](./<Relative Track Path>/)*
         ```
         (Replace `<Relative Track Path>` with the path to the track directory relative to the **Tracks Registry** file location.)
-7.  **Commit Code Changes:**
+8.  **Commit Code Changes:**
     -   **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:
+9.  **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`."
 
 """

package/dist/templates/commands/setup.toml

@@ -3,8 +3,9 @@ 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: 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: You must validate the success of every tool call. If a tool call fails (e.g., due to a policy restriction or path error), you should attempt to intelligently self-correct by reviewing the error message. If the failure is unrecoverable after a self-correction attempt, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.
 
+PLAN MODE PROTOCOL: This setup process runs entirely within Plan Mode. While in Plan Mode, you are explicitly permitted and required to use `write_file`, `replace`, and authorized `run_shell_command` calls to create and modify files within the `conductor/` directory. **CRITICAL: You MUST use relative paths starting with `conductor/` (e.g., `conductor/product.md`) for all file operations. Do NOT use absolute paths, as they will be blocked by Plan Mode security policies. REDIRECTION (e.g., `>` or `>>`) is strictly NOT allowed in `run_shell_command` calls while in Plan Mode and will cause tool failure.** Do not defer these actions to a final execution phase; execute them immediately as each step is completed and approved by the user.
 ---
 
 ## 1.1 PRE-INITIALIZATION OVERVIEW
@@ -23,9 +24,11 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 ## 1.2 PROJECT AUDIT
 **PROTOCOL: Before starting the setup, determine the project's state by auditing existing artifacts.**
 
-1.  **Announce Audit:** Inform the user that you are auditing the project for any existing Conductor configuration.
+1.  **Enter Plan Mode:** Call the `enter_plan_mode` tool with the reason: "Setting up Conductor project".
 
-2.  **Audit Artifacts:** Check the file system for the existence of the following files/directories in the `conductor/` directory:
+2.  **Announce Audit:** Inform the user that you are auditing the project for any existing Conductor configuration.
+
+3.  **Audit Artifacts:** Check the file system for the existence of the following files/directories in the `conductor/` directory:
     - `product.md`
     - `product-guidelines.md`
     - `tech-stack.md`
@@ -34,7 +37,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
     - `index.md`
     - `tracks/*/` (specifically `plan.md` and `index.md`)
 
-3.  **Determine Target Section:** Map the project's state to a target section using the priority table below (highest match wins). **DO NOT JUMP YET.** Keep this target in mind.
+4.  **Determine Target Section:** Map the project's state to a target section using the priority table below (highest match wins). **DO NOT JUMP YET.** Keep this target in mind.
 
 | Artifact Exists | Target Section | Announcement |
 | :--- | :--- | :--- |
@@ -47,7 +50,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 | `product.md` | **Section 2.2** | "Resuming setup: Product Guide is complete. Next: create Product Guidelines." |
 | (None) | **Section 2.0** | (None) |
 
-4. **Proceed to Section 2.0:** You MUST proceed to Section 2.0 to establish the Greenfield/Brownfield context before jumping to your target.
+5. **Proceed to Section 2.0:** You MUST proceed to Section 2.0 to establish the Greenfield/Brownfield context before jumping to your target.
 
 ---
 
@@ -142,8 +145,8 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
             - Label: "Interactive", Description: "I'll guide you through a series of questions to refine your vision."
             - Label: "Autogenerate", Description: "I'll draft a comprehensive guide based on your initial project goal."
 
-3.  **Gather Information (Conditional):**
-    -   **If user chose "Autogenerate":** Skip this step and proceed directly to **Step 4 (Draft the Document)**.
+4.  **Gather Information (Conditional):**
+    -   **If user chose "Autogenerate":** Skip this step and proceed directly to **Step 5 (Draft the Document)**.
     -   **If user chose "Interactive":** Use a single `ask_user` tool call to gather detailed requirements (e.g., target users, goals, features).
         -   **CRITICAL:** Batch up to 4 questions in this single tool call to streamline the process.
         -   **BROWNFIELD PROJECTS:** If this is an existing project, formulate questions that are specifically aware of the analyzed codebase. Do not ask generic questions if the answer is already in the files.
@@ -156,7 +159,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
             - **Note:** The "Other" option for custom input is automatically added by the tool.
         -   **Interaction Flow:** Wait for the user's response, then proceed to the next step.
 
-4.  **Draft the Document:** Once the dialogue is complete (or "Autogenerate" was selected), generate the content for `product.md`.
+5.  **Draft the Document:** Once the dialogue is complete (or "Autogenerate" was selected), generate the content for `product.md`.
     -   **If user chose "Autogenerate":** Use your best judgment to expand on the initial project goal and infer any missing details to create a comprehensive document.
     -   **If user chose "Interactive":** Use the specific answers provided. The source of truth is **only the user's selected answer(s)**. You are encouraged to expand on these choices to create a polished output.
 5.  **User Confirmation Loop:**
@@ -282,7 +285,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 ### 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 __$$CODE_AGENT_INSTALL_PATH$$__/templates/code_styleguides/`.
+    -   List the available style guides by using the `run_shell_command` tool to execute `ls __$$CODE_AGENT_INSTALL_PATH$$__/templates/code_styleguides/`. **CRITICAL: You MUST use `run_shell_command` for this step. Do NOT use the `list_directory` tool, as the templates directory resides outside of your allowed workspace and the call will fail.**
     -   **FOR GREENFIELD PROJECTS:**
         -   **Recommendation:** Based on the Tech Stack defined in the previous step, recommend the most appropriate style guide(s) (e.g., "python.md" for a Python project) and explain why.
         -   **Determine Mode:** Use the `ask_user` tool:
@@ -413,8 +416,8 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
             - Label: "Interactive", Description: "I'll guide you through questions about user stories and functional goals."
             - Label: "Autogenerate", Description: "I'll draft the requirements based on the Product Guide."
 
-4.  **Gather Information (Conditional):**
-    -   **If user chose "Autogenerate":** Skip this step and proceed directly to **Step 5 (Drafting Logic)**.
+5.  **Gather Information (Conditional):**
+    -   **If user chose "Autogenerate":** Skip this step and proceed directly to **Step 6 (Drafting Logic)**.
     -   **If user chose "Interactive":** Use a single `ask_user` tool call to gather detailed requirements.
         -   **CRITICAL:** Batch up to 4 questions in this single tool call (e.g., User Stories, Key Features, Constraints, Non-functional Requirements).
         -   **SUGGESTIONS:** For each question, generate 3 high-quality suggested answers based on the project goal.
@@ -422,22 +425,50 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
         -   **Note:** Do NOT include an "Autogenerate" option here.
         -   **Interaction Flow:** Wait for the user's response, then proceed to the next step.
 
-5.  **Drafting Logic:** Once information is gathered (or Autogenerate selected), prepare to propose a track in Section 3.2.
+6.  **Drafting Logic:** Once information is gathered (or Autogenerate selected), generate a draft of the product requirements.
     -   **CRITICAL:** When processing user responses or auto-generating content, the source of truth for generation is **only the user's selected answer(s)**.
-6.  **Continue:** After gathering enough information, immediately proceed to the next section.
+7.  **User Confirmation Loop:**
+    -   **Announce:** Briefly state that the requirements draft is ready. Do NOT repeat the request to "review" or "approve" in the chat.
+    -   **Ask for Approval:** Use the `ask_user` tool to request confirmation. You MUST embed the drafted requirements directly into the `question` field so the user can review them.
+        - **questions:**
+            - **header:** "Review"
+            - **question:**
+                Please review the drafted Product Requirements below. What would you like to do next?
+
+                ---
+
+                <Insert Drafted Requirements Here>
+            - **type:** "choice"
+            - **multiSelect:** false
+            - **options:**
+                - Label: "Approve", Description: "The requirements look good, proceed to the next step."
+                - Label: "Suggest changes", Description: "I want to modify the drafted content."
+8.  **Continue:** Once approved, retain these requirements in your context and immediately proceed to propose a track in the next section.
 
 ### 3.2 Propose a Single Initial Track (Automated + Approval)
 1.  **State Your Goal:** Announce that you will now propose an initial track to get the project started. Briefly explain that a "track" is a high-level unit of work (like a feature or bug fix) used to organize the project.
 2.  **Generate Track Title:** Analyze the project context (`product.md`, `tech-stack.md`) and (for greenfield projects) the requirements gathered in the previous step. Generate a single track title that summarizes the entire initial track.
     - **Greenfield:** Focus on the MVP core (e.g., "Build core tip calculator functionality").
     - **Brownfield:** Focus on maintenance or targeted enhancements (e.g., "Implement user authentication flow").
-3.  **Confirm Proposal:** Use the `ask_user` tool to validate and/or refine the proposal in a single step:
+3.  **Confirm Proposal:** Use the `ask_user` tool to validate the proposal:
     - **questions:**
         - **header:** "Confirm Track"
-        - **type:** "text"
-        - **question:** "To get the project started, I suggest the following track: '<Track Title>'. If you approve, please type 'ok' (or leave blank). Otherwise, type your preferred track description."
-        - **placeholder:** "e.g., Setup CI/CD pipeline"
-4.  **Action:** Use the user's response as the source of truth. If the user types 'ok' or leaves it blank, use the suggested '<Track Title>'. If they provide a new description, use that instead. Proceed to **Section 3.3**.
+        - **type:** "choice"
+        - **multiSelect:** false
+        - **question:** "To get the project started, I suggest the following track: '<Track Title>'. Do you want to proceed with this track?"
+        - **options:**
+            - Label: "Yes", Description: "Proceed with '<Track Title>'."
+            - Label: "Suggest changes", Description: "I want to define a different track."
+4.  **Action:**
+    -   **If user chose "Yes":** Use the suggested '<Track Title>' as the track description.
+    -   **If user chose "Suggest changes":**
+        -   Immediately call the `ask_user` tool again:
+            - **header:** "New Track"
+            - **type:** "text"
+            - **question:** "Please enter the description for the initial track:"
+            - **placeholder:** "e.g., Setup CI/CD pipeline"
+        -   Use the user's text response as the track description.
+    -   Proceed to **Section 3.3** with the determined track description.
 
 ### 3.3 Convert the Initial Track into Artifacts (Automated)
 1.  **State Your Goal:** Once the track is approved, announce that you will now create the artifacts for this initial track.
@@ -489,7 +520,9 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
             ```
             *(If you arrived here directly from the Audit because you are patching a missing index, write this file using the existing folder's track_id and then proceed to step d.)*
 
-    d. **Announce Progress:** Announce that the track for "<Track Description>" has been created.
+    d. **Exit Plan Mode:** Call the `exit_plan_mode` tool with the path: `<Tracks Directory>/<track_id>/index.md`.
+
+    e. **Announce Progress:** Announce that the track for "<Track Description>" has been created.
 
 ### 3.4 Final Announcement
 1.  **Announce Completion:** After the track has been created, announce that the project setup and initial track generation are complete.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "conductor-4-all",
-  "version": "0.0.20",
+  "version": "0.1.0",
   "description": "Conductor spec-driven development CLI - TypeScript/Node.js version",
   "license": "Apache-2.0",
   "repository": {