@walwal-harness/cli 6.0.4 → 6.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.
- package/CHANGELOG.md +63 -0
- package/bin/init.js +121 -4
- package/commands/harness-solo.md +20 -20
- package/commands/harness-team.md +1 -1
- package/package.json +1 -1
- package/scripts/conductor-tick.sh +382 -0
- package/scripts/harness-archive.sh +14 -0
- package/scripts/harness-meeting-doc.sh +153 -0
- package/scripts/harness-next.sh +31 -0
- package/scripts/harness-session-start.sh +16 -5
- package/scripts/harness-task-session.sh +48 -0
- package/scripts/harness-user-prompt-submit.sh +27 -9
- package/skills/brainstorming/SKILL.md +4 -4
- package/skills/conductor/SKILL.md +12 -16
- package/skills/cqo/SKILL.md +7 -0
- package/skills/cto/SKILL.md +7 -0
- package/skills/dispatcher/SKILL.md +17 -28
- package/skills/evaluator-code-quality/SKILL.md +1 -1
- package/skills/evaluator-functional/SKILL.md +1 -1
- package/skills/evaluator-visual/SKILL.md +1 -1
- package/skills/generator-backend/SKILL.md +1 -1
- package/skills/generator-frontend/SKILL.md +1 -1
- package/skills/meeting-manager/SKILL.md +33 -1
- package/skills/planner/SKILL.md +23 -9
- package/skills/service-ops/SKILL.md +19 -4
|
@@ -90,6 +90,17 @@ Standup 종료 직후 호출됨. 직전 3회 standup의:
|
|
|
90
90
|
- `goal_adherence < 0.5` 24h 이상 → Spec Review (긴급) 소집
|
|
91
91
|
- warn 누적 ≥ 5건/Sprint → 다음 Standup에서 보고
|
|
92
92
|
|
|
93
|
+
### 3.7 Drift Classification
|
|
94
|
+
|
|
95
|
+
Service-Ops는 `goal_adherence` 하락을 감지했을 때 원인 분류 없이 Planner로 넘기면 안 된다. 먼저 아래 분류를 시도한다.
|
|
96
|
+
|
|
97
|
+
- `implementation_drift`: CQO FAIL / regression / 품질 축 미달이 직접 원인
|
|
98
|
+
- `planning_drift`: 구현/품질은 통과했지만 Goal 달성 가설이 어긋남
|
|
99
|
+
- `ops_drift`: 운영 환경, 배포, 로그, incident, KPI 이상이 원인
|
|
100
|
+
- `goal_drift`: Goal/KPI 정의 자체가 흔들리거나 Owner intent와 괴리
|
|
101
|
+
|
|
102
|
+
이 분류는 `progress.json.service_ops.drift_classification` 과 ops-report evidence에 기록되어야 한다.
|
|
103
|
+
|
|
93
104
|
---
|
|
94
105
|
|
|
95
106
|
## 4. Incident 모듈
|
|
@@ -176,6 +187,10 @@ CTO가 수신 → Hotfix/Backlog Feature로 변환 → Planner 등록.
|
|
|
176
187
|
|
|
177
188
|
```json
|
|
178
189
|
"service_ops": {
|
|
190
|
+
"drift_classification": "planning_drift",
|
|
191
|
+
"evidence": [
|
|
192
|
+
{ "source": ".harness/actions/ops-report-3.md", "kind": "ops-report" }
|
|
193
|
+
],
|
|
179
194
|
"monitor": {
|
|
180
195
|
"last_check": "<iso>",
|
|
181
196
|
"cadence_decided": "normal",
|
|
@@ -221,15 +236,15 @@ CTO가 수신 → Hotfix/Backlog Feature로 변환 → Planner 등록.
|
|
|
221
236
|
## 9. Conductor와의 인터페이스
|
|
222
237
|
|
|
223
238
|
- Conductor 틱에서:
|
|
224
|
-
- cron 도달 → spawn `service-ops
|
|
225
|
-
- red-alert 이벤트 → spawn `service-ops
|
|
226
|
-
- Sprint 종료 → spawn `service-ops
|
|
239
|
+
- cron 도달 → spawn `service-ops` + `service_ops.requested_mode="monitor"`
|
|
240
|
+
- red-alert 이벤트 → spawn `service-ops` + `service_ops.requested_mode="incident"`
|
|
241
|
+
- Sprint 종료 → spawn `service-ops` + `service_ops.requested_mode="auto-retro"`
|
|
227
242
|
- 모든 Service-Ops 산출물은 CTO 경유로만 코드 변경에 도달
|
|
228
243
|
|
|
229
244
|
## 10. Session Boundary Protocol
|
|
230
245
|
|
|
231
246
|
### On Start
|
|
232
|
-
1. `.harness/progress.json` 읽기 → 어느 모듈 호출인지 확인 (`
|
|
247
|
+
1. `.harness/progress.json` 읽기 → 어느 모듈 호출인지 확인 (`service_ops.requested_mode = monitor|incident|auto-retro`)
|
|
233
248
|
2. partial update: `current_agent = "service-ops"`, `service_ops.<mode>.running = true`
|
|
234
249
|
|
|
235
250
|
### On Complete
|