create-conductor-flow 0.0.1

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,166 @@
+# Conductor Init
+
+[![npm version](https://badge.fury.io/js/conductor-init.svg)](https://badge.fury.io/js/conductor-init)
+
+<img src="./conductor_init_banner.png" height="400" alt="Conductor Init Banner" />
+
+[English](./README.md) | [中文](./README_zh.md) | [日本語](./README_ja.md) | [한국어](./README_ko.md)
+
+**Conductor Init** is a **Conductor Scaffolding CLI** that generates spec-driven, portable **Gemini [Conductor](https://github.com/gemini-cli-extensions/conductor)** workflows for **any** AI coding agent via `npx`. It enables the **[context-first evolution of spec-driven development](https://blog.jonkimi.com/2026/02/01/en/Vibe-Coding-with-context-driven-development-using-Conductor-for-Gemini-CLI/)** for **Claude Code**, **OpenCode**, **Cursor**, **Kilo Code**, and other leading AI Coding Assistants.
+
+Originally developed for the Gemini CLI, the **Conductor** is now decoupled by this project, **empowering developers to maintain context, manage tasks, and orchestrate complex features**. It serves as a bridge between human intent and AI execution, ensuring "Context is King" in the era of Agentic AI.
+
+## 🎯 Goals
+
+-   **Universal Compatibility:** Enable the Conductor methodology outside of the Gemini CLI ecosystem.
+-   **Agent-Agnostic Setup:** Provide a mechanism to "install" Conductor commands and templates into a project, effectively "enabling" it for consumption by multiple different coding agents.
+-   **Standardization:** Create a unified interface for project orchestration that bridges the gap between human intent and AI execution.
+
+## ✨ Key Features
+
+-   **Universal AI Compatibility**: Works out-of-the-box with **Opencode**, **Claude Code**, **Antigravity**, **Cursor**, **VS Code Copilot**, **Codex**, **Windsurf**, **Cline**, **Kilo Code**, **Roo Code**, **Qwen Code**, **Factory Droid**, and **Gemini CLI**.
+-   **Context Management**: Structured artifacts (`spec.md`, `plan.md`) keep your AI agent focused and context-aware.
+-   **Spec-Driven Development**: Define *what* you want before asking the AI *how* to build it.
+-   **Agent-Agnostic Workflows**: Switch between agents without losing project context or progress.
+-   **Easy Initialization**: Single command setup with `npx conductor-init`.
+-   **Git Ignore Configuration**: Automatically configure `.gitignore` or `.git/info/exclude` to exclude agent configuration files from version control.
+
+## 🚀 Usage
+
+### 1. Setup Conductor in Your Project
+
+```text
+conductor-init [path] [options]
+
+Positionals:
+  path  Directory to install Conductor                   [string] [default: "."]
+
+Options:
+  -a, --agent       Specify the coding agent
+          [string] [choices: "opencode", "claude-code", "antigravity", "cursor",
+        "vscode-copilot", "codex", "windsurf", "cline", "kilo-code", "roo-code",
+                                         "qwen-code", "factory-droid", "gemini"]
+  -r, --repo        Git repository URL for conductor. If used without value,
+                    defaults to official repository.                    [string]
+  -b, --branch      Branch name for conductor repository
+                                                      [string] [default: "main"]
+  -s, --scope       Installation scope (project or global)
+                                         [string] [choices: "project", "global"]
+  -g, --git-ignore  Configure git ignore for Conductor files (gitignore: add to
+                    .gitignore, exclude: add to .git/info/exclude, none: remove
+                    entries)  [string] [choices: "gitignore", "exclude", "none"]
+  -f, --force       Force overwrite existing installation
+                                                      [boolean] [default: false]
+  -h, --help        Show help                                          [boolean]
+  -v, --version     Show version number                                [boolean]
+
+Examples:
+  conductor-init                         Install with interactive prompts
+  conductor-init --agent claude-code     Install for Claude Code agent
+  conductor-init --git-ignore gitignore  Add Conductor files to .gitignore
+  conductor-init --git-ignore exclude    Add Conductor files to
+                                         .git/info/exclude
+  conductor-init --git-ignore none       Remove Conductor entries from git
+                                         ignore
+```
+
+To initialize Conductor in your project, simply run the following command in your project root:
+
+```bash
+npx conductor-init
+```
+
+You can also specify a custom template repository and branch:
+
+```bash
+npx conductor-init --repo https://github.com/your-org/custom-conductor --branch v2
+```
+
+Or specify the agent directly:
+
+```bash
+npx conductor-init --agent claude-code
+```
+
+### 2. Alternative: Build from Source
+
+If you prefer to build from source:
+
+```bash
+pnpm install
+pnpm build
+node dist/index.js
+```
+
+You will be prompted to select your AI Coding Agent:
+-   **Opencode**
+-   **Claude Code**
+-   **Antigravity**
+-   **Cursor**
+-   **VS Code Copilot**
+-   **Codex**
+-   **Windsurf**
+-   **Cline**
+-   **Kilo Code**
+-   **Roo Code**
+-   **Qwen Code**
+-   **Factory Droid**
+-   **Gemini CLI**
+
+This will verify the environment and install the necessary Conductor files:
+-   **Commands:** Agent-specific prompt or command files (e.g., `.opencode/commands/conductor-setup.md` or `.gemini/commands/setup.toml`) that your agent can execute.
+-   **Templates:** Workflow guides and style guides (e.g., `.opencode/conductor/templates/`).
+
+### 3. Shell Completion
+
+Enable tab completion for specific shells (Bash, Zsh) to make using `conductor-init` easier.
+
+#### Zsh (Recommended)
+
+**Option 1: Source from file (Best for performance)**
+
+Generate the script to a file and source it in your `.zshrc`:
+
+```zsh
+mkdir -p ~/.config/conductor
+conductor-init completion > ~/.config/conductor/completion.zsh
+echo 'source ~/.config/conductor/completion.zsh' >> ~/.zshrc
+source ~/.zshrc
+```
+
+**Option 2: One-liner**
+
+Add this directly to your `.zshrc` (easiest setup):
+
+```zsh
+echo 'source <(conductor-init completion)' >> ~/.zshrc
+source ~/.zshrc
+```
+
+#### Bash
+
+Add the completion script to your `.bashrc`:
+
+```bash
+conductor-init completion >> ~/.bashrc
+source ~/.bashrc
+```
+
+### 4. Using Conductor with Your Agent
+
+Once installed, you can instruct your AI Agent to perform Conductor tasks using the installed commands. For example:
+
+-   `/conductor-setup` - Initialize the project structure.
+-   `/conductor-newTrack` - Start a new feature or bug fix track.
+-   `/conductor-implement` - Implement the selected track.
+-   `/conductor-review` - Review the completed track work against guidelines and the plan.
+-   `/conductor-revert` - Revert previous work.
+-   `/conductor-status` - Check the status of current tracks.
+
+*Note: The exact invocation syntax depends on your specific agent's slash command or file context capabilities.*
+
+
+
+## 🙏 Acknowledgements
+
+This project is inspired by and based on the [Conductor](https://github.com/gemini-cli-extensions/conductor) and [Conductor-for-all](https://github.com/hlhr202/Conductor-for-all).

package/dist/conductor/GEMINI.md

@@ -0,0 +1,41 @@
+# Conductor Context
+
+If a user mentions a "plan" or asks about the plan, and they have used the conductor extension in the current session, they are likely referring to the `conductor/tracks.md` file or one of the track plans (`conductor/tracks/<track_id>/plan.md`).
+
+## Universal File Resolution Protocol
+
+**PROTOCOL: How to locate files.**
+To find a file (e.g., "**Product Definition**") within a specific context (Project Root or a specific Track):
+
+1.  **Identify Index:** Determine the relevant index file:
+    -   **Project Context:** `conductor/index.md`
+    -   **Track Context:**
+        a. Resolve and read the **Tracks Registry** (via Project Context).
+        b. Find the entry for the specific `<track_id>`.
+        c. Follow the link provided in the registry to locate the track's folder. The index file is `<track_folder>/index.md`.
+        d. **Fallback:** If the track is not yet registered (e.g., during creation) or the link is broken:
+            1. Resolve the **Tracks Directory** (via Project Context).
+            2. The index file is `<Tracks Directory>/<track_id>/index.md`.
+
+2.  **Check Index:** Read the index file and look for a link with a matching or semantically similar label.
+
+3.  **Resolve Path:** If a link is found, resolve its path **relative to the directory containing the `index.md` file**.
+    -   *Example:* If `conductor/index.md` links to `./workflow.md`, the full path is `conductor/workflow.md`.
+
+4.  **Fallback:** If the index file is missing or the link is absent, use the **Default Path** keys below.
+
+5.  **Verify:** You MUST verify the resolved file actually exists on the disk.
+
+**Standard Default Paths (Project):**
+- **Product Definition**: `conductor/product.md`
+- **Tech Stack**: `conductor/tech-stack.md`
+- **Workflow**: `conductor/workflow.md`
+- **Product Guidelines**: `conductor/product-guidelines.md`
+- **Tracks Registry**: `conductor/tracks.md`
+- **Tracks Directory**: `conductor/tracks/`
+
+**Standard Default Paths (Track):**
+- **Specification**: `conductor/tracks/<track_id>/spec.md`
+- **Implementation Plan**: `conductor/tracks/<track_id>/plan.md`
+- **Metadata**: `conductor/tracks/<track_id>/metadata.json`
+

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

@@ -0,0 +1,179 @@
+description = "Executes the tasks defined in the specified track's plan"
+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.
+
+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
+**PROTOCOL: Verify that the Conductor environment is properly set up.**
+
+1.  **Verify Core Context:** Using the **Universal File Resolution Protocol**, resolve and verify the existence of:
+    -   **Product Definition**
+    -   **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.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>`).
+
+2.  **Locate and Parse Tracks Registry:**
+    -   Resolve the **Tracks Registry**.
+    -   Read and parse this file. 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.
+
+3.  **Continue:** Immediately proceed to the next step to select a track.
+
+4.  **Select Track:**
+    -   **If a track name was provided:**
+        1.  Perform an exact, case-insensitive match for the provided name against the track descriptions you parsed.
+        2.  If a unique match is found, confirm the selection with the user: "I found track '<track_description>'. Is this correct?"
+        3.  If no match is found, or if the match is ambiguous, inform the user and ask for clarification. Suggest the next available track as below.
+    -   **If no track name was provided (or if the previous step failed):**
+        1.  **Identify Next Track:** Find the first track in the parsed tracks file that is NOT marked as `[x] Completed`.
+        2.  **If a next track is found:**
+            -   Announce: "No track name provided. Automatically selecting the next incomplete track: '<track_description>'."
+            -   Proceed with this track.
+        3.  **If no incomplete tracks are found:**
+            -   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.
+
+---
+
+## 3.0 TRACK IMPLEMENTATION
+**PROTOCOL: Execute the selected track.**
+
+1.  **Announce Action:** Announce which track you are beginning to implement.
+
+2.  **Update Status to 'In Progress':**
+    -   Before beginning any work, you MUST update the status of the selected track in the **Tracks Registry** file.
+    -   This requires finding the specific heading for the track (e.g., `## [ ] Track: <Description>`) and replacing it with the updated status (e.g., `## [~] Track: <Description>`) in the **Tracks Registry** file you identified earlier.
+
+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:**
+        -   **Track Context:** Using the **Universal File Resolution Protocol**, resolve and read the **Specification** and **Implementation Plan** for the selected track.
+        -   **Workflow:** Resolve **Workflow** (via the **Universal File Resolution Protocol** using the project's index file).
+    c. **Error Handling:** If you fail to read any of these files, you MUST stop and inform the user of the error.
+
+4.  **Execute Tasks and Update Track Plan:**
+    a. **Announce:** State that you will now execute the tasks from the track's **Implementation Plan** by following the procedures in the **Workflow**.
+    b. **Iterate Through Tasks:** You MUST now loop through each task in the track's **Implementation Plan** one by one.
+    c. **For Each Task, You MUST:**
+        i. **Defer to Workflow:** The **Workflow** 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** file you have in your context. Follow its steps for implementation, testing, and committing precisely.
+
+5.  **Finalize Track:**
+    -   After all tasks in the track's local **Implementation Plan** are completed, you MUST update the track's status in the **Tracks Registry**.
+    -   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 the **Tracks Registry** file 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.
+
+---
+
+## 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.
+
+2.  **Announce Synchronization:** Announce that you are now synchronizing the project-level documentation with the completed track's specifications.
+
+3.  **Load Track Specification:** Read the track's **Specification**.
+
+4.  **Load Project Documents:**
+    -   Resolve and read:
+        -   **Product Definition**
+        -   **Tech Stack**
+        -   **Product Guidelines**
+
+5.  **Analyze and Update:**
+    a.  **Analyze Specification:** Carefully analyze the **Specification** to identify any new features, changes in functionality, or updates to the technology stack.
+    b.  **Update Product Definition:**
+        i. **Condition for Update:** Based on your analysis, you MUST determine if the completed feature or bug fix significantly impacts the description of the product itself.
+        ii. **Propose and Confirm Changes:** If an update is needed, generate the proposed changes. Then, present them to the user for confirmation:
+            > "Based on the completed track, I propose the following updates to the **Product Definition**:"
+            > ```diff
+            > [Proposed changes here, ideally in a diff format]
+            > ```
+            > "Do you approve these changes? (yes/no)"
+        iii. **Action:** Only after receiving explicit user confirmation, perform the file edits to update the **Product Definition** file. Keep a record of whether this file was changed.
+    c.  **Update Tech Stack:**
+        i. **Condition for Update:** Similarly, you MUST determine if significant changes in the technology stack are detected as a result of the completed track.
+        ii. **Propose and Confirm Changes:** If an update is needed, generate the proposed changes. Then, present them to the user for confirmation:
+            > "Based on the completed track, I propose the following updates to the **Tech Stack**:"
+            > ```diff
+            > [Proposed changes here, ideally in a diff format]
+            > ```
+            > "Do you approve these changes? (yes/no)"
+        iii. **Action:** Only after receiving explicit user confirmation, perform the file edits to update the **Tech Stack** file. Keep a record of whether this file was changed.
+    d. **Update Product Guidelines (Strictly Controlled):**
+        i. **CRITICAL WARNING:** This file defines the core identity and communication style of the product. It should be modified with extreme caution and ONLY in cases of significant strategic shifts, such as a product rebrand or a fundamental change in user engagement philosophy. Routine feature updates or bug fixes should NOT trigger changes to this file.
+        ii. **Condition for Update:** You may ONLY propose an update to this file if the track's **Specification** explicitly describes a change that directly impacts branding, voice, tone, or other core product guidelines.
+        iii. **Propose and Confirm Changes:** If the conditions are met, you MUST generate the proposed changes and present them to the user with a clear warning:
+            > "WARNING: The completed track suggests a change to the core **Product Guidelines**. This is an unusual step. Please review carefully:"
+            > ```diff
+            > [Proposed changes here, ideally in a diff format]
+            > ```
+            > "Do you approve these critical changes to the **Product Guidelines**? (yes/no)"
+        iv. **Action:** Only after receiving explicit user confirmation, perform the file edits. Keep a record of whether this file was changed.
+
+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 Definition**, **Tech Stack**, or **Product Guidelines**), you MUST stage them and commit them.
+        - **Commit Message:** `docs(conductor): Synchronize docs for track '<track_description>'`
+    - **Example (if Product Definition was changed, but others were not):**
+        > "Documentation synchronization is complete.
+        > - **Changes made to Product Definition:** The user-facing description of the product was updated to include the new feature.
+        > - **No changes needed for Tech Stack:** The technology stack was not affected.
+        > - **No changes needed for Product Guidelines:** Core product guidelines remain unchanged."
+    - **Example (if no files were changed):**
+        > "Documentation synchronization is complete. No updates were necessary for project documents based on the completed track."
+
+---
+
+## 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.
+
+2.  **Ask for User Choice:** You MUST prompt the user with the available options for the completed track.
+    > "Track '<track_description>' is now complete. What would you like to do?
+    > A.  **Review (Recommended):** Run the review command to verify changes before finalizing.
+    > B.  **Archive:** Move the track's folder to `conductor/archive/` and remove it from the tracks file.
+    > C.  **Delete:** Permanently delete the track's folder and remove it from the tracks file.
+    > D.  **Skip:** Do nothing and leave it in the tracks file.
+    > Please enter the option of your choice (A, B, C, or D)."
+
+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."
+    *   **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>`.
+        iii. **Remove from Tracks File:** Read the content of the **Tracks Registry** file, 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.  **Commit Changes:** Stage the **Tracks Registry** file 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 "C" (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)"
+        ii. **Handle Confirmation:**
+            - **If 'yes'**:
+                a. **Delete Track Folder:** Resolve the **Tracks Directory** and permanently delete the track's folder from `<Tracks Directory>/<track_id>`.
+                b. **Remove from Tracks File:** Read the content of the **Tracks Registry** file, remove the entire section for the completed track, and write the modified content back to the file.
+                c. **Commit Changes:** Stage the **Tracks Registry** file and the deletion of the track directory. 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 "D" (Skip) or provides any other input:**
+        *   Announce: "Okay, the completed track will remain in your tracks file for now."
+"""