omgkit 2.11.0 → 2.12.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.
@@ -0,0 +1,415 @@
1
+ name: "IoT Application"
2
+ id: iot-app
3
+ description: "Internet of Things system with device management, real-time data, and edge computing"
4
+ estimated_duration: "4-8 weeks"
5
+ icon: "microchip"
6
+
7
+ # Default technology recommendations
8
+ defaults:
9
+ protocol: mqtt
10
+ broker: mosquitto
11
+ backend: nodejs
12
+ database: timescaledb
13
+ cloud: aws_iot
14
+ frontend: nextjs
15
+ device_sdk: esp_idf
16
+
17
+ # Alternative technology stacks
18
+ alternatives:
19
+ protocol:
20
+ - id: mqtt
21
+ name: "MQTT"
22
+ description: "Lightweight, pub/sub, most popular for IoT"
23
+ - id: coap
24
+ name: "CoAP"
25
+ description: "REST-like for constrained devices"
26
+ - id: http
27
+ name: "HTTP/REST"
28
+ description: "Standard web protocols"
29
+ - id: websocket
30
+ name: "WebSocket"
31
+ description: "Real-time bidirectional"
32
+
33
+ cloud:
34
+ - id: aws_iot
35
+ name: "AWS IoT Core"
36
+ description: "Full-featured, scalable"
37
+ - id: azure_iot
38
+ name: "Azure IoT Hub"
39
+ description: "Enterprise integration"
40
+ - id: gcp_iot
41
+ name: "Google Cloud IoT"
42
+ description: "ML integration"
43
+ - id: self_hosted
44
+ name: "Self-Hosted"
45
+ description: "Full control, on-premise"
46
+
47
+ database:
48
+ - id: timescaledb
49
+ name: "TimescaleDB"
50
+ description: "PostgreSQL-based time-series"
51
+ - id: influxdb
52
+ name: "InfluxDB"
53
+ description: "Purpose-built time-series"
54
+ - id: questdb
55
+ name: "QuestDB"
56
+ description: "High-performance time-series"
57
+
58
+ # Phases of development
59
+ phases:
60
+ - id: discovery
61
+ name: "IoT Discovery"
62
+ description: "Define devices, protocols, and data requirements"
63
+ order: 1
64
+ checkpoint: true
65
+ checkpoint_message: |
66
+ IoT discovery complete. Review:
67
+ - Device types and capabilities
68
+ - Communication protocols
69
+ - Data collection requirements
70
+ - Security requirements
71
+
72
+ Approve to proceed with planning.
73
+
74
+ steps:
75
+ - id: device_inventory
76
+ name: "Device Inventory"
77
+ agent: planner
78
+ description: "Catalog all device types"
79
+
80
+ - id: protocol_selection
81
+ name: "Protocol Selection"
82
+ agent: architect
83
+ description: "Select communication protocols"
84
+
85
+ - id: data_requirements
86
+ name: "Data Requirements"
87
+ agent: planner
88
+ description: "Define data collection needs"
89
+
90
+ - id: security_requirements
91
+ name: "Security Requirements"
92
+ agent: security-auditor
93
+ description: "Define security requirements"
94
+
95
+ outputs:
96
+ - ".omgkit/generated/device-inventory.md"
97
+ - ".omgkit/generated/protocol-decision.md"
98
+ - ".omgkit/generated/data-requirements.md"
99
+
100
+ - id: planning
101
+ name: "Architecture Planning"
102
+ description: "Design device architecture, data flow, and security model"
103
+ order: 2
104
+ checkpoint: true
105
+ checkpoint_message: |
106
+ Architecture complete. Review:
107
+ - Device architecture
108
+ - Data flow design
109
+ - Security model
110
+
111
+ Approve to begin foundation.
112
+
113
+ steps:
114
+ - id: device_architecture
115
+ name: "Device Architecture"
116
+ agent: architect
117
+ description: "Design device firmware architecture"
118
+
119
+ - id: data_flow
120
+ name: "Data Flow Design"
121
+ agent: architect
122
+ description: "Design data ingestion pipeline"
123
+
124
+ - id: security_model
125
+ name: "Security Model"
126
+ agent: security-auditor
127
+ description: "Design device identity and auth"
128
+
129
+ - id: scaling_plan
130
+ name: "Scaling Plan"
131
+ agent: architect
132
+ description: "Plan for device fleet scaling"
133
+
134
+ outputs:
135
+ - ".omgkit/generated/device-architecture.md"
136
+ - ".omgkit/generated/data-flow.md"
137
+ - ".omgkit/generated/iot-security.md"
138
+
139
+ - id: foundation
140
+ name: "Foundation"
141
+ description: "Set up device firmware and communication layer"
142
+ order: 3
143
+ checkpoint: false
144
+
145
+ steps:
146
+ - id: firmware_setup
147
+ name: "Firmware Setup"
148
+ agent: fullstack-developer
149
+ description: "Initialize device firmware project"
150
+
151
+ - id: communication_layer
152
+ name: "Communication Layer"
153
+ agent: fullstack-developer
154
+ description: "Implement MQTT/CoAP client"
155
+
156
+ - id: device_provisioning
157
+ name: "Device Provisioning"
158
+ agent: fullstack-developer
159
+ description: "Create provisioning workflow"
160
+
161
+ - id: local_storage
162
+ name: "Local Storage"
163
+ agent: fullstack-developer
164
+ description: "Implement on-device storage"
165
+
166
+ outputs:
167
+ - "firmware/"
168
+ - "firmware/src/mqtt/"
169
+ - "firmware/src/storage/"
170
+
171
+ - id: backend
172
+ name: "Backend Infrastructure"
173
+ description: "Set up MQTT broker, data ingestion, and storage"
174
+ order: 4
175
+ checkpoint: true
176
+ checkpoint_message: |
177
+ Backend complete. Review:
178
+ - MQTT broker configuration
179
+ - Data ingestion pipeline
180
+ - Time-series storage
181
+
182
+ Approve to build dashboard.
183
+
184
+ steps:
185
+ - id: broker_setup
186
+ name: "MQTT Broker"
187
+ agent: cicd-manager
188
+ description: "Set up MQTT broker"
189
+
190
+ - id: ingestion_pipeline
191
+ name: "Data Ingestion"
192
+ agent: fullstack-developer
193
+ description: "Build data ingestion pipeline"
194
+
195
+ - id: time_series_db
196
+ name: "Time-Series Database"
197
+ agent: database-admin
198
+ description: "Set up time-series storage"
199
+
200
+ - id: api_layer
201
+ name: "API Layer"
202
+ agent: fullstack-developer
203
+ description: "Build device management API"
204
+
205
+ outputs:
206
+ - "backend/src/mqtt/"
207
+ - "backend/src/ingestion/"
208
+ - "backend/src/api/"
209
+
210
+ - id: dashboard
211
+ name: "Dashboard & Visualization"
212
+ description: "Real-time visualization and device management UI"
213
+ order: 5
214
+ checkpoint: true
215
+ checkpoint_message: |
216
+ Dashboard complete. Review:
217
+ - Real-time data visualization
218
+ - Device management interface
219
+ - Alerting configuration
220
+
221
+ Approve to add edge computing.
222
+
223
+ steps:
224
+ - id: realtime_viz
225
+ name: "Real-Time Visualization"
226
+ agent: fullstack-developer
227
+ description: "Build real-time data charts"
228
+
229
+ - id: device_management
230
+ name: "Device Management UI"
231
+ agent: fullstack-developer
232
+ description: "Create device management interface"
233
+
234
+ - id: alerting
235
+ name: "Alerting System"
236
+ agent: fullstack-developer
237
+ description: "Implement threshold-based alerts"
238
+
239
+ - id: historical_data
240
+ name: "Historical Data"
241
+ agent: fullstack-developer
242
+ description: "Build historical data views"
243
+
244
+ outputs:
245
+ - "dashboard/src/components/"
246
+ - "dashboard/src/pages/"
247
+
248
+ - id: edge_computing
249
+ name: "Edge Computing"
250
+ description: "Local processing and offline operation"
251
+ order: 6
252
+ checkpoint: false
253
+
254
+ steps:
255
+ - id: local_processing
256
+ name: "Local Processing"
257
+ agent: fullstack-developer
258
+ description: "Implement on-device data processing"
259
+
260
+ - id: offline_operation
261
+ name: "Offline Operation"
262
+ agent: fullstack-developer
263
+ description: "Handle offline scenarios"
264
+
265
+ - id: data_sync
266
+ name: "Data Sync"
267
+ agent: fullstack-developer
268
+ description: "Sync data when connectivity returns"
269
+
270
+ - id: edge_analytics
271
+ name: "Edge Analytics"
272
+ agent: fullstack-developer
273
+ description: "Run analytics at the edge"
274
+
275
+ outputs:
276
+ - "firmware/src/edge/"
277
+ - "firmware/src/sync/"
278
+
279
+ - id: security
280
+ name: "Security Hardening"
281
+ description: "Device authentication, encryption, and OTA updates"
282
+ order: 7
283
+ checkpoint: true
284
+ checkpoint_message: |
285
+ Security hardening complete. Review:
286
+ - Device authentication
287
+ - Data encryption
288
+ - OTA update security
289
+
290
+ Approve to proceed with scaling.
291
+
292
+ steps:
293
+ - id: device_auth
294
+ name: "Device Authentication"
295
+ agent: security-auditor
296
+ description: "Implement device identity and auth"
297
+
298
+ - id: encryption
299
+ name: "Data Encryption"
300
+ agent: security-auditor
301
+ description: "Encrypt data in transit and at rest"
302
+
303
+ - id: ota_updates
304
+ name: "OTA Updates"
305
+ agent: fullstack-developer
306
+ description: "Implement secure OTA updates"
307
+
308
+ - id: security_audit
309
+ name: "Security Audit"
310
+ agent: security-auditor
311
+ description: "Audit entire IoT stack"
312
+
313
+ outputs:
314
+ - "firmware/src/security/"
315
+ - "backend/src/ota/"
316
+
317
+ - id: scaling
318
+ name: "Fleet Management & Scaling"
319
+ description: "Manage large device fleets and batch operations"
320
+ order: 8
321
+ checkpoint: true
322
+ checkpoint_message: |
323
+ Scaling setup complete. Review:
324
+ - Fleet management tools
325
+ - Batch operations
326
+ - Monitoring at scale
327
+
328
+ This is the final checkpoint.
329
+
330
+ steps:
331
+ - id: fleet_management
332
+ name: "Fleet Management"
333
+ agent: fullstack-developer
334
+ description: "Build fleet management tools"
335
+
336
+ - id: batch_operations
337
+ name: "Batch Operations"
338
+ agent: fullstack-developer
339
+ description: "Implement batch device operations"
340
+
341
+ - id: monitoring
342
+ name: "Fleet Monitoring"
343
+ agent: fullstack-developer
344
+ description: "Monitor device fleet health"
345
+
346
+ - id: auto_scaling
347
+ name: "Auto-Scaling"
348
+ agent: cicd-manager
349
+ description: "Configure backend auto-scaling"
350
+
351
+ outputs:
352
+ - "dashboard/src/fleet/"
353
+ - "backend/src/batch/"
354
+
355
+ # Autonomy rules for this archetype
356
+ autonomy_rules:
357
+ - pattern: "**/firmware/**"
358
+ level: 3
359
+ reason: "Firmware changes are critical"
360
+ - pattern: "**/security/**"
361
+ level: 3
362
+ reason: "Security code needs review"
363
+ - pattern: "**/ota/**"
364
+ level: 3
365
+ reason: "OTA updates are critical"
366
+ - pattern: "**/dashboard/**"
367
+ level: 1
368
+ reason: "Dashboard UI is less critical"
369
+ - pattern: "**/api/**"
370
+ level: 2
371
+ reason: "API changes need review"
372
+
373
+ # Quality gates
374
+ quality_gates:
375
+ after_feature:
376
+ - "firmware builds successfully"
377
+ - "backend tests pass"
378
+ before_checkpoint:
379
+ - "device connects to broker"
380
+ - "data flows correctly"
381
+ before_deploy:
382
+ - "security audit passes"
383
+ - "load test with 1000+ devices"
384
+ - "OTA update tested"
385
+
386
+ # IoT-specific discovery questions
387
+ discovery_additions:
388
+ - category: "Devices"
389
+ questions:
390
+ - "What types of devices/sensors?"
391
+ - "How many devices initially? At scale?"
392
+ - "Device hardware capabilities? (MCU, memory, connectivity)"
393
+ - "Power source? (battery, mains, solar)"
394
+ - "Environmental conditions? (temperature, humidity, outdoor)"
395
+
396
+ - category: "Connectivity"
397
+ questions:
398
+ - "Connectivity type? (WiFi, cellular, LoRa, Zigbee, BLE)"
399
+ - "Expected connectivity reliability?"
400
+ - "Data transmission frequency?"
401
+ - "Payload size per transmission?"
402
+
403
+ - category: "Data"
404
+ questions:
405
+ - "Types of data collected?"
406
+ - "Data retention requirements?"
407
+ - "Real-time processing needs?"
408
+ - "Edge processing requirements?"
409
+
410
+ - category: "Security"
411
+ questions:
412
+ - "Device authentication method?"
413
+ - "Firmware update requirements?"
414
+ - "Compliance requirements? (industrial, medical)"
415
+ - "Physical security concerns?"