mirror of
https://github.com/google-gemini/gemini-cli.git
synced 2026-03-18 10:01:29 -07:00
feat(cli): rename extension to sdd and add migration prompt
This commit is contained in:
Jerop Kipruto
@@ -367,15 +367,14 @@ The standard planner uses an adaptive workflow to analyze your project, consult
|
||||
you on trade-offs via [`ask_user`](../tools/ask-user.md), and draft a plan for
|
||||
your approval. It is ideal for quick exploration and ad-hoc tasks.
|
||||
|
||||
### Conductor
|
||||
### Spec-Driven Development (SDD)
|
||||
|
||||
[Conductor] is a built-in methodology for spec-driven development, designed for
|
||||
managing large features and complex tasks through persistent artifacts. It
|
||||
organizes work into tracks and stores them in your project's `conductor/`
|
||||
directory.
|
||||
[Spec-Driven Development (SDD)] is a built-in methodology for managing large
|
||||
features and complex tasks through persistent artifacts. It 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 `/spec setup`.
|
||||
SDD leverages Plan Mode internally to ensure architectural safety during the
|
||||
design phase. To get started with SDD, run `/spec setup`.
|
||||
|
||||
- **Automate transitions:** Switches to read-only mode via
|
||||
[`enter_plan_mode`](../tools/planning.md#1-enter_plan_mode-enterplanmode).
|
||||
@@ -388,7 +387,7 @@ the design phase. To get started with Conductor, run `/spec setup`.
|
||||
|
||||
### Comparison of planning workflows
|
||||
|
||||
| Feature | Standard | Conductor |
|
||||
| Feature | Standard | SDD |
|
||||
| :-------------- | :--------------------------------- | :------------------------------------------------ |
|
||||
| **Persistence** | Ephemeral, session-based | Persistent, stored in your repository |
|
||||
| **Workflow** | Lightweight research & design | Structured Spec -> Plan -> Implement lifecycle |
|
||||
@@ -413,8 +412,8 @@ To build a custom planning workflow, you can use:
|
||||
[custom plan directories](#custom-plan-directory-and-policies) and
|
||||
[custom policies](#custom-policies).
|
||||
|
||||
> **Note:** Use [Conductor] as a reference when building your own custom
|
||||
> planning workflow.
|
||||
> **Note:** Use [Spec-Driven Development (SDD)] as a reference when building
|
||||
> your own custom planning workflow.
|
||||
|
||||
By using Plan Mode as its execution environment, your custom methodology can
|
||||
enforce read-only safety during the design phase while benefiting from
|
||||
@@ -468,5 +467,5 @@ those files are not automatically deleted and must be managed manually.
|
||||
|
||||
[`plan.toml`]:
|
||||
https://github.com/google-gemini/gemini-cli/blob/main/packages/core/src/policy/policies/plan.toml
|
||||
[Conductor]: ./conductor.md
|
||||
[Spec-Driven Development (SDD)]: ./spec-driven-development.md
|
||||
[open an issue]: https://github.com/google-gemini/gemini-cli/issues
|
||||
|
||||
@@ -1,19 +1,19 @@
|
||||
# Conductor
|
||||
# Spec-Driven Development (SDD)
|
||||
|
||||
**Measure twice, code once.**
|
||||
|
||||
Conductor is a built-in methodology for Gemini CLI that enables **Context-Driven
|
||||
Development**. It turns the Gemini CLI into a proactive project manager that
|
||||
follows a strict protocol to specify, plan, and implement software features and
|
||||
bug fixes.
|
||||
Spec-Driven Development (SDD) is a built-in methodology for Gemini CLI that
|
||||
enables **Context-Driven Development**. Inspired by [Conductor], it turns Gemini
|
||||
CLI into a proactive project manager that follows a strict protocol to specify,
|
||||
plan, and implement software features and bug fixes.
|
||||
|
||||
Instead of just writing code, Conductor ensures a consistent, high-quality
|
||||
lifecycle for every task: **Context -> Spec & Plan -> Implement**.
|
||||
Instead of just writing code, SDD ensures a consistent, high-quality lifecycle
|
||||
for every task: **Context -> Spec & Plan -> Implement**.
|
||||
|
||||
The philosophy behind Conductor is simple: control your code. By treating
|
||||
context as a managed artifact alongside your code, you transform your repository
|
||||
into a single source of truth that drives every agent interaction with deep,
|
||||
persistent project awareness.
|
||||
The philosophy behind SDD is simple: control your code. By treating context as a
|
||||
managed artifact alongside your code, you transform your repository into a
|
||||
single source of truth that drives every agent interaction with deep, persistent
|
||||
project awareness.
|
||||
|
||||
## Features
|
||||
|
||||
@@ -32,20 +32,20 @@ persistent project awareness.
|
||||
|
||||
## Usage
|
||||
|
||||
Conductor is designed to manage the entire lifecycle of your development tasks.
|
||||
It is one of the [planning workflows](./plan-mode.md#planning-workflows)
|
||||
supported by Gemini CLI.
|
||||
SDD is designed to manage the entire lifecycle of your development tasks. It is
|
||||
one of the [planning workflows](./plan-mode.md#planning-workflows) supported by
|
||||
Gemini CLI.
|
||||
|
||||
**Note on Token Consumption:** Conductor's context-driven approach involves
|
||||
reading and analyzing your project's context, specifications, and plans. This
|
||||
can lead to increased token consumption, especially in larger projects or during
|
||||
**Note on Token Consumption:** SDD's context-driven approach involves reading
|
||||
and analyzing your project's context, specifications, and plans. This can lead
|
||||
to increased token consumption, especially in larger projects or during
|
||||
extensive planning and implementation phases. You can check the token
|
||||
consumption in the current session by running `/stats model`.
|
||||
|
||||
### 1. Set Up the Project (Run Once)
|
||||
|
||||
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
|
||||
When you run `/spec setup`, SDD 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
|
||||
@@ -72,8 +72,8 @@ features by you or anyone on your team.
|
||||
### 2. Start a New Track (Feature or Bug)
|
||||
|
||||
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:
|
||||
initializes a **track** — a high-level unit of work. SDD helps you generate two
|
||||
critical artifacts:
|
||||
|
||||
- **Specs**: The detailed requirements for the specific job. What are we
|
||||
building and why?
|
||||
@@ -106,7 +106,7 @@ through the `plan.md` file, checking off tasks as it completes them.
|
||||
/spec implement
|
||||
```
|
||||
|
||||
Conductor will:
|
||||
SDD will:
|
||||
|
||||
1. Select the next pending task.
|
||||
2. Follow the defined workflow (e.g., TDD: Write Test -> Fail -> Implement ->
|
||||
@@ -134,11 +134,14 @@ During implementation, you can also:
|
||||
|
||||
## Commands Reference
|
||||
|
||||
| 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` |
|
||||
| Command | Description | Artifacts |
|
||||
| :---------------- | :-------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `/spec setup` | Scaffolds the project and sets up the SDD 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` |
|
||||
|
||||
[Conductor]:
|
||||
https://developers.googleblog.com/conductor-introducing-context-driven-development-for-gemini-cli/
|
||||
Reference in New Issue
Block a user