omgkit 2.10.1 → 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.
- package/README.md +46 -1
- package/package.json +2 -1
- package/plugin/agents/autonomous-orchestrator.yaml +215 -0
- package/plugin/commands/auto/approve.md +258 -0
- package/plugin/commands/auto/checkpoint.md +253 -0
- package/plugin/commands/auto/init.md +236 -0
- package/plugin/commands/auto/next.md +278 -0
- package/plugin/commands/auto/reject.md +278 -0
- package/plugin/commands/auto/resume.md +233 -0
- package/plugin/commands/auto/start.md +212 -0
- package/plugin/commands/auto/status.md +212 -0
- package/plugin/commands/auto/verify.md +353 -0
- package/plugin/skills/autonomous/project-orchestration/SKILL.md +332 -0
- package/plugin/templates/autonomous/archetypes/ai-model-building.yaml +443 -0
- package/plugin/templates/autonomous/archetypes/ai-powered-app.yaml +420 -0
- package/plugin/templates/autonomous/archetypes/api-service.yaml +78 -0
- package/plugin/templates/autonomous/archetypes/cli-tool.yaml +67 -0
- package/plugin/templates/autonomous/archetypes/desktop-app.yaml +371 -0
- package/plugin/templates/autonomous/archetypes/fullstack-app.yaml +97 -0
- package/plugin/templates/autonomous/archetypes/game-app.yaml +428 -0
- package/plugin/templates/autonomous/archetypes/iot-app.yaml +415 -0
- package/plugin/templates/autonomous/archetypes/library.yaml +64 -0
- package/plugin/templates/autonomous/archetypes/mobile-app.yaml +356 -0
- package/plugin/templates/autonomous/archetypes/saas-mvp.yaml +417 -0
- package/plugin/templates/autonomous/archetypes/simulation-app.yaml +428 -0
- package/plugin/templates/autonomous/artifacts-schema.yaml +465 -0
- package/plugin/templates/autonomous/decision-framework.yaml +337 -0
- package/plugin/templates/autonomous/discovery-questions.yaml +795 -0
- package/plugin/templates/autonomous/features-schema.yaml +254 -0
- package/plugin/templates/autonomous/memory-system.yaml +298 -0
- package/plugin/templates/autonomous/prd-template.md +251 -0
- package/plugin/templates/autonomous/state-schema.yaml +487 -0
- package/plugin/workflows/autonomous/discovery.yaml +232 -0
- package/plugin/workflows/autonomous/execution.yaml +275 -0
- package/plugin/workflows/autonomous/planning.yaml +244 -0
|
@@ -0,0 +1,353 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Run verification checks on autonomous project
|
|
3
|
+
allowed-tools: Read, Bash, Glob, Grep
|
|
4
|
+
argument-hint: "[--full | --quick | --phase <phase>]"
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Verify Autonomous Project
|
|
8
|
+
|
|
9
|
+
Run comprehensive verification checks on the autonomous project state and artifacts.
|
|
10
|
+
|
|
11
|
+
## Verification Modes
|
|
12
|
+
|
|
13
|
+
### Quick Verification
|
|
14
|
+
Fast checks for basic integrity:
|
|
15
|
+
```bash
|
|
16
|
+
/auto:verify --quick
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
### Full Verification
|
|
20
|
+
Complete verification of all aspects:
|
|
21
|
+
```bash
|
|
22
|
+
/auto:verify --full
|
|
23
|
+
/auto:verify
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
### Phase Verification
|
|
27
|
+
Verify specific phase artifacts:
|
|
28
|
+
```bash
|
|
29
|
+
/auto:verify --phase planning
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
## Verification Categories
|
|
33
|
+
|
|
34
|
+
### 1. State Integrity
|
|
35
|
+
|
|
36
|
+
Check `.omgkit/state.yaml`:
|
|
37
|
+
- [ ] File exists and is valid YAML
|
|
38
|
+
- [ ] Required fields present (project, phase, status)
|
|
39
|
+
- [ ] Phase matches archetype phases
|
|
40
|
+
- [ ] Progress data is consistent
|
|
41
|
+
- [ ] No orphaned references
|
|
42
|
+
|
|
43
|
+
### 2. Artifact Verification
|
|
44
|
+
|
|
45
|
+
For each phase's expected outputs:
|
|
46
|
+
- [ ] File exists
|
|
47
|
+
- [ ] File is not empty
|
|
48
|
+
- [ ] File format is valid (YAML, SQL, MD)
|
|
49
|
+
- [ ] Content matches expected structure
|
|
50
|
+
|
|
51
|
+
### 3. Code Quality
|
|
52
|
+
|
|
53
|
+
If code has been generated:
|
|
54
|
+
- [ ] TypeScript compiles without errors
|
|
55
|
+
- [ ] ESLint passes
|
|
56
|
+
- [ ] All tests pass
|
|
57
|
+
- [ ] Coverage meets threshold
|
|
58
|
+
|
|
59
|
+
### 4. Consistency Checks
|
|
60
|
+
|
|
61
|
+
- [ ] PRD features match implementation plan
|
|
62
|
+
- [ ] Schema matches models
|
|
63
|
+
- [ ] API spec matches routes
|
|
64
|
+
- [ ] Tests cover documented features
|
|
65
|
+
|
|
66
|
+
### 5. Memory Integrity
|
|
67
|
+
|
|
68
|
+
- [ ] Context files are current
|
|
69
|
+
- [ ] Decisions are recorded
|
|
70
|
+
- [ ] Journal entries exist for activities
|
|
71
|
+
|
|
72
|
+
## Verification Process
|
|
73
|
+
|
|
74
|
+
### 1. Load Configuration
|
|
75
|
+
|
|
76
|
+
```yaml
|
|
77
|
+
archetype: "saas-mvp"
|
|
78
|
+
current_phase: "backend"
|
|
79
|
+
quality_gates:
|
|
80
|
+
- command: "npm test"
|
|
81
|
+
required: true
|
|
82
|
+
- coverage_threshold: 80
|
|
83
|
+
```
|
|
84
|
+
|
|
85
|
+
### 2. Run Checks
|
|
86
|
+
|
|
87
|
+
Execute each verification category:
|
|
88
|
+
```
|
|
89
|
+
[1/5] State Integrity...
|
|
90
|
+
[2/5] Artifact Verification...
|
|
91
|
+
[3/5] Code Quality...
|
|
92
|
+
[4/5] Consistency Checks...
|
|
93
|
+
[5/5] Memory Integrity...
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
### 3. Collect Results
|
|
97
|
+
|
|
98
|
+
```yaml
|
|
99
|
+
verification_results:
|
|
100
|
+
timestamp: "2024-01-15T10:30:00Z"
|
|
101
|
+
mode: "full"
|
|
102
|
+
|
|
103
|
+
categories:
|
|
104
|
+
state_integrity:
|
|
105
|
+
passed: true
|
|
106
|
+
checks: 5
|
|
107
|
+
failures: 0
|
|
108
|
+
|
|
109
|
+
artifacts:
|
|
110
|
+
passed: true
|
|
111
|
+
checks: 8
|
|
112
|
+
failures: 0
|
|
113
|
+
|
|
114
|
+
code_quality:
|
|
115
|
+
passed: false
|
|
116
|
+
checks: 4
|
|
117
|
+
failures: 1
|
|
118
|
+
details:
|
|
119
|
+
- check: "coverage"
|
|
120
|
+
expected: 80
|
|
121
|
+
actual: 76
|
|
122
|
+
|
|
123
|
+
consistency:
|
|
124
|
+
passed: true
|
|
125
|
+
checks: 3
|
|
126
|
+
failures: 0
|
|
127
|
+
|
|
128
|
+
memory:
|
|
129
|
+
passed: true
|
|
130
|
+
checks: 3
|
|
131
|
+
failures: 0
|
|
132
|
+
```
|
|
133
|
+
|
|
134
|
+
## Output
|
|
135
|
+
|
|
136
|
+
### All Passing
|
|
137
|
+
```
|
|
138
|
+
## Verification Complete ✓
|
|
139
|
+
|
|
140
|
+
**Mode:** Full
|
|
141
|
+
**Duration:** 12.3s
|
|
142
|
+
|
|
143
|
+
### Results
|
|
144
|
+
|
|
145
|
+
| Category | Status | Checks |
|
|
146
|
+
|----------|--------|--------|
|
|
147
|
+
| State Integrity | ✅ Pass | 5/5 |
|
|
148
|
+
| Artifacts | ✅ Pass | 8/8 |
|
|
149
|
+
| Code Quality | ✅ Pass | 4/4 |
|
|
150
|
+
| Consistency | ✅ Pass | 3/3 |
|
|
151
|
+
| Memory | ✅ Pass | 3/3 |
|
|
152
|
+
|
|
153
|
+
**Total:** 23/23 checks passing
|
|
154
|
+
|
|
155
|
+
### Quality Metrics
|
|
156
|
+
- Test Coverage: 84% (threshold: 80%)
|
|
157
|
+
- TypeScript: No errors
|
|
158
|
+
- ESLint: No warnings
|
|
159
|
+
|
|
160
|
+
### Project Health: Excellent 🟢
|
|
161
|
+
|
|
162
|
+
---
|
|
163
|
+
|
|
164
|
+
**Commands:**
|
|
165
|
+
- `/auto:start` - Continue execution
|
|
166
|
+
- `/auto:status` - View full status
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
### With Failures
|
|
170
|
+
```
|
|
171
|
+
## Verification Complete ⚠️
|
|
172
|
+
|
|
173
|
+
**Mode:** Full
|
|
174
|
+
**Duration:** 15.7s
|
|
175
|
+
|
|
176
|
+
### Results
|
|
177
|
+
|
|
178
|
+
| Category | Status | Checks |
|
|
179
|
+
|----------|--------|--------|
|
|
180
|
+
| State Integrity | ✅ Pass | 5/5 |
|
|
181
|
+
| Artifacts | ✅ Pass | 8/8 |
|
|
182
|
+
| Code Quality | ⚠️ Fail | 3/4 |
|
|
183
|
+
| Consistency | ✅ Pass | 3/3 |
|
|
184
|
+
| Memory | ✅ Pass | 3/3 |
|
|
185
|
+
|
|
186
|
+
**Total:** 22/23 checks passing
|
|
187
|
+
|
|
188
|
+
### Failures
|
|
189
|
+
|
|
190
|
+
#### Code Quality: Coverage Below Threshold
|
|
191
|
+
|
|
192
|
+
**Expected:** 80%
|
|
193
|
+
**Actual:** 76%
|
|
194
|
+
|
|
195
|
+
**Uncovered Files:**
|
|
196
|
+
- `src/services/payment.service.ts` (62%)
|
|
197
|
+
- `src/utils/validation.ts` (71%)
|
|
198
|
+
|
|
199
|
+
**Suggested Fix:**
|
|
200
|
+
Add tests for payment service and validation utilities.
|
|
201
|
+
|
|
202
|
+
### Project Health: Needs Attention 🟡
|
|
203
|
+
|
|
204
|
+
---
|
|
205
|
+
|
|
206
|
+
**Actions Required:**
|
|
207
|
+
1. Increase test coverage to 80%
|
|
208
|
+
2. Run `/auto:verify` again after fixes
|
|
209
|
+
|
|
210
|
+
**Commands:**
|
|
211
|
+
- `/auto:verify --quick` - Quick re-check
|
|
212
|
+
- `npm test -- --coverage` - Run tests with coverage
|
|
213
|
+
```
|
|
214
|
+
|
|
215
|
+
### Critical Failures
|
|
216
|
+
```
|
|
217
|
+
## Verification Failed ❌
|
|
218
|
+
|
|
219
|
+
**Mode:** Full
|
|
220
|
+
**Duration:** 8.2s
|
|
221
|
+
|
|
222
|
+
### Critical Issues Found
|
|
223
|
+
|
|
224
|
+
#### 1. State Corruption
|
|
225
|
+
|
|
226
|
+
**Issue:** Phase "backend" not found in archetype
|
|
227
|
+
**File:** `.omgkit/state.yaml`
|
|
228
|
+
|
|
229
|
+
```yaml
|
|
230
|
+
# Current (invalid)
|
|
231
|
+
phase: "backend"
|
|
232
|
+
|
|
233
|
+
# Expected (one of)
|
|
234
|
+
phases: ["discovery", "planning", "foundation", "core", ...]
|
|
235
|
+
```
|
|
236
|
+
|
|
237
|
+
**Fix:** Update phase to valid archetype phase
|
|
238
|
+
|
|
239
|
+
#### 2. Missing Required Artifact
|
|
240
|
+
|
|
241
|
+
**Issue:** Schema file not found
|
|
242
|
+
**Expected:** `.omgkit/generated/schema.sql`
|
|
243
|
+
**Phase:** Planning (required output)
|
|
244
|
+
|
|
245
|
+
**Fix:** Run planning phase or create schema manually
|
|
246
|
+
|
|
247
|
+
### Project Health: Critical 🔴
|
|
248
|
+
|
|
249
|
+
---
|
|
250
|
+
|
|
251
|
+
**Recovery Options:**
|
|
252
|
+
|
|
253
|
+
1. **Auto-repair** (if possible)
|
|
254
|
+
```bash
|
|
255
|
+
/auto:verify --repair
|
|
256
|
+
```
|
|
257
|
+
|
|
258
|
+
2. **Manual fix**
|
|
259
|
+
- Fix state.yaml phase value
|
|
260
|
+
- Create missing schema.sql
|
|
261
|
+
|
|
262
|
+
3. **Reset to checkpoint**
|
|
263
|
+
```bash
|
|
264
|
+
/auto:resume --from planning
|
|
265
|
+
```
|
|
266
|
+
|
|
267
|
+
**Commands:**
|
|
268
|
+
- `/auto:status --verbose` - Detailed state info
|
|
269
|
+
- `/auto:resume --from discovery` - Restart from known good state
|
|
270
|
+
```
|
|
271
|
+
|
|
272
|
+
## Quick Verification Output
|
|
273
|
+
|
|
274
|
+
```
|
|
275
|
+
## Quick Verification ✓
|
|
276
|
+
|
|
277
|
+
**Duration:** 2.1s
|
|
278
|
+
|
|
279
|
+
### Essential Checks
|
|
280
|
+
- ✅ State file valid
|
|
281
|
+
- ✅ Current phase valid
|
|
282
|
+
- ✅ No blocking errors
|
|
283
|
+
- ✅ Tests passing
|
|
284
|
+
|
|
285
|
+
**Status:** Ready to continue
|
|
286
|
+
|
|
287
|
+
---
|
|
288
|
+
|
|
289
|
+
Run `/auto:verify --full` for comprehensive check.
|
|
290
|
+
```
|
|
291
|
+
|
|
292
|
+
## Phase Verification Output
|
|
293
|
+
|
|
294
|
+
```
|
|
295
|
+
## Phase Verification: Planning ✓
|
|
296
|
+
|
|
297
|
+
**Duration:** 4.3s
|
|
298
|
+
|
|
299
|
+
### Expected Outputs
|
|
300
|
+
- ✅ `.omgkit/generated/prd.md` (12.4 KB)
|
|
301
|
+
- ✅ `.omgkit/generated/schema.sql` (3.2 KB)
|
|
302
|
+
- ✅ `.omgkit/generated/api-spec.md` (8.7 KB)
|
|
303
|
+
|
|
304
|
+
### Validation
|
|
305
|
+
- ✅ PRD has all required sections
|
|
306
|
+
- ✅ Schema is valid SQL
|
|
307
|
+
- ✅ API spec follows OpenAPI format
|
|
308
|
+
|
|
309
|
+
### Quality Gates
|
|
310
|
+
- ✅ Schema validation passed
|
|
311
|
+
- ✅ API spec validation passed
|
|
312
|
+
|
|
313
|
+
**Phase Status:** Complete and verified
|
|
314
|
+
|
|
315
|
+
---
|
|
316
|
+
|
|
317
|
+
**Commands:**
|
|
318
|
+
- `/auto:approve` - Approve this phase
|
|
319
|
+
- `/auto:verify --phase foundation` - Verify next phase
|
|
320
|
+
```
|
|
321
|
+
|
|
322
|
+
## Repair Mode
|
|
323
|
+
|
|
324
|
+
Attempt automatic repairs for recoverable issues:
|
|
325
|
+
|
|
326
|
+
```bash
|
|
327
|
+
/auto:verify --repair
|
|
328
|
+
```
|
|
329
|
+
|
|
330
|
+
```
|
|
331
|
+
## Verification with Repair
|
|
332
|
+
|
|
333
|
+
### Issues Found: 2
|
|
334
|
+
### Auto-repairable: 1
|
|
335
|
+
|
|
336
|
+
#### Repaired ✓
|
|
337
|
+
|
|
338
|
+
1. **State Progress Inconsistency**
|
|
339
|
+
- Issue: steps_completed count mismatch
|
|
340
|
+
- Fix: Recalculated from actual completed steps
|
|
341
|
+
- Result: Updated state.yaml
|
|
342
|
+
|
|
343
|
+
#### Manual Repair Needed
|
|
344
|
+
|
|
345
|
+
2. **Missing Test File**
|
|
346
|
+
- Issue: `user.service.test.ts` referenced but not found
|
|
347
|
+
- Cannot auto-repair: Test content unknown
|
|
348
|
+
- Action: Create test file or remove reference
|
|
349
|
+
|
|
350
|
+
---
|
|
351
|
+
|
|
352
|
+
**Verification After Repair:** 22/23 passing
|
|
353
|
+
```
|
|
@@ -0,0 +1,332 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: Project Orchestration
|
|
3
|
+
description: Orchestrate autonomous project development through state-driven execution
|
|
4
|
+
category: autonomous
|
|
5
|
+
tools:
|
|
6
|
+
- Task
|
|
7
|
+
- Read
|
|
8
|
+
- Write
|
|
9
|
+
- Edit
|
|
10
|
+
- Bash
|
|
11
|
+
- Glob
|
|
12
|
+
- Grep
|
|
13
|
+
- AskUserQuestion
|
|
14
|
+
---
|
|
15
|
+
|
|
16
|
+
# Project Orchestration Skill
|
|
17
|
+
|
|
18
|
+
Orchestrate autonomous project development through state-driven execution.
|
|
19
|
+
|
|
20
|
+
## Overview
|
|
21
|
+
|
|
22
|
+
The Project Orchestration skill provides the core functionality for managing
|
|
23
|
+
autonomous project development. It handles state transitions, phase execution,
|
|
24
|
+
checkpoint management, and quality enforcement.
|
|
25
|
+
|
|
26
|
+
## Capabilities
|
|
27
|
+
|
|
28
|
+
### State Management
|
|
29
|
+
|
|
30
|
+
```yaml
|
|
31
|
+
# Read current state
|
|
32
|
+
state = load_state(".omgkit/state.yaml")
|
|
33
|
+
|
|
34
|
+
# Update state
|
|
35
|
+
update_state({
|
|
36
|
+
phase: "backend",
|
|
37
|
+
status: "in_progress",
|
|
38
|
+
progress: {
|
|
39
|
+
current_feature: "user_auth"
|
|
40
|
+
}
|
|
41
|
+
})
|
|
42
|
+
|
|
43
|
+
# Transition state
|
|
44
|
+
transition_state("in_progress", "checkpoint")
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
### Phase Execution
|
|
48
|
+
|
|
49
|
+
Execute phases according to archetype definition:
|
|
50
|
+
|
|
51
|
+
1. **Discovery Phase** - Requirements gathering via interview
|
|
52
|
+
2. **Planning Phase** - Generate specifications and schema
|
|
53
|
+
3. **Foundation Phase** - Project scaffolding and setup
|
|
54
|
+
4. **Core Phases** - Feature implementation (dynamic)
|
|
55
|
+
5. **Hardening Phase** - Security and performance
|
|
56
|
+
6. **Deployment Phase** - Production release
|
|
57
|
+
|
|
58
|
+
### Checkpoint Management
|
|
59
|
+
|
|
60
|
+
```yaml
|
|
61
|
+
# Create checkpoint
|
|
62
|
+
create_checkpoint({
|
|
63
|
+
type: "phase",
|
|
64
|
+
phase: "planning",
|
|
65
|
+
artifacts: ["schema.sql", "api-spec.md"]
|
|
66
|
+
})
|
|
67
|
+
|
|
68
|
+
# Check for pending checkpoint
|
|
69
|
+
if has_pending_checkpoint():
|
|
70
|
+
wait_for_approval()
|
|
71
|
+
|
|
72
|
+
# Approve checkpoint
|
|
73
|
+
approve_checkpoint()
|
|
74
|
+
|
|
75
|
+
# Reject with feedback
|
|
76
|
+
reject_checkpoint("Need soft delete columns")
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
### Decision Framework
|
|
80
|
+
|
|
81
|
+
Classify and handle decisions by autonomy level:
|
|
82
|
+
|
|
83
|
+
| Level | Action | Example |
|
|
84
|
+
|-------|--------|---------|
|
|
85
|
+
| 0 | Auto-execute | Code formatting |
|
|
86
|
+
| 1 | Execute + notify | Add dependency |
|
|
87
|
+
| 2 | Preview + quick approve | Database index |
|
|
88
|
+
| 3 | Full review | Auth approach |
|
|
89
|
+
| 4 | Human does it | API credentials |
|
|
90
|
+
|
|
91
|
+
### Quality Gates
|
|
92
|
+
|
|
93
|
+
Run quality checks between phases and features:
|
|
94
|
+
|
|
95
|
+
```yaml
|
|
96
|
+
quality_gates:
|
|
97
|
+
after_feature:
|
|
98
|
+
- npm test
|
|
99
|
+
- npm run lint
|
|
100
|
+
|
|
101
|
+
before_checkpoint:
|
|
102
|
+
- npm run build
|
|
103
|
+
- coverage >= 80%
|
|
104
|
+
|
|
105
|
+
before_deploy:
|
|
106
|
+
- security_scan
|
|
107
|
+
- performance_test
|
|
108
|
+
```
|
|
109
|
+
|
|
110
|
+
## Usage
|
|
111
|
+
|
|
112
|
+
### Initialize Project
|
|
113
|
+
|
|
114
|
+
```bash
|
|
115
|
+
# Start discovery interview
|
|
116
|
+
/auto:init my-saas-app
|
|
117
|
+
|
|
118
|
+
# Generates:
|
|
119
|
+
# - .omgkit/state.yaml
|
|
120
|
+
# - .omgkit/generated/prd.md
|
|
121
|
+
# - .omgkit/generated/discovery-answers.yaml
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
### Start Execution
|
|
125
|
+
|
|
126
|
+
```bash
|
|
127
|
+
# Begin autonomous execution
|
|
128
|
+
/auto:start
|
|
129
|
+
|
|
130
|
+
# Execution flow:
|
|
131
|
+
# 1. Load state and archetype
|
|
132
|
+
# 2. Execute current phase
|
|
133
|
+
# 3. Run quality gates
|
|
134
|
+
# 4. Update progress
|
|
135
|
+
# 5. Create checkpoint if needed
|
|
136
|
+
```
|
|
137
|
+
|
|
138
|
+
### Monitor Progress
|
|
139
|
+
|
|
140
|
+
```bash
|
|
141
|
+
# Check status
|
|
142
|
+
/auto:status
|
|
143
|
+
|
|
144
|
+
# Preview next action
|
|
145
|
+
/auto:next
|
|
146
|
+
|
|
147
|
+
# Run verification
|
|
148
|
+
/auto:verify
|
|
149
|
+
```
|
|
150
|
+
|
|
151
|
+
### Handle Checkpoints
|
|
152
|
+
|
|
153
|
+
```bash
|
|
154
|
+
# At checkpoint, review artifacts then:
|
|
155
|
+
/auto:approve # Continue
|
|
156
|
+
/auto:reject "reason" # Request changes
|
|
157
|
+
```
|
|
158
|
+
|
|
159
|
+
### Resume After Interruption
|
|
160
|
+
|
|
161
|
+
```bash
|
|
162
|
+
# Resume from saved state
|
|
163
|
+
/auto:resume
|
|
164
|
+
|
|
165
|
+
# Retry failed step
|
|
166
|
+
/auto:resume --retry
|
|
167
|
+
|
|
168
|
+
# Skip problematic step
|
|
169
|
+
/auto:resume --skip
|
|
170
|
+
```
|
|
171
|
+
|
|
172
|
+
## State Machine
|
|
173
|
+
|
|
174
|
+
```
|
|
175
|
+
┌─────────┐ start ┌─────────────┐
|
|
176
|
+
│ ready │────────────►│ in_progress │
|
|
177
|
+
└─────────┘ └──────┬──────┘
|
|
178
|
+
▲ │
|
|
179
|
+
│ approve │ phase_complete
|
|
180
|
+
│ │ decision_required
|
|
181
|
+
│ │ quality_fail
|
|
182
|
+
┌─────────────┐ │
|
|
183
|
+
│ checkpoint │◄───────────────┘
|
|
184
|
+
└─────────────┘
|
|
185
|
+
│
|
|
186
|
+
│ reject
|
|
187
|
+
▼
|
|
188
|
+
┌─────────────────┐
|
|
189
|
+
│ revision_needed │
|
|
190
|
+
└─────────────────┘
|
|
191
|
+
|
|
192
|
+
┌─────────────┐ error ┌─────────┐
|
|
193
|
+
│ in_progress │────────────►│ blocked │
|
|
194
|
+
└─────────────┘ └─────────┘
|
|
195
|
+
│
|
|
196
|
+
│ resume/skip
|
|
197
|
+
▼
|
|
198
|
+
┌─────────────┐
|
|
199
|
+
│ in_progress │
|
|
200
|
+
└─────────────┘
|
|
201
|
+
|
|
202
|
+
┌─────────────┐ all_complete ┌───────────┐
|
|
203
|
+
│ in_progress │───────────────►│ completed │
|
|
204
|
+
└─────────────┘ └───────────┘
|
|
205
|
+
```
|
|
206
|
+
|
|
207
|
+
## Memory Integration
|
|
208
|
+
|
|
209
|
+
### Context Files
|
|
210
|
+
|
|
211
|
+
Maintain current context in `.omgkit/memory/context/`:
|
|
212
|
+
|
|
213
|
+
- `project-brief.md` - Project overview
|
|
214
|
+
- `current-feature.md` - Active feature details
|
|
215
|
+
- `tech-stack.md` - Technology decisions
|
|
216
|
+
|
|
217
|
+
### Decision Log
|
|
218
|
+
|
|
219
|
+
Record all decisions in `.omgkit/memory/decisions/`:
|
|
220
|
+
|
|
221
|
+
```markdown
|
|
222
|
+
# Decision: Authentication Approach
|
|
223
|
+
|
|
224
|
+
**Date:** 2024-01-15
|
|
225
|
+
**Status:** Approved
|
|
226
|
+
|
|
227
|
+
## Context
|
|
228
|
+
Need to implement user authentication.
|
|
229
|
+
|
|
230
|
+
## Options Considered
|
|
231
|
+
1. Session-based auth
|
|
232
|
+
2. JWT with refresh tokens
|
|
233
|
+
3. OAuth only
|
|
234
|
+
|
|
235
|
+
## Decision
|
|
236
|
+
JWT with refresh tokens
|
|
237
|
+
|
|
238
|
+
## Rationale
|
|
239
|
+
- Stateless for scalability
|
|
240
|
+
- Works with mobile apps
|
|
241
|
+
- Standard approach
|
|
242
|
+
```
|
|
243
|
+
|
|
244
|
+
### Journal
|
|
245
|
+
|
|
246
|
+
Track daily progress in `.omgkit/memory/journal/`:
|
|
247
|
+
|
|
248
|
+
```markdown
|
|
249
|
+
# 2024-01-15 Development Journal
|
|
250
|
+
|
|
251
|
+
## Summary
|
|
252
|
+
Completed planning phase, started backend implementation.
|
|
253
|
+
|
|
254
|
+
## Completed
|
|
255
|
+
- Database schema design
|
|
256
|
+
- API specification
|
|
257
|
+
- User model implementation
|
|
258
|
+
|
|
259
|
+
## Challenges
|
|
260
|
+
- Decided on password hashing approach
|
|
261
|
+
- Resolved dependency conflict
|
|
262
|
+
|
|
263
|
+
## Tomorrow
|
|
264
|
+
- Complete auth service
|
|
265
|
+
- Add unit tests
|
|
266
|
+
```
|
|
267
|
+
|
|
268
|
+
## Error Recovery
|
|
269
|
+
|
|
270
|
+
### Test Failure Recovery
|
|
271
|
+
|
|
272
|
+
1. Analyze failure message
|
|
273
|
+
2. Identify failing test
|
|
274
|
+
3. Check related code
|
|
275
|
+
4. Attempt auto-fix if confidence > 70%
|
|
276
|
+
5. Retry tests
|
|
277
|
+
6. Block if still failing after 2 attempts
|
|
278
|
+
|
|
279
|
+
### Build Failure Recovery
|
|
280
|
+
|
|
281
|
+
1. Parse build error
|
|
282
|
+
2. Check for common issues
|
|
283
|
+
3. Fix imports, types, syntax
|
|
284
|
+
4. Retry build
|
|
285
|
+
5. Block if unfixable
|
|
286
|
+
|
|
287
|
+
### External Failure Recovery
|
|
288
|
+
|
|
289
|
+
1. Identify external service
|
|
290
|
+
2. Retry with exponential backoff
|
|
291
|
+
3. Max 3 retries
|
|
292
|
+
4. Block and report if persistent
|
|
293
|
+
|
|
294
|
+
## Configuration
|
|
295
|
+
|
|
296
|
+
### Archetype Selection
|
|
297
|
+
|
|
298
|
+
Based on project type, select appropriate archetype:
|
|
299
|
+
|
|
300
|
+
| Project Type | Archetype | Phases |
|
|
301
|
+
|-------------|-----------|--------|
|
|
302
|
+
| SaaS | saas-mvp | 7 phases |
|
|
303
|
+
| API | api-service | 6 phases |
|
|
304
|
+
| CLI | cli-tool | 5 phases |
|
|
305
|
+
| Library | library | 6 phases |
|
|
306
|
+
| Full-stack | fullstack-app | 8 phases |
|
|
307
|
+
|
|
308
|
+
### Autonomy Overrides
|
|
309
|
+
|
|
310
|
+
Configure autonomy levels in state:
|
|
311
|
+
|
|
312
|
+
```yaml
|
|
313
|
+
autonomy:
|
|
314
|
+
default_level: 1
|
|
315
|
+
overrides:
|
|
316
|
+
- pattern: "**/migrations/**"
|
|
317
|
+
level: 3
|
|
318
|
+
- pattern: "**/auth/**"
|
|
319
|
+
level: 3
|
|
320
|
+
- pattern: "**/tests/**"
|
|
321
|
+
level: 0
|
|
322
|
+
```
|
|
323
|
+
|
|
324
|
+
## Best Practices
|
|
325
|
+
|
|
326
|
+
1. **Always save state** after significant actions
|
|
327
|
+
2. **Run quality gates** before checkpoints
|
|
328
|
+
3. **Record decisions** for future reference
|
|
329
|
+
4. **Update memory** as context changes
|
|
330
|
+
5. **Handle errors gracefully** with recovery options
|
|
331
|
+
6. **Respect autonomy levels** for sensitive operations
|
|
332
|
+
7. **Provide clear progress** updates to user
|