mirror of
https://github.com/google-gemini/gemini-cli.git
synced 2026-03-18 01:51:20 -07:00
feat(cli): rename conductor commands to /spec
This commit is contained in:
Jerop Kipruto
@@ -44,9 +44,9 @@ consumption in the current session by running `/stats model`.
|
||||
|
||||
### 1. Set Up the Project (Run Once)
|
||||
|
||||
When you run `/conductor:setup`, Conductor helps you define the core components
|
||||
of your project context. This context is then used for building new components
|
||||
or features by you or anyone on your team.
|
||||
When you run `/spec setup`, Conductor helps you define the core components of
|
||||
your project context. This context is then used for building new components or
|
||||
features by you or anyone on your team.
|
||||
|
||||
- **Product**: Define project context (e.g. users, product goals, high-level
|
||||
features).
|
||||
@@ -66,14 +66,14 @@ or features by you or anyone on your team.
|
||||
- `conductor/tracks.md`
|
||||
|
||||
```bash
|
||||
/conductor:setup
|
||||
/spec setup
|
||||
```
|
||||
|
||||
### 2. Start a New Track (Feature or Bug)
|
||||
|
||||
When you’re ready to take on a new feature or bug fix, run
|
||||
`/conductor:newTrack`. This initializes a **track** — a high-level unit of work.
|
||||
Conductor helps you generate two critical artifacts:
|
||||
When you’re ready to take on a new feature or bug fix, run `/spec create`. This
|
||||
initializes a **track** — a high-level unit of work. Conductor helps you
|
||||
generate two critical artifacts:
|
||||
|
||||
- **Specs**: The detailed requirements for the specific job. What are we
|
||||
building and why?
|
||||
@@ -86,15 +86,15 @@ Conductor helps you generate two critical artifacts:
|
||||
- `conductor/tracks/<track_id>/metadata.json`
|
||||
|
||||
```bash
|
||||
/conductor:newTrack
|
||||
/spec create
|
||||
# OR with a description
|
||||
/conductor:newTrack "Add a dark mode toggle to the settings page"
|
||||
/spec create "Add a dark mode toggle to the settings page"
|
||||
```
|
||||
|
||||
### 3. Implement the Track
|
||||
|
||||
Once you approve the plan, run `/conductor:implement`. Your coding agent then
|
||||
works through the `plan.md` file, checking off tasks as it completes them.
|
||||
Once you approve the plan, run `/spec implement`. Your coding agent then works
|
||||
through the `plan.md` file, checking off tasks as it completes them.
|
||||
|
||||
**Updated Artifacts:**
|
||||
|
||||
@@ -103,7 +103,7 @@ works through the `plan.md` file, checking off tasks as it completes them.
|
||||
- Project context files (Synchronized on completion)
|
||||
|
||||
```bash
|
||||
/conductor:implement
|
||||
/spec implement
|
||||
```
|
||||
|
||||
Conductor will:
|
||||
@@ -119,26 +119,26 @@ During implementation, you can also:
|
||||
|
||||
- **Check status**: Get a high-level overview of your project's progress.
|
||||
```bash
|
||||
/conductor:status
|
||||
/spec status
|
||||
```
|
||||
- **Revert work**: Undo a feature or a specific task if needed.
|
||||
|
||||
```bash
|
||||
/conductor:revert
|
||||
/spec revert
|
||||
```
|
||||
|
||||
- **Review work**: Review completed work against guidelines and the plan.
|
||||
```bash
|
||||
/conductor:review
|
||||
/spec review
|
||||
```
|
||||
|
||||
## Commands Reference
|
||||
|
||||
| Command | Description | Artifacts |
|
||||
| :--------------------- | :-------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `/conductor:setup` | Scaffolds the project and sets up the Conductor environment. Run this once per project. | `conductor/product.md`<br>`conductor/product-guidelines.md`<br>`conductor/tech-stack.md`<br>`conductor/workflow.md`<br>`conductor/tracks.md` |
|
||||
| `/conductor:newTrack` | Starts a new feature or bug track. Generates `spec.md` and `plan.md`. | `conductor/tracks/<id>/spec.md`<br>`conductor/tracks/<id>/plan.md`<br>`conductor/tracks.md` |
|
||||
| `/conductor:implement` | Executes the tasks defined in the current track's plan. | `conductor/tracks.md`<br>`conductor/tracks/<id>/plan.md` |
|
||||
| `/conductor:status` | Displays the current progress of the tracks file and active tracks. | Reads `conductor/tracks.md` |
|
||||
| `/conductor:revert` | Reverts a track, phase, or task by analyzing git history. | Reverts git history |
|
||||
| `/conductor:review` | Reviews completed work against guidelines and the plan. | Reads `plan.md`, `product-guidelines.md` |
|
||||
| Command | Description | Artifacts |
|
||||
| :---------------- | :-------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `/spec setup` | Scaffolds the project and sets up the Conductor environment. Run this once per project. | `conductor/product.md`<br>`conductor/product-guidelines.md`<br>`conductor/tech-stack.md`<br>`conductor/workflow.md`<br>`conductor/tracks.md` |
|
||||
| `/spec create` | Starts a new feature or bug track. Generates `spec.md` and `plan.md`. | `conductor/tracks/<id>/spec.md`<br>`conductor/tracks/<id>/plan.md`<br>`conductor/tracks.md` |
|
||||
| `/spec implement` | Executes the tasks defined in the current track's plan. | `conductor/tracks.md`<br>`conductor/tracks/<id>/plan.md` |
|
||||
| `/spec status` | Displays the current progress of the tracks file and active tracks. | Reads `conductor/tracks.md` |
|
||||
| `/spec revert` | Reverts a track, phase, or task by analyzing git history. | Reverts git history |
|
||||
| `/spec review` | Reviews completed work against guidelines and the plan. | Reads `plan.md`, `product-guidelines.md` |
|
||||
|
||||
@@ -375,7 +375,7 @@ organizes work into tracks and stores them in your project's `conductor/`
|
||||
directory.
|
||||
|
||||
Conductor leverages Plan Mode internally to ensure architectural safety during
|
||||
the design phase. To get started with Conductor, run `/conductor:setup`.
|
||||
the design phase. To get started with Conductor, run `/spec setup`.
|
||||
|
||||
- **Automate transitions:** Switches to read-only mode via
|
||||
[`enter_plan_mode`](../tools/planning.md#1-enter_plan_mode-enterplanmode).
|
||||
|
||||
@@ -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`."
|
||||
|
||||
"""
|
||||
@@ -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>`.
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
---
|
||||
@@ -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`.
|
||||
"""
|
||||
@@ -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.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user