MediaMetz/gemini-cli
1
0
Fork 0
mirror of https://github.com/google-gemini/gemini-cli.git synced 2026-03-27 06:20:52 -07:00
Code Issues Packages Projects Releases Wiki Activity

feat(cli): rename conductor commands to /spec

Browse Source
This commit is contained in:
Jerop Kipruto
2026-03-17 11:51:52 -04:00
parent 889d2fca97
commit b84596796f
8 changed files with 35 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
packages/core/src/extensions/builtin/conductor/commands/conductor/newTrack.toml → packages/core/src/extensions/builtin/conductor/commands/spec/create.toml
View File

@@ -19,7 +19,7 @@ PLAN MODE PROTOCOL: Parts of this process run within Plan Mode. While in Plan Mo
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 `/spec setup` to set up the environment."
- Do NOT proceed to New Track Initialization.
---
@@ -179,6 +179,6 @@ PLAN MODE PROTOCOL: Parts of this process run within Plan Mode. While in Plan Mo
- **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>'`.
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`."
> "New track '<track_id>' has been created and added to the tracks file. You can now start implementation by running `/spec implement`."
"""

6
packages/core/src/extensions/builtin/conductor/commands/conductor/implement.toml → packages/core/src/extensions/builtin/conductor/commands/spec/implement.toml
View File

@@ -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 `/spec 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., `/spec implement <track_description>`).
2. **Locate and Parse Tracks Registry:**
- Resolve the **Tracks Registry**.
@@ -192,7 +192,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
3. **Handle User Response:**
* **If user chooses "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 `/spec review` to verify your changes. You will be able to archive or delete the track after the review."
* **If user chooses "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>`.

4
packages/core/src/extensions/builtin/conductor/commands/conductor/revert.toml → packages/core/src/extensions/builtin/conductor/commands/spec/revert.toml
View File

@@ -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 `/spec 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., `/spec 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.

2
packages/core/src/extensions/builtin/conductor/commands/conductor/review.toml → packages/core/src/extensions/builtin/conductor/commands/spec/review.toml
View File

@@ -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 `/spec setup` to set up the environment."
- Do NOT proceed to Review Protocol.
---

4
packages/core/src/extensions/builtin/conductor/commands/conductor/setup.toml → packages/core/src/extensions/builtin/conductor/commands/spec/setup.toml
View File

@@ -41,7 +41,7 @@ PLAN MODE PROTOCOL: This setup process runs entirely within Plan Mode. While in
| Artifact Exists | Target Section | Announcement |
| :--- | :--- | :--- |
| All files in `tracks/<track_id>/` (`spec`, `plan`, `metadata`, `index`) | **HALT** | "The project is already initialized. Use `/conductor:newTrack` or `/conductor:implement`." |
| All files in `tracks/<track_id>/` (`spec`, `plan`, `metadata`, `index`) | **HALT** | "The project is already initialized. Use `/spec create` or `/spec implement`." |
| `index.md` (top-level) | **Section 3.0** | "Resuming setup: Scaffolding is complete. Next: generate the first track. (Note: If an incomplete track folder was detected, we will restart this step to ensure a clean, consistent state)." |
| `workflow.md` | **Section 2.6** | "Resuming setup: Workflow is defined. Next: generate project index." |
| `code_styleguides/` | **Section 2.5** | "Resuming setup: Guides/Tech Stack configured. Next: define project workflow." |
@@ -527,5 +527,5 @@ PLAN MODE PROTOCOL: This setup process runs entirely within Plan Mode. While in
### 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 `/spec implement`.
"""

2
packages/core/src/extensions/builtin/conductor/commands/conductor/status.toml → packages/core/src/extensions/builtin/conductor/commands/spec/status.toml
View File

@@ -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 `/spec setup` to set up the environment."
- Do NOT proceed to Status Overview Protocol.
---