modify framework

.codex/skills/harness-workflow/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: harness-workflow
-description: Use when planning or running this Harness framework: reading AGENTS.md and docs/*.md, discussing implementation scope, creating or updating phases/index.json, phases/{task}/index.json, phases/{task}/stepN.md, or invoking scripts/execute.py for staged Codex execution.
+description: Use when planning or running this C++/MSVC Harness framework: reading AGENTS.md and docs/*.md, discussing implementation scope, creating or updating phases/index.json, phases/{task}/index.json, phases/{task}/stepN.md, or invoking scripts/execute.py for staged Codex execution.
 ---
 
 # Harness Workflow
 
 ## Overview
 
-Use this skill to turn a user-approved task into small, self-contained Harness steps that another Codex session can execute reliably. Keep the workflow grounded in repository docs and executable acceptance criteria.
+Use this skill to turn a user-approved task into small, self-contained Harness steps that another Codex session can execute reliably. Keep every step grounded in repository docs, C++/MSVC constraints, TDD, and executable acceptance criteria.
 
 ## Workflow
 
@@ -23,10 +23,10 @@ Use this skill to turn a user-approved task into small, self-contained Harness s
 - Make every step self-contained. Do not rely on prior conversation; include all required context and file paths.
 - Force context gathering. Each step must tell Codex which docs and previous outputs to read before editing.
 - Specify interfaces and signatures, not full implementations, unless exact code is required for a constraint.
-- Put core invariants directly in the step: idempotency, security, data integrity, API contracts, or other non-negotiables.
-- Use executable acceptance criteria such as `npm run build && npm test`, not abstract statements.
-- Write cautions concretely: "Do not do X. Reason: Y."
-- Name steps with kebab-case slugs such as `project-setup`, `api-layer`, or `auth-flow`.
+- Put core invariants directly in the step: idempotency, numerical conventions, data integrity, API contracts, or other non-negotiables.
+- Use executable acceptance criteria such as `python scripts/validate_workspace.py`, not abstract statements.
+- For C++ behavior changes, require tests first and name the expected test file or test executable.
+- Name steps with kebab-case slugs such as `project-setup`, `core-types`, or `solver-validation`.
 
 ## Phase Files
 
@@ -47,12 +47,12 @@ Create `phases/{task-name}/index.json`:
 
 ```json
 {
-  "project": "<project-name>",
+  "project": "FESA Harness",
   "phase": "<task-name>",
   "steps": [
     { "step": 0, "name": "project-setup", "status": "pending" },
     { "step": 1, "name": "core-types", "status": "pending" },
-    { "step": 2, "name": "api-layer", "status": "pending" }
+    { "step": 2, "name": "validation-path", "status": "pending" }
   ]
 }
 ```
@@ -85,11 +85,15 @@ Rules:
 
 {Concrete instructions with file paths, interfaces, signatures, and rules.}
 
+## Tests To Write First
+
+- {Exact C++ or Python test file and behavior to add before implementation.}
+
 ## Acceptance Criteria
 
 ```bash
-npm run build
-npm test
+python -m unittest discover -s scripts -p "test_*.py"
+python scripts/validate_workspace.py
 ```
 
 ## 검증 절차
@@ -99,6 +103,7 @@ npm test
    - ARCHITECTURE.md 디렉토리 구조를 따르는가?
    - ADR 기술 스택을 벗어나지 않았는가?
    - AGENTS.md CRITICAL 규칙을 위반하지 않았는가?
+   - C++ 변경에는 관련 테스트가 존재하는가?
 3. 결과에 따라 `phases/{task-name}/index.json`의 해당 step을 업데이트한다:
    - 성공: `"status": "completed"`, `"summary": "산출물 한 줄 요약"`
    - 3회 수정 시도 후 실패: `"status": "error"`, `"error_message": "구체적 에러 내용"`
@@ -106,7 +111,7 @@ npm test
 
 ## 금지사항
 
-- {Do not do X. Reason: Y.}
+- JavaScript/TypeScript/npm fallback을 추가하지 마라. Reason: 이 Harness는 C++/MSVC 전용이다.
 - 기존 테스트를 깨뜨리지 마라.
 ```