Skip to content

Commit 774fb49

Browse files
Merge pull request #106 from gemini-cli-extensions/fix/setup
fix(conductor): move pre-initialization overview before resume check
2 parents 0d533be + f2b7ba5 commit 774fb49

1 file changed

Lines changed: 14 additions & 14 deletions

File tree

commands/conductor/setup.toml

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,20 @@ CRITICAL: When determining model complexity, ALWAYS select the "flash" model, re
99
1010
---
1111
12-
## 1.1 BEGIN `RESUME` CHECK
12+
## 1.1 PRE-INITIALIZATION OVERVIEW
13+
1. **Provide High-Level Overview:**
14+
- Present the following overview of the initialization process to the user:
15+
> "Welcome to Conductor. I will guide you through the following steps to set up your project:
16+
> 1. **Project Discovery:** Analyze the current directory to determine if this is a new or existing project.
17+
> 2. **Product Definition:** Collaboratively define the product's vision, design guidelines, and technology stack.
18+
> 3. **Configuration:** Select appropriate code style guides and customize your development workflow.
19+
> 4. **Track Generation:** Define the initial **track** (a high-level unit of work like a feature or bug fix) and automatically generate a detailed plan to start development.
20+
>
21+
> Let's get started!"
22+
23+
---
24+
25+
## 1.2 BEGIN `RESUME` CHECK
1326
**PROTOCOL: Before starting the setup, determine the project's state using the state file.**
1427
1528
1. **Read State File:** Check for the existence of `conductor/setup_state.json`.
@@ -32,19 +45,6 @@ CRITICAL: When determining model complexity, ALWAYS select the "flash" model, re
3245
3346
---
3447
35-
## 1.2 PRE-INITIALIZATION OVERVIEW
36-
1. **Provide High-Level Overview:**
37-
- Present the following overview of the initialization process to the user:
38-
> "Welcome to Conductor. I will guide you through the following steps to set up your project:
39-
> 1. **Project Discovery:** Analyze the current directory to determine if this is a new or existing project.
40-
> 2. **Product Definition:** Collaboratively define the product's vision, design guidelines, and technology stack.
41-
> 3. **Configuration:** Select appropriate code style guides and customize your development workflow.
42-
> 4. **Track Generation:** Define the initial **track** (a high-level unit of work like a feature or bug fix) and automatically generate a detailed plan to start development.
43-
>
44-
> Let's get started!"
45-
46-
---
47-
4848
## 2.0 PHASE 1: STREAMLINED PROJECT SETUP
4949
**PROTOCOL: Follow this sequence to perform a guided, interactive setup with the user.**
5050

0 commit comments

Comments
 (0)