mirror of
https://github.com/google-gemini/gemini-cli.git
synced 2026-04-01 08:51:11 -07:00
feat(cli): rename extension to sdd and add migration prompt
This commit is contained in:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user