From a058ef76746a78890b7c0581e07d1b61a043d206 Mon Sep 17 00:00:00 2001 From: "KOKO\\Mimi" Date: Wed, 12 Aug 2026 15:31:46 +0900 Subject: [PATCH] docs: clarify Harness phase ownership --- .agents/skills/harness/SKILL.md | 2 +- .codex/skills/fesa-cpp-msvc-tdd/SKILL.md | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/.agents/skills/harness/SKILL.md b/.agents/skills/harness/SKILL.md index 0f5627b..2ded056 100644 --- a/.agents/skills/harness/SKILL.md +++ b/.agents/skills/harness/SKILL.md @@ -15,7 +15,7 @@ description: Use when planning agentic implementation phases, creating phases/in | 책임 | 소유자 | |---|---| -| branch, pending Step 선택, retry, timestamps, commits, advancement | Executor (`scripts/execute.py`) | +| branch, pending Step 선택, retry, timestamps, commits, advancement, top-level phase status | Executor (`scripts/execute.py`) | | Executor-selected current Step의 작업과 해당 Step의 `status` 및 `summary` / `error_message` / `blocked_reason` payload | Implementation Agent | | PreToolUse interception과 Stop whole-project validation | `.codex/hooks.json`으로 등록된 hooks | diff --git a/.codex/skills/fesa-cpp-msvc-tdd/SKILL.md b/.codex/skills/fesa-cpp-msvc-tdd/SKILL.md index 00011a8..14dcbf2 100644 --- a/.codex/skills/fesa-cpp-msvc-tdd/SKILL.md +++ b/.codex/skills/fesa-cpp-msvc-tdd/SKILL.md @@ -34,7 +34,8 @@ For Harness implementation, also read `.agents/skills/harness/SKILL.md`, Executor-selected current `stepN.md`. Do not start another pending Step. 3. Execute the current Step as `RED -> observed failure -> minimal GREEN -> focused/full VERIFY`. Update only its Codex-owned `status` plus `summary`, `error_message`, or `blocked_reason`. - The Executor owns branch, pending-Step selection, retry, timestamps, commits, and advancement. + The Executor owns branch, pending-Step selection, retry, timestamps, commits, advancement, + and top-level phase status. 4. Hooks are automatic through `.codex/hooks.json`: PreToolUse intercepts before edits and Stop performs whole-project validation. Do not manually run their entry points as substitutes. 5. RED: write the planned unit, integration, parser/I/O, or reference-comparison test first.