From 5c8302ad33ee102aedd292f2e5f966023c036501 Mon Sep 17 00:00:00 2001 From: Jerop Kipruto Date: Tue, 17 Mar 2026 12:47:28 -0400 Subject: [PATCH] feat(cli): rename extension to sdd and add migration prompt --- README.md | 9 +-- docs/cli/plan-mode.md | 21 +++---- ...onductor.md => spec-driven-development.md} | 63 ++++++++++--------- packages/cli/src/config/extension-manager.ts | 11 ++++ .../commands/spec/create.toml | 8 +-- .../commands/spec/implement.toml | 6 +- .../commands/spec/revert.toml | 6 +- .../commands/spec/review.toml | 4 +- .../commands/spec/setup.toml | 18 +++--- .../commands/spec/status.toml | 4 +- .../{conductor => sdd}/gemini-extension.json | 2 +- .../policies/conductor.toml | 4 +- .../templates/code_styleguides/cpp.md | 0 .../templates/code_styleguides/csharp.md | 0 .../templates/code_styleguides/dart.md | 0 .../templates/code_styleguides/general.md | 0 .../templates/code_styleguides/go.md | 0 .../templates/code_styleguides/html-css.md | 0 .../templates/code_styleguides/javascript.md | 0 .../templates/code_styleguides/python.md | 0 .../templates/code_styleguides/typescript.md | 0 .../{conductor => sdd}/templates/workflow.md | 0 22 files changed, 85 insertions(+), 71 deletions(-) rename docs/cli/{conductor.md => spec-driven-development.md} (56%) rename packages/core/src/extensions/builtin/{conductor => sdd}/commands/spec/create.toml (95%) rename packages/core/src/extensions/builtin/{conductor => sdd}/commands/spec/implement.toml (97%) rename packages/core/src/extensions/builtin/{conductor => sdd}/commands/spec/revert.toml (94%) rename packages/core/src/extensions/builtin/{conductor => sdd}/commands/spec/review.toml (98%) rename packages/core/src/extensions/builtin/{conductor => sdd}/commands/spec/setup.toml (97%) rename packages/core/src/extensions/builtin/{conductor => sdd}/commands/spec/status.toml (94%) rename packages/core/src/extensions/builtin/{conductor => sdd}/gemini-extension.json (78%) rename packages/core/src/extensions/builtin/{conductor => sdd}/policies/conductor.toml (81%) rename packages/core/src/extensions/builtin/{conductor => sdd}/templates/code_styleguides/cpp.md (100%) rename packages/core/src/extensions/builtin/{conductor => sdd}/templates/code_styleguides/csharp.md (100%) rename packages/core/src/extensions/builtin/{conductor => sdd}/templates/code_styleguides/dart.md (100%) rename packages/core/src/extensions/builtin/{conductor => sdd}/templates/code_styleguides/general.md (100%) rename packages/core/src/extensions/builtin/{conductor => sdd}/templates/code_styleguides/go.md (100%) rename packages/core/src/extensions/builtin/{conductor => sdd}/templates/code_styleguides/html-css.md (100%) rename packages/core/src/extensions/builtin/{conductor => sdd}/templates/code_styleguides/javascript.md (100%) rename packages/core/src/extensions/builtin/{conductor => sdd}/templates/code_styleguides/python.md (100%) rename packages/core/src/extensions/builtin/{conductor => sdd}/templates/code_styleguides/typescript.md (100%) rename packages/core/src/extensions/builtin/{conductor => sdd}/templates/workflow.md (100%) diff --git a/README.md b/README.md index 2b1b894d51..b772433d6c 100644 --- a/README.md +++ b/README.md @@ -22,9 +22,9 @@ Learn all about Gemini CLI in our [documentation](https://geminicli.com/docs/). context window. - **πŸ”§ Built-in tools**: Google Search grounding, file operations, shell commands, web fetching. -- **πŸ“‹ Context-Driven Development**: Built-in [Conductor] extension for - spec-driven project management. -- **πŸ”Œ Extensible**: MCP (Model Context Protocol) support for custom +- **πŸ“‹ [Spec-Driven Development (SDD)]**: Built-in extension for spec-driven + project management (inspired by [Conductor]). +- **Plug-and-play**: MCP (Model Context Protocol) support for custom integrations. - **πŸ’» Terminal-first**: Designed for developers who live in the command line. - **πŸ›‘οΈ Open source**: Apache 2.0 licensed. @@ -390,7 +390,8 @@ instructions. --- -[Conductor]: ./docs/cli/conductor.md +[Spec-Driven Development (SDD)]: ./docs/cli/spec-driven-development.md +[Conductor]: https://github.com/gemini-cli-extensions/conductor

Built with ❀️ by Google and the open source community diff --git a/docs/cli/plan-mode.md b/docs/cli/plan-mode.md index 98ae29eae8..f343c24c78 100644 --- a/docs/cli/plan-mode.md +++ b/docs/cli/plan-mode.md @@ -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 diff --git a/docs/cli/conductor.md b/docs/cli/spec-driven-development.md similarity index 56% rename from docs/cli/conductor.md rename to docs/cli/spec-driven-development.md index fcfb7f19e5..2aedf14002 100644 --- a/docs/cli/conductor.md +++ b/docs/cli/spec-driven-development.md @@ -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`
`conductor/product-guidelines.md`
`conductor/tech-stack.md`
`conductor/workflow.md`
`conductor/tracks.md` | -| `/spec create` | Starts a new feature or bug track. Generates `spec.md` and `plan.md`. | `conductor/tracks//spec.md`
`conductor/tracks//plan.md`
`conductor/tracks.md` | -| `/spec implement` | Executes the tasks defined in the current track's plan. | `conductor/tracks.md`
`conductor/tracks//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`
`conductor/product-guidelines.md`
`conductor/tech-stack.md`
`conductor/workflow.md`
`conductor/tracks.md` | +| `/spec create` | Starts a new feature or bug track. Generates `spec.md` and `plan.md`. | `conductor/tracks//spec.md`
`conductor/tracks//plan.md`
`conductor/tracks.md` | +| `/spec implement` | Executes the tasks defined in the current track's plan. | `conductor/tracks.md`
`conductor/tracks//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/ diff --git a/packages/cli/src/config/extension-manager.ts b/packages/cli/src/config/extension-manager.ts index ef179f8b9e..848db586a4 100644 --- a/packages/cli/src/config/extension-manager.ts +++ b/packages/cli/src/config/extension-manager.ts @@ -693,6 +693,17 @@ Would you like to attempt to install via "git clone" instead?`, } builtExtensions[existingIdx] = builtinExt; } else { + // Check if this is the new 'sdd' extension and if 'conductor' is installed. + if (builtinExt.name === 'sdd') { + const conductorIdx = builtExtensions.findIndex( + (e) => e.name === 'conductor', + ); + if (conductorIdx !== -1) { + const message = `The "conductor" extension has been renamed to "sdd" and is now built-in. Please run "gemini extensions uninstall conductor" to migrate. Your project files in "conductor/" will be preserved.`; + debugLogger.warn(message); + coreEvents.emitFeedback('warning', message); + } + } builtExtensions.push(builtinExt); } } diff --git a/packages/core/src/extensions/builtin/conductor/commands/spec/create.toml b/packages/core/src/extensions/builtin/sdd/commands/spec/create.toml similarity index 95% rename from packages/core/src/extensions/builtin/conductor/commands/spec/create.toml rename to packages/core/src/extensions/builtin/sdd/commands/spec/create.toml index 4975321d00..5296f3e62e 100644 --- a/packages/core/src/extensions/builtin/conductor/commands/spec/create.toml +++ b/packages/core/src/extensions/builtin/sdd/commands/spec/create.toml @@ -1,7 +1,7 @@ description = "Plans a track, generates track-specific spec documents and updates the tracks file" prompt = """ ## 1.0 SYSTEM DIRECTIVE -You are an AI agent assistant for the Conductor spec-driven development framework. Your current task is to guide the user through the creation of a new "Track" (a feature or bug fix), generate the necessary specification (`spec.md`) and plan (`plan.md`) files, and organize them within a dedicated track directory. +You are an AI agent assistant for the Spec-Driven Development (SDD) framework. Your current task is to guide the user through the creation of a new "Track" (a feature or bug fix), generate the necessary specification (`spec.md`) and plan (`plan.md`) files, and organize them within a dedicated track directory. 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. @@ -10,7 +10,7 @@ PLAN MODE PROTOCOL: Parts of this process run within Plan Mode. While in Plan Mo --- ## 1.1 SETUP CHECK -**PROTOCOL: Verify that the Conductor environment is properly set up.** +**PROTOCOL: Verify that the SDD environment is properly set up.** 1. **Verify Core Context:** Using the **Universal File Resolution Protocol**, resolve and verify the existence of: - **Product Definition** @@ -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 `/spec setup` to set up the environment." + - Announce: "SDD is not set up. Please run `/spec setup` to set up the environment." - Do NOT proceed to New Track Initialization. --- @@ -115,7 +115,7 @@ PLAN MODE PROTOCOL: Parts of this process run within Plan Mode. While in Plan Mo * Include status markers `[ ]` for **EVERY** task and sub-task. The format must be: - Parent Task: `- [ ] Task: ...` - Sub-task: ` - [ ] ...` - * **CRITICAL: Inject Phase Completion Tasks.** Determine if a "Phase Completion Verification and Checkpointing Protocol" is defined in the **Workflow**. If this protocol exists, then for each **Phase** that you generate in `plan.md`, you MUST append a final meta-task to that phase. The format for this meta-task is: `- [ ] Task: Conductor - User Manual Verification '' (Protocol in workflow.md)`. + * **CRITICAL: Inject Phase Completion Tasks.** Determine if a "Phase Completion Verification and Checkpointing Protocol" is defined in the **Workflow**. If this protocol exists, then for each **Phase** that you generate in `plan.md`, you MUST append a final meta-task to that phase. The format for this meta-task is: `- [ ] Task: SDD - User Manual Verification '' (Protocol in workflow.md)`. 3. **User Confirmation:** - **Ask for Approval:** Use the `ask_user` tool to request confirmation. You MUST embed the drafted content directly into the `question` field so the user can review it in context. diff --git a/packages/core/src/extensions/builtin/conductor/commands/spec/implement.toml b/packages/core/src/extensions/builtin/sdd/commands/spec/implement.toml similarity index 97% rename from packages/core/src/extensions/builtin/conductor/commands/spec/implement.toml rename to packages/core/src/extensions/builtin/sdd/commands/spec/implement.toml index 938357ef6b..5fc5ccbe03 100644 --- a/packages/core/src/extensions/builtin/conductor/commands/spec/implement.toml +++ b/packages/core/src/extensions/builtin/sdd/commands/spec/implement.toml @@ -1,21 +1,21 @@ 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. +You are an AI agent assistant for the Spec-Driven Development (SDD) 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.** +**PROTOCOL: Verify that the SDD 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 `/spec setup`." and HALT. +2. **Handle Failure:** If ANY of these are missing (or their resolved paths do not exist), Announce: "SDD is not set up. Please run `/spec setup`." and HALT. --- diff --git a/packages/core/src/extensions/builtin/conductor/commands/spec/revert.toml b/packages/core/src/extensions/builtin/sdd/commands/spec/revert.toml similarity index 94% rename from packages/core/src/extensions/builtin/conductor/commands/spec/revert.toml rename to packages/core/src/extensions/builtin/sdd/commands/spec/revert.toml index c4b2a6bc0e..0b13a27003 100644 --- a/packages/core/src/extensions/builtin/conductor/commands/spec/revert.toml +++ b/packages/core/src/extensions/builtin/sdd/commands/spec/revert.toml @@ -1,9 +1,9 @@ description = "Reverts previous work" prompt = """ ## 1.0 SYSTEM DIRECTIVE -You are an AI agent for the Conductor framework. Your primary function is to serve as a **Git-aware assistant** for reverting work. +You are an AI agent for the Spec-Driven Development (SDD) framework. Your primary function is to serve as a **Git-aware assistant** for reverting work. -**Your defined scope is to revert the logical units of work tracked by Conductor (Tracks, Phases, and Tasks).** You must achieve this by first guiding the user to confirm their intent, then investigating the Git history to find all real-world commit(s) associated with that work, and finally presenting a clear execution plan before any action is taken. +**Your defined scope is to revert the logical units of work tracked by SDD (Tracks, Phases, and Tasks).** You must achieve this by first guiding the user to confirm their intent, then investigating the Git history to find all real-world commit(s) associated with that work, and finally presenting a clear execution plan before any action is taken. Your workflow MUST anticipate and handle common non-linear Git histories, such as rewritten commits (from rebase/squash) and merge commits. @@ -14,7 +14,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai --- ## 1.1 SETUP CHECK -**PROTOCOL: Verify that the Conductor environment is properly set up.** +**PROTOCOL: Verify that the SDD environment is properly set up.** 1. **Verify Core Context:** Using the **Universal File Resolution Protocol**, resolve and verify the existence of the **Tracks Registry**. diff --git a/packages/core/src/extensions/builtin/conductor/commands/spec/review.toml b/packages/core/src/extensions/builtin/sdd/commands/spec/review.toml similarity index 98% rename from packages/core/src/extensions/builtin/conductor/commands/spec/review.toml rename to packages/core/src/extensions/builtin/sdd/commands/spec/review.toml index 86cd60cbed..3cdeb303a2 100644 --- a/packages/core/src/extensions/builtin/conductor/commands/spec/review.toml +++ b/packages/core/src/extensions/builtin/sdd/commands/spec/review.toml @@ -15,7 +15,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai --- ## 1.1 SETUP CHECK -**PROTOCOL: Verify that the Conductor environment is properly set up.** +**PROTOCOL: Verify that the SDD environment is properly set up.** 1. **Verify Core Context:** Using the **Universal File Resolution Protocol**, resolve and verify the existence of: - **Tracks Registry** @@ -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 `/spec setup` to set up the environment." + - Announce: "SDD is not set up. Please run `/spec setup` to set up the environment." - Do NOT proceed to Review Protocol. --- diff --git a/packages/core/src/extensions/builtin/conductor/commands/spec/setup.toml b/packages/core/src/extensions/builtin/sdd/commands/spec/setup.toml similarity index 97% rename from packages/core/src/extensions/builtin/conductor/commands/spec/setup.toml rename to packages/core/src/extensions/builtin/sdd/commands/spec/setup.toml index 0c7f7b5300..bce358d6e2 100644 --- a/packages/core/src/extensions/builtin/conductor/commands/spec/setup.toml +++ b/packages/core/src/extensions/builtin/sdd/commands/spec/setup.toml @@ -1,7 +1,7 @@ -description = "Scaffolds the project and sets up the Conductor environment" +description = "Scaffolds the project and sets up the SDD environment" prompt = """ ## 1.0 SYSTEM DIRECTIVE -You are an AI agent. Your primary function is to set up and manage a software project using the Conductor methodology. This document is your operational protocol. Adhere to these instructions precisely and sequentially. Do not make assumptions. +You are an AI agent. Your primary function is to set up and manage a software project using the Spec-Driven Development (SDD) methodology. This document is your operational protocol. Adhere to these instructions precisely and sequentially. Do not make assumptions. CRITICAL: You must validate the success of every tool call. If a tool call fails (e.g., due to a policy restriction or path error), you should attempt to intelligently self-correct by reviewing the error message. If the failure is unrecoverable after a self-correction attempt, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions. @@ -11,7 +11,7 @@ PLAN MODE PROTOCOL: This setup process runs entirely within Plan Mode. While in ## 1.1 PRE-INITIALIZATION OVERVIEW 1. **Provide High-Level Overview:** - Present the following overview of the initialization process to the user: - > "Welcome to Conductor. I will guide you through the following steps to set up your project: + > "Welcome to Spec-Driven Development (SDD). I will guide you through the following steps to set up your project: > 1. **Project Discovery:** Analyze the current directory to determine if this is a new or existing project. > 2. **Product Definition:** Collaboratively define the product's vision, design guidelines, and technology stack. > 3. **Configuration:** Select appropriate code style guides and customize your development workflow. @@ -24,9 +24,9 @@ PLAN MODE PROTOCOL: This setup process runs entirely within Plan Mode. While in ## 1.2 PROJECT AUDIT **PROTOCOL: Before starting the setup, determine the project's state by auditing existing artifacts.** -1. **Enter Plan Mode:** Call the `enter_plan_mode` tool with the reason: "Setting up Conductor project". +1. **Enter Plan Mode:** Call the `enter_plan_mode` tool with the reason: "Setting up SDD project". -2. **Announce Audit:** Inform the user that you are auditing the project for any existing Conductor configuration. +2. **Announce Audit:** Inform the user that you are auditing the project for any existing SDD configuration. 3. **Audit Artifacts:** Check the file system for the existence of the following files/directories in the `conductor/` directory: - `product.md` @@ -81,7 +81,7 @@ PLAN MODE PROTOCOL: This setup process runs entirely within Plan Mode. While in 3. **Execute Workflow based on Maturity:** - **If Brownfield:** - Announce that an existing project has been detected, and **briefly state the specific indicator you found** (e.g., "because I found a `package.json` file"). Be concise. - - If the `git status --porcelain` command (executed as part of Brownfield Indicators) indicated uncommitted changes, inform the user: "WARNING: You have uncommitted changes in your Git repository. Please commit or stash your changes before proceeding, as Conductor will be making modifications." + - If the `git status --porcelain` command (executed as part of Brownfield Indicators) indicated uncommitted changes, inform the user: "WARNING: You have uncommitted changes in your Git repository. Please commit or stash your changes before proceeding, as SDD will be making modifications." - **Begin Brownfield Project Initialization Protocol:** - **1.0 Pre-analysis Confirmation:** 1. **Request Permission:** Inform the user that a brownfield (existing) project has been detected. @@ -334,7 +334,7 @@ PLAN MODE PROTOCOL: This setup process runs entirely within Plan Mode. While in - **question:** "Do you want to use the default workflow or customize it? The default includes >80% test coverage and per-task commits." - **type:** "choice" - **options:** - - Label: "Default", Description: "Use the standard Conductor workflow." + - Label: "Default", Description: "Use the standard SDD workflow." - Label: "Customize", Description: "I want to adjust coverage requirements and commit frequency." 3. **Gather Information (Conditional):** @@ -493,7 +493,7 @@ PLAN MODE PROTOCOL: This setup process runs entirely within Plan Mode. While in - **CRITICAL:** Include status markers `[ ]` for **EVERY** task and sub-task. The format must be: - Parent Task: `- [ ] Task: ...` - Sub-task: ` - [ ] ...` - - **CRITICAL: Inject Phase Completion Tasks.** You MUST read the `conductor/workflow.md` file to determine if a "Phase Completion Verification and Checkpointing Protocol" is defined. If this protocol exists, then for each **Phase** that you generate in `plan.md`, you MUST append a final meta-task to that phase. The format for this meta-task is: `- [ ] Task: Conductor - User Manual Verification '' (Protocol in workflow.md)`. You MUST replace `` with the actual name of the phase. + - **CRITICAL: Inject Phase Completion Tasks.** You MUST read the `conductor/workflow.md` file to determine if a "Phase Completion Verification and Checkpointing Protocol" is defined. If this protocol exists, then for each **Phase** that you generate in `plan.md`, you MUST append a final meta-task to that phase. The format for this meta-task is: `- [ ] Task: SDD - User Manual Verification '' (Protocol in workflow.md)`. You MUST replace `` with the actual name of the phase. c. **Create Track Artifacts:** i. **Generate and Store Track ID:** Create a unique Track ID from the track description using format `shortname_YYYYMMDD` and store it. You MUST use this exact same ID for all subsequent steps for this track. ii. **Create Single Directory:** Resolve the **Tracks Directory** via the **Universal File Resolution Protocol** and create a single new directory: `//`. @@ -526,6 +526,6 @@ 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`. +2. **Save SDD 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 `/spec implement`. """ \ No newline at end of file diff --git a/packages/core/src/extensions/builtin/conductor/commands/spec/status.toml b/packages/core/src/extensions/builtin/sdd/commands/spec/status.toml similarity index 94% rename from packages/core/src/extensions/builtin/conductor/commands/spec/status.toml rename to packages/core/src/extensions/builtin/sdd/commands/spec/status.toml index a8ef3ed0c2..fbe4463284 100644 --- a/packages/core/src/extensions/builtin/conductor/commands/spec/status.toml +++ b/packages/core/src/extensions/builtin/sdd/commands/spec/status.toml @@ -9,7 +9,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai ## 1.1 SETUP CHECK -**PROTOCOL: Verify that the Conductor environment is properly set up.** +**PROTOCOL: Verify that the SDD environment is properly set up.** 1. **Verify Core Context:** Using the **Universal File Resolution Protocol**, resolve and verify the existence of: - **Tracks Registry** @@ -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 `/spec setup` to set up the environment." + - Announce: "SDD is not set up. Please run `/spec setup` to set up the environment." - Do NOT proceed to Status Overview Protocol. --- diff --git a/packages/core/src/extensions/builtin/conductor/gemini-extension.json b/packages/core/src/extensions/builtin/sdd/gemini-extension.json similarity index 78% rename from packages/core/src/extensions/builtin/conductor/gemini-extension.json rename to packages/core/src/extensions/builtin/sdd/gemini-extension.json index 06a9a708ee..5777096f63 100644 --- a/packages/core/src/extensions/builtin/conductor/gemini-extension.json +++ b/packages/core/src/extensions/builtin/sdd/gemini-extension.json @@ -1,5 +1,5 @@ { - "name": "conductor", + "name": "sdd", "contextFileName": "GEMINI.md", "plan": { "directory": "conductor" diff --git a/packages/core/src/extensions/builtin/conductor/policies/conductor.toml b/packages/core/src/extensions/builtin/sdd/policies/conductor.toml similarity index 81% rename from packages/core/src/extensions/builtin/conductor/policies/conductor.toml rename to packages/core/src/extensions/builtin/sdd/policies/conductor.toml index caab21abef..7d2c8b8717 100644 --- a/packages/core/src/extensions/builtin/conductor/policies/conductor.toml +++ b/packages/core/src/extensions/builtin/sdd/policies/conductor.toml @@ -1,4 +1,4 @@ -# Allow writing conductor files in plan mode +# Allow writing SDD files in plan mode [[rule]] toolName = ["write_file", "replace"] priority = 100 # prioritize over other extension policies @@ -6,7 +6,7 @@ decision = "ask_user" modes = ["plan"] argsPattern = '"(?:file_path|path)":"conductor/[^"]*"' -# Allow tools used by conductor to set up conductor dir +# Allow tools used by SDD to set up conductor dir [[rule]] toolName = "run_shell_command" commandPrefix = ["git status", "git diff", "ls", "mkdir", "cp", "git init", "git add", "git commit"] diff --git a/packages/core/src/extensions/builtin/conductor/templates/code_styleguides/cpp.md b/packages/core/src/extensions/builtin/sdd/templates/code_styleguides/cpp.md similarity index 100% rename from packages/core/src/extensions/builtin/conductor/templates/code_styleguides/cpp.md rename to packages/core/src/extensions/builtin/sdd/templates/code_styleguides/cpp.md diff --git a/packages/core/src/extensions/builtin/conductor/templates/code_styleguides/csharp.md b/packages/core/src/extensions/builtin/sdd/templates/code_styleguides/csharp.md similarity index 100% rename from packages/core/src/extensions/builtin/conductor/templates/code_styleguides/csharp.md rename to packages/core/src/extensions/builtin/sdd/templates/code_styleguides/csharp.md diff --git a/packages/core/src/extensions/builtin/conductor/templates/code_styleguides/dart.md b/packages/core/src/extensions/builtin/sdd/templates/code_styleguides/dart.md similarity index 100% rename from packages/core/src/extensions/builtin/conductor/templates/code_styleguides/dart.md rename to packages/core/src/extensions/builtin/sdd/templates/code_styleguides/dart.md diff --git a/packages/core/src/extensions/builtin/conductor/templates/code_styleguides/general.md b/packages/core/src/extensions/builtin/sdd/templates/code_styleguides/general.md similarity index 100% rename from packages/core/src/extensions/builtin/conductor/templates/code_styleguides/general.md rename to packages/core/src/extensions/builtin/sdd/templates/code_styleguides/general.md diff --git a/packages/core/src/extensions/builtin/conductor/templates/code_styleguides/go.md b/packages/core/src/extensions/builtin/sdd/templates/code_styleguides/go.md similarity index 100% rename from packages/core/src/extensions/builtin/conductor/templates/code_styleguides/go.md rename to packages/core/src/extensions/builtin/sdd/templates/code_styleguides/go.md diff --git a/packages/core/src/extensions/builtin/conductor/templates/code_styleguides/html-css.md b/packages/core/src/extensions/builtin/sdd/templates/code_styleguides/html-css.md similarity index 100% rename from packages/core/src/extensions/builtin/conductor/templates/code_styleguides/html-css.md rename to packages/core/src/extensions/builtin/sdd/templates/code_styleguides/html-css.md diff --git a/packages/core/src/extensions/builtin/conductor/templates/code_styleguides/javascript.md b/packages/core/src/extensions/builtin/sdd/templates/code_styleguides/javascript.md similarity index 100% rename from packages/core/src/extensions/builtin/conductor/templates/code_styleguides/javascript.md rename to packages/core/src/extensions/builtin/sdd/templates/code_styleguides/javascript.md diff --git a/packages/core/src/extensions/builtin/conductor/templates/code_styleguides/python.md b/packages/core/src/extensions/builtin/sdd/templates/code_styleguides/python.md similarity index 100% rename from packages/core/src/extensions/builtin/conductor/templates/code_styleguides/python.md rename to packages/core/src/extensions/builtin/sdd/templates/code_styleguides/python.md diff --git a/packages/core/src/extensions/builtin/conductor/templates/code_styleguides/typescript.md b/packages/core/src/extensions/builtin/sdd/templates/code_styleguides/typescript.md similarity index 100% rename from packages/core/src/extensions/builtin/conductor/templates/code_styleguides/typescript.md rename to packages/core/src/extensions/builtin/sdd/templates/code_styleguides/typescript.md diff --git a/packages/core/src/extensions/builtin/conductor/templates/workflow.md b/packages/core/src/extensions/builtin/sdd/templates/workflow.md similarity index 100% rename from packages/core/src/extensions/builtin/conductor/templates/workflow.md rename to packages/core/src/extensions/builtin/sdd/templates/workflow.md