geminize 1.0.0 → 1.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/.cursor/mcp.json +3 -0
- data/.cursor/rules/isolation_rules/Core/command-execution.mdc +235 -0
- data/.cursor/rules/isolation_rules/Core/complexity-decision-tree.mdc +187 -0
- data/.cursor/rules/isolation_rules/Core/creative-phase-enforcement.mdc +145 -0
- data/.cursor/rules/isolation_rules/Core/creative-phase-metrics.mdc +195 -0
- data/.cursor/rules/isolation_rules/Core/file-verification.mdc +198 -0
- data/.cursor/rules/isolation_rules/Core/platform-awareness.mdc +71 -0
- data/.cursor/rules/isolation_rules/Level3/planning-comprehensive.mdc +159 -0
- data/.cursor/rules/isolation_rules/Level3/task-tracking-intermediate.mdc +135 -0
- data/.cursor/rules/isolation_rules/Phases/CreativePhase/creative-phase-architecture.mdc +187 -0
- data/.cursor/rules/isolation_rules/main.mdc +123 -0
- data/.cursor/rules/isolation_rules/visual-maps/archive-mode-map.mdc +277 -0
- data/.cursor/rules/isolation_rules/visual-maps/creative-mode-map.mdc +224 -0
- data/.cursor/rules/isolation_rules/visual-maps/implement-mode-map.mdc +321 -0
- data/.cursor/rules/isolation_rules/visual-maps/plan-mode-map.mdc +269 -0
- data/.cursor/rules/isolation_rules/visual-maps/qa-mode-map.mdc +495 -0
- data/.cursor/rules/isolation_rules/visual-maps/reflect-mode-map.mdc +234 -0
- data/.cursor/rules/isolation_rules/visual-maps/van-mode-map.mdc +902 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-complexity-determination.mdc +60 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-file-verification.mdc +49 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-mode-map.mdc +49 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-platform-detection.mdc +50 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-checks/build-test.mdc +117 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-checks/config-check.mdc +103 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-checks/dependency-check.mdc +147 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-checks/environment-check.mdc +104 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-checks/file-verification.mdc +1 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-main.mdc +142 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-utils/common-fixes.mdc +92 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-utils/mode-transitions.mdc +101 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-utils/reports.mdc +149 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-utils/rule-calling-guide.mdc +66 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-utils/rule-calling-help.mdc +19 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-validation.md.old +363 -0
- data/.env.example +7 -0
- data/.memory_bank/activeContext.md +78 -0
- data/.memory_bank/progress.md +80 -0
- data/.memory_bank/projectbrief.md +29 -0
- data/.memory_bank/systemPatterns.md +90 -0
- data/.memory_bank/tasks.md +98 -0
- data/.memory_bank/techContext.md +73 -0
- data/.tool-versions +1 -0
- data/CHANGELOG.md +20 -0
- data/README.md +42 -5
- data/examples/models_api.rb +125 -0
- data/lib/geminize/configuration.rb +4 -4
- data/lib/geminize/model_info.rb +87 -8
- data/lib/geminize/models/model.rb +101 -109
- data/lib/geminize/models/model_list.rb +70 -28
- data/lib/geminize/request_builder.rb +29 -0
- data/lib/geminize/version.rb +1 -1
- data/lib/geminize.rb +71 -14
- metadata +45 -2
@@ -0,0 +1,321 @@
|
|
1
|
+
---
|
2
|
+
description: Visual process map for BUILD mode (Code Implementation)
|
3
|
+
globs: implementation-mode-map.mdc
|
4
|
+
alwaysApply: false
|
5
|
+
---
|
6
|
+
|
7
|
+
# BUILD MODE: CODE EXECUTION PROCESS MAP
|
8
|
+
|
9
|
+
> **TL;DR:** This visual map guides the BUILD mode process, focusing on efficient code implementation based on the planning and creative phases, with proper command execution and progress tracking.
|
10
|
+
|
11
|
+
## 🧭 BUILD MODE PROCESS FLOW
|
12
|
+
|
13
|
+
```mermaid
|
14
|
+
graph TD
|
15
|
+
Start["START BUILD MODE"] --> ReadDocs["Read Reference Documents<br>Core/command-execution.md"]
|
16
|
+
|
17
|
+
%% Initialization
|
18
|
+
ReadDocs --> CheckLevel{"Determine<br>Complexity Level<br>from tasks.md"}
|
19
|
+
|
20
|
+
%% Level 1 Implementation
|
21
|
+
CheckLevel -->|"Level 1<br>Quick Bug Fix"| L1Process["LEVEL 1 PROCESS<br>Level1/quick-bug-workflow.md"]
|
22
|
+
L1Process --> L1Review["Review Bug<br>Report"]
|
23
|
+
L1Review --> L1Examine["Examine<br>Relevant Code"]
|
24
|
+
L1Examine --> L1Fix["Implement<br>Targeted Fix"]
|
25
|
+
L1Fix --> L1Test["Test<br>Fix"]
|
26
|
+
L1Test --> L1Update["Update<br>tasks.md"]
|
27
|
+
|
28
|
+
%% Level 2 Implementation
|
29
|
+
CheckLevel -->|"Level 2<br>Simple Enhancement"| L2Process["LEVEL 2 PROCESS<br>Level2/enhancement-workflow.md"]
|
30
|
+
L2Process --> L2Review["Review Build<br>Plan"]
|
31
|
+
L2Review --> L2Examine["Examine Relevant<br>Code Areas"]
|
32
|
+
L2Examine --> L2Implement["Implement Changes<br>Sequentially"]
|
33
|
+
L2Implement --> L2Test["Test<br>Changes"]
|
34
|
+
L2Test --> L2Update["Update<br>tasks.md"]
|
35
|
+
|
36
|
+
%% Level 3-4 Implementation
|
37
|
+
CheckLevel -->|"Level 3-4<br>Feature/System"| L34Process["LEVEL 3-4 PROCESS<br>Level3/feature-workflow.md<br>Level4/system-workflow.md"]
|
38
|
+
L34Process --> L34Review["Review Plan &<br>Creative Decisions"]
|
39
|
+
L34Review --> L34Phase{"Creative Phase<br>Documents<br>Complete?"}
|
40
|
+
|
41
|
+
L34Phase -->|"No"| L34Error["ERROR:<br>Return to CREATIVE Mode"]
|
42
|
+
L34Phase -->|"Yes"| L34DirSetup["Create Directory<br>Structure"]
|
43
|
+
L34DirSetup --> L34VerifyDirs["VERIFY Directories<br>Created Successfully"]
|
44
|
+
L34VerifyDirs --> L34Implementation["Build<br>Phase"]
|
45
|
+
|
46
|
+
%% Implementation Phases
|
47
|
+
L34Implementation --> L34Phase1["Phase 1<br>Build"]
|
48
|
+
L34Phase1 --> L34VerifyFiles["VERIFY Files<br>Created Successfully"]
|
49
|
+
L34VerifyFiles --> L34Test1["Test<br>Phase 1"]
|
50
|
+
L34Test1 --> L34Document1["Document<br>Phase 1"]
|
51
|
+
L34Document1 --> L34Next1{"Next<br>Phase?"}
|
52
|
+
L34Next1 -->|"Yes"| L34Implementation
|
53
|
+
|
54
|
+
L34Next1 -->|"No"| L34Integration["Integration<br>Testing"]
|
55
|
+
L34Integration --> L34Document["Document<br>Integration Points"]
|
56
|
+
L34Document --> L34Update["Update<br>tasks.md"]
|
57
|
+
|
58
|
+
%% Command Execution
|
59
|
+
L1Fix & L2Implement & L34Phase1 --> CommandExec["COMMAND EXECUTION<br>Core/command-execution.md"]
|
60
|
+
CommandExec --> DocCommands["Document Commands<br>& Results"]
|
61
|
+
|
62
|
+
%% Completion & Transition
|
63
|
+
L1Update & L2Update & L34Update --> VerifyComplete["Verify Build<br>Complete"]
|
64
|
+
VerifyComplete --> UpdateProgress["Update progress.md<br>with Status"]
|
65
|
+
UpdateProgress --> Transition["NEXT MODE:<br>REFLECT MODE"]
|
66
|
+
```
|
67
|
+
|
68
|
+
## 📋 REQUIRED FILE STATE VERIFICATION
|
69
|
+
|
70
|
+
Before implementation can begin, verify file state:
|
71
|
+
|
72
|
+
```mermaid
|
73
|
+
graph TD
|
74
|
+
Start["File State<br>Verification"] --> CheckTasks{"tasks.md has<br>planning complete?"}
|
75
|
+
|
76
|
+
CheckTasks -->|"No"| ErrorPlan["ERROR:<br>Return to PLAN Mode"]
|
77
|
+
CheckTasks -->|"Yes"| CheckLevel{"Task<br>Complexity?"}
|
78
|
+
|
79
|
+
CheckLevel -->|"Level 1"| L1Ready["Ready for<br>Implementation"]
|
80
|
+
|
81
|
+
CheckLevel -->|"Level 2"| L2Ready["Ready for<br>Implementation"]
|
82
|
+
|
83
|
+
CheckLevel -->|"Level 3-4"| CheckCreative{"Creative phases<br>required?"}
|
84
|
+
|
85
|
+
CheckCreative -->|"No"| L34Ready["Ready for<br>Implementation"]
|
86
|
+
CheckCreative -->|"Yes"| VerifyCreative{"Creative phases<br>completed?"}
|
87
|
+
|
88
|
+
VerifyCreative -->|"No"| ErrorCreative["ERROR:<br>Return to CREATIVE Mode"]
|
89
|
+
VerifyCreative -->|"Yes"| L34Ready
|
90
|
+
```
|
91
|
+
|
92
|
+
## 🔄 FILE SYSTEM VERIFICATION PROCESS
|
93
|
+
|
94
|
+
```mermaid
|
95
|
+
graph TD
|
96
|
+
Start["Start File<br>Verification"] --> CheckDir["Check Directory<br>Structure"]
|
97
|
+
CheckDir --> DirResult{"Directories<br>Exist?"}
|
98
|
+
|
99
|
+
DirResult -->|"No"| ErrorDir["❌ ERROR:<br>Missing Directories"]
|
100
|
+
DirResult -->|"Yes"| CheckFiles["Check Each<br>Created File"]
|
101
|
+
|
102
|
+
ErrorDir --> FixDir["Fix Directory<br>Structure"]
|
103
|
+
FixDir --> CheckDir
|
104
|
+
|
105
|
+
CheckFiles --> FileResult{"All Files<br>Exist?"}
|
106
|
+
FileResult -->|"No"| ErrorFile["❌ ERROR:<br>Missing/Wrong Path Files"]
|
107
|
+
FileResult -->|"Yes"| Complete["✅ Verification<br>Complete"]
|
108
|
+
|
109
|
+
ErrorFile --> FixFile["Fix File Paths<br>or Recreate Files"]
|
110
|
+
FixFile --> CheckFiles
|
111
|
+
```
|
112
|
+
|
113
|
+
## 📋 DIRECTORY VERIFICATION STEPS
|
114
|
+
|
115
|
+
Before beginning any file creation:
|
116
|
+
|
117
|
+
```
|
118
|
+
✓ DIRECTORY VERIFICATION PROCEDURE
|
119
|
+
1. Create all directories first before any files
|
120
|
+
2. Use ABSOLUTE paths: /full/path/to/directory
|
121
|
+
3. Verify each directory after creation:
|
122
|
+
ls -la /full/path/to/directory # Linux/Mac
|
123
|
+
dir "C:\full\path\to\directory" # Windows
|
124
|
+
4. Document directory structure in progress.md
|
125
|
+
5. Only proceed to file creation AFTER verifying ALL directories exist
|
126
|
+
```
|
127
|
+
|
128
|
+
## 📋 FILE CREATION VERIFICATION
|
129
|
+
|
130
|
+
After creating files:
|
131
|
+
|
132
|
+
```
|
133
|
+
✓ FILE VERIFICATION PROCEDURE
|
134
|
+
1. Use ABSOLUTE paths for all file operations: /full/path/to/file.ext
|
135
|
+
2. Verify each file creation was successful:
|
136
|
+
ls -la /full/path/to/file.ext # Linux/Mac
|
137
|
+
dir "C:\full\path\to\file.ext" # Windows
|
138
|
+
3. If verification fails:
|
139
|
+
a. Check for path resolution issues
|
140
|
+
b. Verify directory exists
|
141
|
+
c. Try creating with corrected path
|
142
|
+
d. Recheck file exists after correction
|
143
|
+
4. Document all file paths in progress.md
|
144
|
+
```
|
145
|
+
|
146
|
+
## 🔄 COMMAND EXECUTION WORKFLOW
|
147
|
+
|
148
|
+
```mermaid
|
149
|
+
graph TD
|
150
|
+
Start["Command<br>Execution"] --> Analyze["Analyze Command<br>Requirements"]
|
151
|
+
Analyze --> Complexity{"Command<br>Complexity?"}
|
152
|
+
|
153
|
+
Complexity -->|"Simple"| Simple["Execute<br>Single Command"]
|
154
|
+
Complexity -->|"Moderate"| Chain["Use Efficient<br>Command Chaining"]
|
155
|
+
Complexity -->|"Complex"| Break["Break Into<br>Logical Steps"]
|
156
|
+
|
157
|
+
Simple & Chain & Break --> Verify["Verify<br>Results"]
|
158
|
+
Verify --> Document["Document<br>Command & Result"]
|
159
|
+
Document --> Next["Next<br>Command"]
|
160
|
+
```
|
161
|
+
|
162
|
+
## 📋 LEVEL-SPECIFIC BUILD APPROACHES
|
163
|
+
|
164
|
+
```mermaid
|
165
|
+
graph TD
|
166
|
+
subgraph "Level 1: Quick Bug Fix"
|
167
|
+
L1A["Targeted Code<br>Examination"]
|
168
|
+
L1B["Minimal<br>Change Scope"]
|
169
|
+
L1C["Direct<br>Fix"]
|
170
|
+
L1D["Verify<br>Fix"]
|
171
|
+
end
|
172
|
+
|
173
|
+
subgraph "Level 2: Enhancement"
|
174
|
+
L2A["Sequential<br>Build"]
|
175
|
+
L2B["Contained<br>Changes"]
|
176
|
+
L2C["Standard<br>Testing"]
|
177
|
+
L2D["Component<br>Documentation"]
|
178
|
+
end
|
179
|
+
|
180
|
+
subgraph "Level 3-4: Feature/System"
|
181
|
+
L3A["Directory<br>Structure First"]
|
182
|
+
L3B["Verify Dirs<br>Before Files"]
|
183
|
+
L3C["Phased<br>Build"]
|
184
|
+
L3D["Verify Files<br>After Creation"]
|
185
|
+
L3E["Integration<br>Testing"]
|
186
|
+
L3F["Detailed<br>Documentation"]
|
187
|
+
end
|
188
|
+
|
189
|
+
L1A --> L1B --> L1C --> L1D
|
190
|
+
L2A --> L2B --> L2C --> L2D
|
191
|
+
L3A --> L3B --> L3C --> L3D --> L3E --> L3F
|
192
|
+
```
|
193
|
+
|
194
|
+
## 📝 BUILD DOCUMENTATION FORMAT
|
195
|
+
|
196
|
+
Document builds with:
|
197
|
+
|
198
|
+
```
|
199
|
+
## Build: [Component/Feature]
|
200
|
+
|
201
|
+
### Approach
|
202
|
+
[Brief description of build approach]
|
203
|
+
|
204
|
+
### Directory Structure
|
205
|
+
- [/absolute/path/to/dir1/]: [Purpose]
|
206
|
+
- [/absolute/path/to/dir2/]: [Purpose]
|
207
|
+
|
208
|
+
### Code Changes
|
209
|
+
- [/absolute/path/to/file1.ext]: [Description of changes]
|
210
|
+
- [/absolute/path/to/file2.ext]: [Description of changes]
|
211
|
+
|
212
|
+
### Verification Steps
|
213
|
+
- [✓] Directory structure created and verified
|
214
|
+
- [✓] All files created in correct locations
|
215
|
+
- [✓] File content verified
|
216
|
+
|
217
|
+
### Commands Executed
|
218
|
+
```
|
219
|
+
[Command 1]
|
220
|
+
[Result]
|
221
|
+
```
|
222
|
+
|
223
|
+
```
|
224
|
+
[Command 2]
|
225
|
+
[Result]
|
226
|
+
```
|
227
|
+
|
228
|
+
### Testing
|
229
|
+
- [Test 1]: [Result]
|
230
|
+
- [Test 2]: [Result]
|
231
|
+
|
232
|
+
### Status
|
233
|
+
- [x] Build complete
|
234
|
+
- [x] Testing performed
|
235
|
+
- [x] File verification completed
|
236
|
+
- [ ] Documentation updated
|
237
|
+
```
|
238
|
+
|
239
|
+
## 📊 TASKS.MD UPDATE FORMAT
|
240
|
+
|
241
|
+
During the build process, update tasks.md with progress:
|
242
|
+
|
243
|
+
```
|
244
|
+
## Status
|
245
|
+
- [x] Initialization complete
|
246
|
+
- [x] Planning complete
|
247
|
+
[For Level 3-4:]
|
248
|
+
- [x] Creative phases complete
|
249
|
+
- [x] Directory structure created and verified
|
250
|
+
- [x] [Built component 1]
|
251
|
+
- [x] [Built component 2]
|
252
|
+
- [ ] [Remaining component]
|
253
|
+
|
254
|
+
## Build Progress
|
255
|
+
- [Component 1]: Complete
|
256
|
+
- Files: [/absolute/path/to/files]
|
257
|
+
- [Details about implementation]
|
258
|
+
- [Component 2]: Complete
|
259
|
+
- Files: [/absolute/path/to/files]
|
260
|
+
- [Details about implementation]
|
261
|
+
- [Component 3]: In Progress
|
262
|
+
- [Current status]
|
263
|
+
```
|
264
|
+
|
265
|
+
## 📋 PROGRESS.MD UPDATE FORMAT
|
266
|
+
|
267
|
+
Update progress.md with:
|
268
|
+
|
269
|
+
```
|
270
|
+
# Build Progress
|
271
|
+
|
272
|
+
## Directory Structure
|
273
|
+
- [/absolute/path/to/dir1/]: Created and verified
|
274
|
+
- [/absolute/path/to/dir2/]: Created and verified
|
275
|
+
|
276
|
+
## [Date]: [Component/Feature] Built
|
277
|
+
- **Files Created**:
|
278
|
+
- [/absolute/path/to/file1.ext]: Verified
|
279
|
+
- [/absolute/path/to/file2.ext]: Verified
|
280
|
+
- **Key Changes**:
|
281
|
+
- [Change 1]
|
282
|
+
- [Change 2]
|
283
|
+
- **Testing**: [Test results]
|
284
|
+
- **Next Steps**: [What comes next]
|
285
|
+
```
|
286
|
+
|
287
|
+
## 📊 BUILD VERIFICATION CHECKLIST
|
288
|
+
|
289
|
+
```
|
290
|
+
✓ BUILD VERIFICATION
|
291
|
+
- Directory structure created correctly? [YES/NO]
|
292
|
+
- All files created in correct locations? [YES/NO]
|
293
|
+
- All file paths verified with absolute paths? [YES/NO]
|
294
|
+
- All planned changes implemented? [YES/NO]
|
295
|
+
- Testing performed for all changes? [YES/NO]
|
296
|
+
- Code follows project standards? [YES/NO]
|
297
|
+
- Edge cases handled appropriately? [YES/NO]
|
298
|
+
- Build documented with absolute paths? [YES/NO]
|
299
|
+
- tasks.md updated with progress? [YES/NO]
|
300
|
+
- progress.md updated with details? [YES/NO]
|
301
|
+
|
302
|
+
→ If all YES: Build complete - ready for REFLECT mode
|
303
|
+
→ If any NO: Complete missing build elements
|
304
|
+
```
|
305
|
+
|
306
|
+
## 🔄 MODE TRANSITION NOTIFICATION
|
307
|
+
|
308
|
+
When the build is complete, notify user with:
|
309
|
+
|
310
|
+
```
|
311
|
+
## BUILD COMPLETE
|
312
|
+
|
313
|
+
✅ Directory structure verified
|
314
|
+
✅ All files created in correct locations
|
315
|
+
✅ All planned changes implemented
|
316
|
+
✅ Testing performed successfully
|
317
|
+
✅ tasks.md updated with status
|
318
|
+
✅ progress.md updated with details
|
319
|
+
|
320
|
+
→ NEXT RECOMMENDED MODE: REFLECT MODE
|
321
|
+
```
|
@@ -0,0 +1,269 @@
|
|
1
|
+
# PLAN MODE: TASK PLANNING PROCESS MAP
|
2
|
+
|
3
|
+
> **TL;DR:** This visual map guides the PLAN mode process, focusing on creating detailed implementation plans based on the complexity level determined during initialization, with mandatory technology validation before implementation.
|
4
|
+
|
5
|
+
## 🧭 PLAN MODE PROCESS FLOW
|
6
|
+
|
7
|
+
```mermaid
|
8
|
+
graph TD
|
9
|
+
Start["START PLANNING"] --> ReadTasks["Read tasks.md<br>Core/task-tracking.md"]
|
10
|
+
|
11
|
+
%% Complexity Level Determination
|
12
|
+
ReadTasks --> CheckLevel{"Determine<br>Complexity Level"}
|
13
|
+
CheckLevel -->|"Level 2"| Level2["LEVEL 2 PLANNING<br>Level2/enhancement-planning.md"]
|
14
|
+
CheckLevel -->|"Level 3"| Level3["LEVEL 3 PLANNING<br>Level3/feature-planning.md"]
|
15
|
+
CheckLevel -->|"Level 4"| Level4["LEVEL 4 PLANNING<br>Level4/system-planning.md"]
|
16
|
+
|
17
|
+
%% Level 2 Planning
|
18
|
+
Level2 --> L2Review["Review Code<br>Structure"]
|
19
|
+
L2Review --> L2Document["Document<br>Planned Changes"]
|
20
|
+
L2Document --> L2Challenges["Identify<br>Challenges"]
|
21
|
+
L2Challenges --> L2Checklist["Create Task<br>Checklist"]
|
22
|
+
L2Checklist --> L2Update["Update tasks.md<br>with Plan"]
|
23
|
+
L2Update --> L2Tech["TECHNOLOGY<br>VALIDATION"]
|
24
|
+
L2Tech --> L2Verify["Verify Plan<br>Completeness"]
|
25
|
+
|
26
|
+
%% Level 3 Planning
|
27
|
+
Level3 --> L3Review["Review Codebase<br>Structure"]
|
28
|
+
L3Review --> L3Requirements["Document Detailed<br>Requirements"]
|
29
|
+
L3Requirements --> L3Components["Identify Affected<br>Components"]
|
30
|
+
L3Components --> L3Plan["Create Comprehensive<br>Implementation Plan"]
|
31
|
+
L3Plan --> L3Challenges["Document Challenges<br>& Solutions"]
|
32
|
+
L3Challenges --> L3Update["Update tasks.md<br>with Plan"]
|
33
|
+
L3Update --> L3Tech["TECHNOLOGY<br>VALIDATION"]
|
34
|
+
L3Tech --> L3Flag["Flag Components<br>Requiring Creative"]
|
35
|
+
L3Flag --> L3Verify["Verify Plan<br>Completeness"]
|
36
|
+
|
37
|
+
%% Level 4 Planning
|
38
|
+
Level4 --> L4Analysis["Codebase Structure<br>Analysis"]
|
39
|
+
L4Analysis --> L4Requirements["Document Comprehensive<br>Requirements"]
|
40
|
+
L4Requirements --> L4Diagrams["Create Architectural<br>Diagrams"]
|
41
|
+
L4Diagrams --> L4Subsystems["Identify Affected<br>Subsystems"]
|
42
|
+
L4Subsystems --> L4Dependencies["Document Dependencies<br>& Integration Points"]
|
43
|
+
L4Dependencies --> L4Plan["Create Phased<br>Implementation Plan"]
|
44
|
+
L4Plan --> L4Update["Update tasks.md<br>with Plan"]
|
45
|
+
L4Update --> L4Tech["TECHNOLOGY<br>VALIDATION"]
|
46
|
+
L4Tech --> L4Flag["Flag Components<br>Requiring Creative"]
|
47
|
+
L4Flag --> L4Verify["Verify Plan<br>Completeness"]
|
48
|
+
|
49
|
+
%% Technology Validation Gate - NEW
|
50
|
+
L2Tech & L3Tech & L4Tech --> TechGate["⛔ TECHNOLOGY<br>VALIDATION GATE"]
|
51
|
+
TechGate --> TechSelection["Document Technology<br>Stack Selection"]
|
52
|
+
TechSelection --> TechHelloWorld["Create Hello World<br>Proof of Concept"]
|
53
|
+
TechHelloWorld --> TechDependencies["Verify Required<br>Dependencies"]
|
54
|
+
TechDependencies --> TechConfig["Validate Build<br>Configuration"]
|
55
|
+
TechConfig --> TechBuild["Complete Test<br>Build"]
|
56
|
+
TechBuild --> TechVerify["⛔ TECHNOLOGY<br>CHECKPOINT"]
|
57
|
+
|
58
|
+
%% Verification & Completion
|
59
|
+
L2Verify & L3Verify & L4Verify & TechVerify --> CheckCreative{"Creative<br>Phases<br>Required?"}
|
60
|
+
|
61
|
+
%% Mode Transition
|
62
|
+
CheckCreative -->|"Yes"| RecCreative["NEXT MODE:<br>CREATIVE MODE"]
|
63
|
+
CheckCreative -->|"No"| RecImplement["NEXT MODE:<br>IMPLEMENT MODE"]
|
64
|
+
|
65
|
+
%% Style for Technology Gate
|
66
|
+
style TechGate fill:#ff5555,stroke:#dd3333,color:white,stroke-width:3px
|
67
|
+
style TechVerify fill:#ff5555,stroke:#dd3333,color:white,stroke-width:3px
|
68
|
+
style TechSelection fill:#4da6ff,stroke:#0066cc,color:white
|
69
|
+
style TechHelloWorld fill:#4da6ff,stroke:#0066cc,color:white
|
70
|
+
style TechDependencies fill:#4da6ff,stroke:#0066cc,color:white
|
71
|
+
style TechConfig fill:#4da6ff,stroke:#0066cc,color:white
|
72
|
+
style TechBuild fill:#4da6ff,stroke:#0066cc,color:white
|
73
|
+
```
|
74
|
+
|
75
|
+
## 📋 LEVEL-SPECIFIC PLANNING APPROACHES
|
76
|
+
|
77
|
+
```mermaid
|
78
|
+
graph TD
|
79
|
+
subgraph "Level 2: Enhancement"
|
80
|
+
L2A["Basic Requirements<br>Analysis"]
|
81
|
+
L2B["Simple Component<br>Identification"]
|
82
|
+
L2C["Linear Implementation<br>Plan"]
|
83
|
+
L2D["Basic Checklist<br>Creation"]
|
84
|
+
end
|
85
|
+
|
86
|
+
subgraph "Level 3: Feature"
|
87
|
+
L3A["Detailed Requirements<br>Analysis"]
|
88
|
+
L3B["Component Mapping<br>with Dependencies"]
|
89
|
+
L3C["Multi-Phase<br>Implementation Plan"]
|
90
|
+
L3D["Comprehensive<br>Checklist"]
|
91
|
+
L3E["Creative Phase<br>Identification"]
|
92
|
+
end
|
93
|
+
|
94
|
+
subgraph "Level 4: System"
|
95
|
+
L4A["Architectural<br>Requirements Analysis"]
|
96
|
+
L4B["System Component<br>Mapping"]
|
97
|
+
L4C["Subsystem<br>Integration Plan"]
|
98
|
+
L4D["Phased Implementation<br>Strategy"]
|
99
|
+
L4E["Risk Assessment<br>& Mitigation"]
|
100
|
+
L4F["Multiple Creative<br>Phase Requirements"]
|
101
|
+
end
|
102
|
+
|
103
|
+
L2A --> L2B --> L2C --> L2D
|
104
|
+
L3A --> L3B --> L3C --> L3D --> L3E
|
105
|
+
L4A --> L4B --> L4C --> L4D --> L4E --> L4F
|
106
|
+
```
|
107
|
+
|
108
|
+
## 🔧 TECHNOLOGY VALIDATION WORKFLOW
|
109
|
+
|
110
|
+
```mermaid
|
111
|
+
graph TD
|
112
|
+
Start["Technology<br>Validation Start"] --> Select["Technology<br>Stack Selection"]
|
113
|
+
Select --> Document["Document Chosen<br>Technologies"]
|
114
|
+
Document --> POC["Create Minimal<br>Proof of Concept"]
|
115
|
+
POC --> Build["Verify Build<br>Process Works"]
|
116
|
+
Build --> Dependencies["Validate All<br>Dependencies"]
|
117
|
+
Dependencies --> Config["Confirm Configuration<br>Files Are Correct"]
|
118
|
+
Config --> Test["Complete Test<br>Build/Run"]
|
119
|
+
Test --> Success{"All Checks<br>Pass?"}
|
120
|
+
|
121
|
+
Success -->|"Yes"| Ready["Ready for<br>Implementation"]
|
122
|
+
Success -->|"No"| Fix["Fix Technology<br>Issues"]
|
123
|
+
Fix --> Document
|
124
|
+
|
125
|
+
style Start fill:#4da6ff,stroke:#0066cc,color:white
|
126
|
+
style POC fill:#4da6ff,stroke:#0066cc,color:white
|
127
|
+
style Success fill:#ff5555,stroke:#dd3333,color:white
|
128
|
+
style Fix fill:#ff5555,stroke:#dd3333,color:white
|
129
|
+
style Ready fill:#10b981,stroke:#059669,color:white
|
130
|
+
```
|
131
|
+
|
132
|
+
## 📊 REQUIRED FILE STATE VERIFICATION
|
133
|
+
|
134
|
+
Before planning can begin, verify the file state:
|
135
|
+
|
136
|
+
```mermaid
|
137
|
+
graph TD
|
138
|
+
Start["File State<br>Verification"] --> CheckTasks{"tasks.md<br>initialized?"}
|
139
|
+
|
140
|
+
CheckTasks -->|"No"| ErrorTasks["ERROR:<br>Return to VAN Mode"]
|
141
|
+
CheckTasks -->|"Yes"| CheckActive{"activeContext.md<br>exists?"}
|
142
|
+
|
143
|
+
CheckActive -->|"No"| ErrorActive["ERROR:<br>Return to VAN Mode"]
|
144
|
+
CheckActive -->|"Yes"| ReadyPlan["Ready for<br>Planning"]
|
145
|
+
```
|
146
|
+
|
147
|
+
## 📝 TASKS.MD UPDATE FORMAT
|
148
|
+
|
149
|
+
During planning, update tasks.md with this structure:
|
150
|
+
|
151
|
+
```
|
152
|
+
# Task: [Task name]
|
153
|
+
|
154
|
+
## Description
|
155
|
+
[Detailed description]
|
156
|
+
|
157
|
+
## Complexity
|
158
|
+
Level: [2/3/4]
|
159
|
+
Type: [Enhancement/Feature/Complex System]
|
160
|
+
|
161
|
+
## Technology Stack
|
162
|
+
- Framework: [Selected framework]
|
163
|
+
- Build Tool: [Selected build tool]
|
164
|
+
- Language: [Selected language]
|
165
|
+
- Storage: [Selected storage mechanism]
|
166
|
+
|
167
|
+
## Technology Validation Checkpoints
|
168
|
+
- [ ] Project initialization command verified
|
169
|
+
- [ ] Required dependencies identified and installed
|
170
|
+
- [ ] Build configuration validated
|
171
|
+
- [ ] Hello world verification completed
|
172
|
+
- [ ] Test build passes successfully
|
173
|
+
|
174
|
+
## Status
|
175
|
+
- [x] Initialization complete
|
176
|
+
- [x] Planning complete
|
177
|
+
- [ ] Technology validation complete
|
178
|
+
- [ ] [Implementation steps]
|
179
|
+
|
180
|
+
## Implementation Plan
|
181
|
+
1. [Step 1]
|
182
|
+
- [Subtask 1.1]
|
183
|
+
- [Subtask 1.2]
|
184
|
+
2. [Step 2]
|
185
|
+
- [Subtask 2.1]
|
186
|
+
- [Subtask 2.2]
|
187
|
+
|
188
|
+
## Creative Phases Required
|
189
|
+
- [ ] [Component 1] Design
|
190
|
+
- [ ] [Component 2] Architecture
|
191
|
+
- [ ] [Component 3] Data Model
|
192
|
+
|
193
|
+
## Dependencies
|
194
|
+
- [Dependency 1]
|
195
|
+
- [Dependency 2]
|
196
|
+
|
197
|
+
## Challenges & Mitigations
|
198
|
+
- [Challenge 1]: [Mitigation strategy]
|
199
|
+
- [Challenge 2]: [Mitigation strategy]
|
200
|
+
```
|
201
|
+
|
202
|
+
## 📋 CREATIVE PHASE IDENTIFICATION
|
203
|
+
|
204
|
+
For Level 3-4 tasks, identify components requiring creative phases:
|
205
|
+
|
206
|
+
```mermaid
|
207
|
+
graph TD
|
208
|
+
Start["Creative Phase<br>Identification"] --> CheckComp{"Component<br>Analysis"}
|
209
|
+
|
210
|
+
CheckComp --> UI["UI/UX<br>Components"]
|
211
|
+
CheckComp --> Data["Data Model<br>Components"]
|
212
|
+
CheckComp --> Arch["Architecture<br>Components"]
|
213
|
+
CheckComp --> Algo["Algorithm<br>Components"]
|
214
|
+
|
215
|
+
UI & Data & Arch & Algo --> Decision{"Design Decisions<br>Required?"}
|
216
|
+
|
217
|
+
Decision -->|"Yes"| Flag["Flag for<br>Creative Phase"]
|
218
|
+
Decision -->|"No"| Skip["Standard<br>Implementation"]
|
219
|
+
|
220
|
+
Flag --> Document["Document in<br>tasks.md"]
|
221
|
+
```
|
222
|
+
|
223
|
+
## 📊 TECHNOLOGY VALIDATION CHECKLIST
|
224
|
+
|
225
|
+
```
|
226
|
+
✓ TECHNOLOGY VALIDATION CHECKLIST
|
227
|
+
- Technology stack clearly defined? [YES/NO]
|
228
|
+
- Project initialization command documented? [YES/NO]
|
229
|
+
- Required dependencies identified? [YES/NO]
|
230
|
+
- Minimal proof of concept created? [YES/NO]
|
231
|
+
- Hello world build/run successful? [YES/NO]
|
232
|
+
- Configuration files validated? [YES/NO]
|
233
|
+
- Test build completes successfully? [YES/NO]
|
234
|
+
|
235
|
+
→ If all YES: Technology validation complete - ready for next phase
|
236
|
+
→ If any NO: Resolve technology issues before proceeding
|
237
|
+
```
|
238
|
+
|
239
|
+
## 📊 PLAN VERIFICATION CHECKLIST
|
240
|
+
|
241
|
+
```
|
242
|
+
✓ PLAN VERIFICATION CHECKLIST
|
243
|
+
- Requirements clearly documented? [YES/NO]
|
244
|
+
- Technology stack validated? [YES/NO]
|
245
|
+
- Affected components identified? [YES/NO]
|
246
|
+
- Implementation steps detailed? [YES/NO]
|
247
|
+
- Dependencies documented? [YES/NO]
|
248
|
+
- Challenges & mitigations addressed? [YES/NO]
|
249
|
+
- Creative phases identified (Level 3-4)? [YES/NO/NA]
|
250
|
+
- tasks.md updated with plan? [YES/NO]
|
251
|
+
|
252
|
+
→ If all YES: Planning complete - ready for next mode
|
253
|
+
→ If any NO: Complete missing plan elements
|
254
|
+
```
|
255
|
+
|
256
|
+
## 🔄 MODE TRANSITION NOTIFICATION
|
257
|
+
|
258
|
+
When planning is complete, notify user with:
|
259
|
+
|
260
|
+
```
|
261
|
+
## PLANNING COMPLETE
|
262
|
+
|
263
|
+
✅ Implementation plan created
|
264
|
+
✅ Technology stack validated
|
265
|
+
✅ tasks.md updated with plan
|
266
|
+
✅ Challenges and mitigations documented
|
267
|
+
[✅ Creative phases identified (for Level 3-4)]
|
268
|
+
|
269
|
+
→ NEXT RECOMMENDED MODE: [CREATIVE/IMPLEMENT] MODE
|