uctm 1.1.0 → 1.2.0

package/README.md

@@ -60,24 +60,6 @@ uc-taskmanager was built to solve this. When you provide a requirement as input,
 
 Each step runs in an **isolated subagent pipeline**, so your context stays clean and every decision is documented.
 
-### The Bigger Picture
-
-This agent is designed to work with an **SDD-based requirement management and automated development system** — a server application that links requirement management → automated development → plans and artifacts. The full system architecture is documented in [`docs/spec_SDD_with_ucagent_requirement.md`](docs/spec_SDD_with_ucagent_requirement.md). Use it as a reference to build your own system tailored to your needs.
-
-### A Note on Language
-
-Starting from v1.1.0, uctm supports **multi-language agent prompts**. Use `uctm init --lang en` for English or `--lang ko` for Korean. All 12 agent files are available in both languages with identical structure and functionality.
-
-I'm Korean, so you'll find Korean in some internal documents (design specs, commit messages). Modern translation tools handle Korean well, so this shouldn't be a barrier.
-
-### What This Took
-
-I built this agent and the accompanying SDD requirement management system in roughly **one calendar month — about 2 weeks of actual development time** (8 hours/day). Ideas become reality. The technical and time barriers that once stopped you have fallen. This is the age of AI agents.
-
-**Good luck. Build something great.**
-
-This project is open source. Use it freely, share your ideas, and let's push this forward together.
-
 ---
 
 Six subagents work across any project and any language, automatically handling **request routing → task decomposition → dependency management → code implementation → verification → commit**.
@@ -265,7 +247,7 @@ uctm update --lang en
 ```bash
 git clone https://github.com/UCJung/uc-taskmanager-claude-agent.git /tmp/uc-tm
 mkdir -p .claude/agents
-cp /tmp/uc-tm/agents/*.md .claude/agents/
+cp /tmp/uc-tm/agents/en/*.md .claude/agents/   # or agents/ko/ for Korean
 rm -rf /tmp/uc-tm
 git add .claude/agents/ && git commit -m "chore: add uc-taskmanager agents"
 ```
@@ -953,6 +935,12 @@ The dashboard is still available at `http://localhost:PORT` — it just won't au
 
 ---
 
+## The Bigger Picture
+
+This agent is designed to work with an **SDD-based requirement management and automated development system** — a server application that links requirement management → automated development → plans and artifacts. The full system architecture is documented in [`docs/spec_SDD_with_ucagent_requirement.md`](docs/spec_SDD_with_ucagent_requirement.md). Use it as a reference to build your own system tailored to your needs.
+
+---
+
 ## License
 
 GPL-3.0

package/agents/en/agent-flow.md

@@ -1,106 +1,106 @@
-# Agent Flow — Main Claude Orchestration Guide
-
-> **All agent invocations are performed by Main Claude.**
-> Subagents only return results (dispatch XML or task-result XML) after completing their work.
-> Main Claude receives the return values and invokes the next agent.
-
----
-
-## Execution Mode Decision
-
-```
-[] tag detected → invoke router
-    │
-    Check router return value (execution-mode)
-    │
-    ├─ direct   → router handles everything (no additional invocations)
-    ├─ pipeline → Execute § pipeline procedure
-    └─ full     → Execute § full procedure
-```
-
----
-
-## direct Mode
-
-Router handles everything on its own. No additional invocations by Main Claude.
-
----
-
-## pipeline Mode
-
-```
-1. Invoke router → creates PLAN.md + TASK-00.md + returns builder dispatch XML
-2. Invoke builder (dispatch XML as prompt)
-3. Invoke verifier (builder result as prompt)
-4. Invoke committer (verifier result as prompt)
-```
-
----
-
-## full Mode
-
-```
-1. Invoke router → creates WORK directory + returns planner dispatch XML
-2. Invoke planner (dispatch XML as prompt) → creates PLAN.md + TASK files
-3. Invoke scheduler → DAG analysis + READY TASK + returns builder dispatch XML
-4. Invoke builder (dispatch XML as prompt) → implementation
-5. Invoke verifier (builder result as prompt) → verification
-6. Invoke committer (verifier result as prompt) → commit
-7. If incomplete TASKs remain, return to step 3
-```
-
-Parallel execution: If scheduler returns multiple READY TASKs, invoke builders concurrently.
-
----
-
-## Agent Role Summary
-
-| Agent | Return Value | Invoked By |
-|-------|-------------|------------|
-| router | execution-mode + dispatch XML | Main Claude |
-| planner | PLAN.md/TASK file creation completion report | Main Claude |
-| scheduler | READY TASK + dispatch XML | Main Claude |
-| builder | task-result XML (includes context-handoff) | Main Claude |
-| verifier | task-result XML | Main Claude |
-| committer | task-result XML + commit hash | Main Claude |
-
----
-
-## Bash CLI Execution (Server Automation)
-
-Method to run pipeline independently without an interactive session. `claude -p` acts as Main Claude.
-
-```bash
-env -u CLAUDECODE -u ANTHROPIC_API_KEY claude -p \
-  "[new-work] {task description}" \
-  --dangerously-skip-permissions \
-  --output-format stream-json \
-  --verbose \
-  2>&1 | tee /tmp/pipeline.log
-```
-
-| Option | Purpose |
-|--------|---------|
-| `env -u CLAUDECODE` | Bypass nested execution blocking |
-| `env -u ANTHROPIC_API_KEY` | Use subscription auth (Max) instead of API key |
-| `--dangerously-skip-permissions` | Skip permission prompts for unattended execution |
-| `--output-format stream-json --verbose` | Streaming for real-time monitoring |
-
-Resume interrupted pipeline:
-```bash
-env -u CLAUDECODE -u ANTHROPIC_API_KEY claude -p \
-  "Resume WORK-XX pipeline." \
-  --dangerously-skip-permissions
-```
-
-Verification result (WORK-24): `claude -p` → 9 Task tool invocations → full auto-completion of router/planner/scheduler/builder/verifier/committer confirmed.
-
----
-
-## Context Transfer (Sliding Window)
-
-| Distance | Level | Content |
-|----------|-------|---------|
-| Immediate predecessor | FULL | what + why + caution + incomplete |
-| 2 steps back | SUMMARY | what only, 1-2 lines |
-| 3+ steps back | DROP | Not transmitted |
+# Agent Flow — Main Claude Orchestration Guide
+
+> **All agent invocations are performed by Main Claude.**
+> Subagents only return results (dispatch XML or task-result XML) after completing their work.
+> Main Claude receives the return values and invokes the next agent.
+
+---
+
+## Execution Mode Decision
+
+```
+[] tag detected → invoke router
+    │
+    Check router return value (execution-mode)
+    │
+    ├─ direct   → router handles everything (no additional invocations)
+    ├─ pipeline → Execute § pipeline procedure
+    └─ full     → Execute § full procedure
+```
+
+---
+
+## direct Mode
+
+Router handles everything on its own. No additional invocations by Main Claude.
+
+---
+
+## pipeline Mode
+
+```
+1. Invoke router → creates PLAN.md + TASK-00.md + returns builder dispatch XML
+2. Invoke builder (dispatch XML as prompt)
+3. Invoke verifier (builder result as prompt)
+4. Invoke committer (verifier result as prompt)
+```
+
+---
+
+## full Mode
+
+```
+1. Invoke router → creates WORK directory + returns planner dispatch XML
+2. Invoke planner (dispatch XML as prompt) → creates PLAN.md + TASK files
+3. Invoke scheduler → DAG analysis + READY TASK + returns builder dispatch XML
+4. Invoke builder (dispatch XML as prompt) → implementation
+5. Invoke verifier (builder result as prompt) → verification
+6. Invoke committer (verifier result as prompt) → commit
+7. If incomplete TASKs remain, return to step 3
+```
+
+Parallel execution: If scheduler returns multiple READY TASKs, invoke builders concurrently.
+
+---
+
+## Agent Role Summary
+
+| Agent | Return Value | Invoked By |
+|-------|-------------|------------|
+| router | execution-mode + dispatch XML | Main Claude |
+| planner | PLAN.md/TASK file creation completion report | Main Claude |
+| scheduler | READY TASK + dispatch XML | Main Claude |
+| builder | task-result XML (includes context-handoff) | Main Claude |
+| verifier | task-result XML | Main Claude |
+| committer | task-result XML + commit hash | Main Claude |
+
+---
+
+## Bash CLI Execution (Server Automation)
+
+Method to run pipeline independently without an interactive session. `claude -p` acts as Main Claude.
+
+```bash
+env -u CLAUDECODE -u ANTHROPIC_API_KEY claude -p \
+  "[new-work] {task description}" \
+  --dangerously-skip-permissions \
+  --output-format stream-json \
+  --verbose \
+  2>&1 | tee /tmp/pipeline.log
+```
+
+| Option | Purpose |
+|--------|---------|
+| `env -u CLAUDECODE` | Bypass nested execution blocking |
+| `env -u ANTHROPIC_API_KEY` | Use subscription auth (Max) instead of API key |
+| `--dangerously-skip-permissions` | Skip permission prompts for unattended execution |
+| `--output-format stream-json --verbose` | Streaming for real-time monitoring |
+
+Resume interrupted pipeline:
+```bash
+env -u CLAUDECODE -u ANTHROPIC_API_KEY claude -p \
+  "Resume WORK-XX pipeline." \
+  --dangerously-skip-permissions
+```
+
+Verification result (WORK-24): `claude -p` → 9 Task tool invocations → full auto-completion of router/planner/scheduler/builder/verifier/committer confirmed.
+
+---
+
+## Context Transfer (Sliding Window)
+
+| Distance | Level | Content |
+|----------|-------|---------|
+| Immediate predecessor | FULL | what + why + caution + incomplete |
+| 2 steps back | SUMMARY | what only, 1-2 lines |
+| 3+ steps back | DROP | Not transmitted |

package/agents/en/builder.md

@@ -35,11 +35,11 @@ You are the **Builder** — the implementation agent that receives a TASK specif
 
 | File | Purpose |
 |------|---------|
-| `agents/file-content-schema.md` | File format schema |
-| `agents/shared-prompt-sections.md` | Common rules (TASK ID, PLAN.md 7 fields, WORK-LIST) |
-| `agents/xml-schema.md` | XML communication format |
-| `agents/context-policy.md` | Sliding window rules |
-| `agents/work-activity-log.md` | Activity Log rules (log_work function, STAGE table) |
+| `.claude/agents/file-content-schema.md` | File format schema |
+| `.claude/agents/shared-prompt-sections.md` | Common rules (TASK ID, PLAN.md 7 fields, WORK-LIST) |
+| `.claude/agents/xml-schema.md` | XML communication format |
+| `.claude/agents/context-policy.md` | Sliding window rules |
+| `.claude/agents/work-activity-log.md` | Activity Log rules (log_work function, STAGE table) |
 
 ### 3-2. XML Input Parsing
 

package/agents/en/committer.md

@@ -35,11 +35,11 @@ You are the **Committer** — the agent that generates the result report for a v
 
 | File | Purpose |
 |------|---------|
-| `agents/file-content-schema.md` | File format schema |
-| `agents/shared-prompt-sections.md` | Common rules |
-| `agents/xml-schema.md` | XML communication format |
-| `agents/context-policy.md` | Sliding window rules |
-| `agents/work-activity-log.md` | Activity Log rules (log_work function, STAGE table) |
+| `.claude/agents/file-content-schema.md` | File format schema |
+| `.claude/agents/shared-prompt-sections.md` | Common rules |
+| `.claude/agents/xml-schema.md` | XML communication format |
+| `.claude/agents/context-policy.md` | Sliding window rules |
+| `.claude/agents/work-activity-log.md` | Activity Log rules (log_work function, STAGE table) |
 
 ### 3-2. XML Input Parsing
 
@@ -66,7 +66,7 @@ On gate failure:
 
 ### 3-4. Result Report Generation
 
-→ see `agents/file-content-schema.md` § 4 (format + language-specific section headers)
+→ see `.claude/agents/file-content-schema.md` § 4 (format + language-specific section headers)
 
 Create `works/{WORK_ID}/TASK-XX_result.md`.
 - builder context-handoff `what` → "Builder Context" section
@@ -155,8 +155,24 @@ Committer-specific additional fields:
 </next-tasks>
 ```
 
-Do not change WORK-LIST.md to COMPLETED — changed only at git push time.
-→ see `agents/shared-prompt-sections.md` § 8
+### 3-9-1. WORK-LIST.md Auto-Completion
+
+Check if this is the last TASK. If so, change WORK-LIST.md from `IN_PROGRESS` to `COMPLETED`.
+
+```bash
+# Check if last TASK
+TOTAL=$(ls works/${WORK_ID}/TASK-*.md 2>/dev/null | grep -cv '_result\|_progress')
+DONE=$(ls works/${WORK_ID}/TASK-*_result.md 2>/dev/null | wc -l)
+
+if [ "$DONE" -ge "$TOTAL" ]; then
+  # Change IN_PROGRESS → COMPLETED in WORK-LIST.md
+  sed -i "s/| ${WORK_ID} |\\(.*\\)| IN_PROGRESS |\\(.*\\)|\\(.*\\)|/| ${WORK_ID} |\\1| COMPLETED |\\2| $(date '+%Y-%m-%d') |/" works/WORK-LIST.md
+  git add works/WORK-LIST.md
+  git commit --amend --no-edit
+fi
+```
+
+→ see `.claude/agents/shared-prompt-sections.md` § 8
 
 ---
 
@@ -173,7 +189,7 @@ Do not change WORK-LIST.md to COMPLETED — changed only at git push time.
 - If Files changed is empty → immediately return FAIL
 
 ### WORK-LIST.md Rules
-- Changing to COMPLETED is prohibited — changed only at git push time
+- Automatically change WORK-LIST.md from `IN_PROGRESS` to `COMPLETED` when the last TASK is completed
 
 ### Output Language Rule
 → see `shared-prompt-sections.md` § 1

package/agents/en/context-policy.md

@@ -56,7 +56,7 @@ Processing:
 2. Gate passed → write result.md + git commit
 3. Gate failed → return FAIL (triggers scheduler retry)
 
-Output: → `agents/file-content-schema.md` § 4 reference
+Output: → `.claude/agents/file-content-schema.md` § 4 reference
 
 ## Inter-TASK Dependency Transfer
 

package/agents/en/file-content-schema.md

@@ -23,7 +23,7 @@ Path: `works/{WORK_ID}/PLAN.md`
 # WORK-01: {title}
 
 > Created: {YYYY-MM-DD}
-> Requirement: {REQ-XXX | N/A}
+> Requirement: {REQ-XXX | user request text}
 > Execution-Mode: {direct | pipeline | full}
 > Project: {project name}
 > Tech Stack: {stack}

package/agents/en/planner.md

@@ -37,9 +37,9 @@ WORK (unit of work)    — Goal unit of the user's request
 
 | File | Purpose |
 |------|---------|
-| `agents/file-content-schema.md` | File format schema (PLAN.md 7 fields, TASK format) |
-| `agents/shared-prompt-sections.md` | Common rules (TASK ID, WORK-LIST rules) |
-| `agents/work-activity-log.md` | Activity Log rules (log_work function, STAGE table) |
+| `.claude/agents/file-content-schema.md` | File format schema (PLAN.md 7 fields, TASK format) |
+| `.claude/agents/shared-prompt-sections.md` | Common rules (TASK ID, WORK-LIST rules) |
+| `.claude/agents/work-activity-log.md` | Activity Log rules (log_work function, STAGE table) |
 
 ### 3-2. Project Exploration (Discovery Process)
 
@@ -103,7 +103,7 @@ Use `mcp__sequential-thinking__sequentialthinking` when TASK count is 4+ or depe
 
 ### 3-6. Output Structure
 
-→ see `agents/file-content-schema.md` § 7
+→ see `.claude/agents/file-content-schema.md` § 7
 
 Creation responsibilities:
 - `PLAN.md`, `TASK-XX.md`, `TASK-XX_progress.md` (initial template) → Planner
@@ -113,7 +113,7 @@ Creation responsibilities:
 
 When creating TASK files, always create `TASK-XX_progress.md` template in the same directory.
 
-File formats: → `agents/file-content-schema.md` § 1 (PLAN.md), § 2 (TASK), § 3 (progress initial value)
+File formats: → `.claude/agents/file-content-schema.md` § 1 (PLAN.md), § 2 (TASK), § 3 (progress initial value)
 
 ### 3-7. MCP Tool Usage (Serena)
 
@@ -143,7 +143,7 @@ Record resolved language in PLAN.md `> Language:` field. Write all outputs in th
 ### 3-9. Requirement Code (REQ) Recording
 
 - `REQ-XXX` pattern exists: `> Requirement: REQ-XXX`
-- If absent: `> Requirement: N/A`
+- If absent: `> Requirement: {user request text}` — record the user's request text as-is
 
 ---
 

package/agents/en/router.md

@@ -34,10 +34,10 @@ You are the **Router** — the top-level orchestrator that analyzes user request
 
 | File | Purpose |
 |------|---------|
-| `agents/file-content-schema.md` | File format schema (PLAN.md 7 fields, TASK format, result.md format) |
-| `agents/shared-prompt-sections.md` | Common rules (TASK ID pattern, WORK-LIST rules, log_work function) |
-| `agents/xml-schema.md` | XML communication format (dispatch / task-result structure) |
-| `agents/work-activity-log.md` | Activity Log rules (log_work function, STAGE table, reference collection) |
+| `.claude/agents/file-content-schema.md` | File format schema (PLAN.md 7 fields, TASK format, result.md format) |
+| `.claude/agents/shared-prompt-sections.md` | Common rules (TASK ID pattern, WORK-LIST rules, log_work function) |
+| `.claude/agents/xml-schema.md` | XML communication format (dispatch / task-result structure) |
+| `.claude/agents/work-activity-log.md` | Activity Log rules (log_work function, STAGE table, reference collection) |
 
 ### 3-2. Execution-Mode Determination
 
@@ -103,9 +103,21 @@ Router handles everything on its own. Use Serena MCP first for code exploration:
 16. Add WORK-LIST.md IN_PROGRESS
 ```
 
-### 3-5. pipeline Mode Execution
+### 3-5. Pipeline Mode Execution
 
-**builder dispatch** Execute subagent then dispatch message
+> ⚠️ In pipeline mode, Router only creates PLAN.md + TASK-NN.md.
+> Code modification, builder invocation, and commits are strictly prohibited. Only return dispatch XML.
+
+```
+1.  Determine WORK ID
+2.  mkdir works/WORK-NN/
+3.  log_work INIT "WORK-NN created — Execution-Mode: pipeline"
+4.  Create PLAN.md (Execution-Mode: pipeline) → file-content-schema.md § 1
+5.  Create TASK-NN.md (multiple if needed) → file-content-schema.md § 2
+6.  Add IN_PROGRESS to WORK-LIST.md
+7.  Generate and return dispatch XML below. **Invocation is performed by Main Claude.**
+8.  log_work DISPATCH "Builder dispatch XML returned"
+```
 
 → dispatch XML format: see `xml-schema.md` § 1 (to="builder", task="TASK-00", execution-mode="pipeline")
 
@@ -138,10 +150,10 @@ Router handles everything on its own. Use Serena MCP first for code exploration:
 - Only enable auto mode when "run automatically" is explicitly stated (valid only within current WORK)
 
 ### WORK-LIST.md Rules
-→ see `agents/shared-prompt-sections.md` § 8
+→ see `.claude/agents/shared-prompt-sections.md` § 8
 
 - On WORK creation: add `IN_PROGRESS`
-- COMPLETED change: **only at git push time** — Router must not change directly
+- COMPLETED change: automatically changed by committer when last TASK is completed
 
 ### File Naming Rules
 - TASK filenames: `TASK-XX.md` format

package/agents/en/scheduler.md

@@ -38,11 +38,11 @@ You are the **Scheduler** — the WORK pipeline execution agent.
 
 | File | Purpose |
 |------|---------|
-| `agents/file-content-schema.md` | File format schema |
-| `agents/shared-prompt-sections.md` | Common rules |
-| `agents/xml-schema.md` | XML communication format |
-| `agents/context-policy.md` | Sliding Window rules |
-| `agents/work-activity-log.md` | Activity Log rules (log_work function, STAGE table) |
+| `.claude/agents/file-content-schema.md` | File format schema |
+| `.claude/agents/shared-prompt-sections.md` | Common rules |
+| `.claude/agents/xml-schema.md` | XML communication format |
+| `.claude/agents/context-policy.md` | Sliding Window rules |
+| `.claude/agents/work-activity-log.md` | Activity Log rules (log_work function, STAGE table) |
 
 ### 3-2. WORK Identification and Initial Load
 
@@ -132,7 +132,7 @@ Committer FAIL retry:
 
 ### 3-9. Progress Report
 
-Update PROGRESS.md after TASK completion (→ see `agents/file-content-schema.md` § 6) and output status:
+Update PROGRESS.md after TASK completion (→ see `.claude/agents/file-content-schema.md` § 6) and output status:
 
 ```
 ✅ TASK-XX completed — commit: {hash}
@@ -164,7 +164,7 @@ Multi-WORK status check:
 
 ### WORK-LIST.md Rules
 - Do not change WORK-LIST.md to COMPLETED — changed only at git push time
-- → see `agents/shared-prompt-sections.md` § 8
+- → see `.claude/agents/shared-prompt-sections.md` § 8
 
 ### Output Language Rule
 → see `shared-prompt-sections.md` § 1

package/agents/en/shared-prompt-sections.md

@@ -106,12 +106,12 @@ echo "$DONE / $TOTAL"
 
 ## § 7. PLAN.md Required Meta-Information — 7 Fields
 
-→ `agents/file-content-schema.md` § 1 reference
+→ `.claude/agents/file-content-schema.md` § 1 reference
 
 | Field | Required | Description |
 |-------|----------|-------------|
 | `> Created:` | ✅ | YYYY-MM-DD |
-| `> Requirement:` | ✅ | `REQ-XXX` or `N/A` |
+| `> Requirement:` | ✅ | `REQ-XXX` or user request text |
 | `> Execution-Mode:` | ✅ | `direct` / `pipeline` / `full` |
 | `> Project:` | ✅ | Project name |
 | `> Tech Stack:` | ✅ | Detected tech stack |
@@ -127,11 +127,10 @@ File: `works/WORK-LIST.md`
 | Status | Timing |
 |--------|--------|
 | `IN_PROGRESS` | Added when WORK directory is created |
-| `COMPLETED` | Changed only at git push time |
+| `COMPLETED` | Automatically changed by committer when last TASK is completed |
 
-- committer / scheduler → changing to COMPLETED is prohibited
 - Must add IN_PROGRESS when WORK directory is created
-- Do not leave as IN_PROGRESS after push
+- committer: after committing the last TASK, change WORK-LIST.md from `IN_PROGRESS` to `COMPLETED`
 
 ---
 

package/agents/en/verifier.md

@@ -35,10 +35,10 @@ Verifies the results of TASKs completed by the Builder, checking build, lint, te
 
 | File | Purpose |
 |------|---------|
-| `agents/shared-prompt-sections.md` | Common rules |
-| `agents/xml-schema.md` | XML communication format |
-| `agents/context-policy.md` | Sliding Window rules |
-| `agents/work-activity-log.md` | Activity Log rules (log_work function, STAGE table) |
+| `.claude/agents/shared-prompt-sections.md` | Common rules |
+| `.claude/agents/xml-schema.md` | XML communication format |
+| `.claude/agents/context-policy.md` | Sliding Window rules |
+| `.claude/agents/work-activity-log.md` | Activity Log rules (log_work function, STAGE table) |
 
 ### 3-2. XML Input Parsing
 

package/agents/en/work-activity-log.md

@@ -1,45 +1,45 @@
-# Work Activity Log
-
-Defines the rules for each agent to record WORK progress in the `works/{WORK_ID}/work_{WORK_ID}.log` file.
-
----
-
-# 1. Stages and Log Content
-* On first execution: The received prompt message** Content of the prompt message received at agent startup (Required)
-* On Callback invocation: Called Callback URL, success status, Payload, Response (Required)
-* During work: Work items and work content
-* On task completion: The prompt message sent to other agents** Content of the prompt message received at agent startup (Required)
-
-## log_work Function
-
-```bash
-AGENT_NAME="ROUTER"  # Set appropriately in each agent file
-
-log_work() {
-  local WORK_ID="$1" AGENT="$2" STAGE="$3" DESC="$4"
-  mkdir -p "works/${WORK_ID}"
-  printf '[%s]_%s_%s_%s\n' \
-    "$(date '+%Y-%m-%dT%H:%M:%S')" "$AGENT" "$STAGE" "$DESC" \
-    >> "works/${WORK_ID}/work_${WORK_ID}.log"
-}
-```
-
----
-
-## STAGE Table
-
-| STAGE | Timing | Description Example |
-|-------|--------|---------------------|
-| `INIT` | After WORK_ID determined | `WORK-NN created — Execution-Mode: direct/pipeline/full` |
-| `REF` | After STARTUP references | `References: CLAUDE.md, .agent/router_rule_config.json, agents/file-content-schema.md` |
-| `PLAN` | After PLAN.md + TASK files created | `PLAN.md, TASK-00.md created` |
-| `IMPL` | When direct mode code implementation starts | `Code implementation started — References: {modified file list}` |
-| `BUILD` | After self-check passes | `Build/lint passed` |
-| `COMMIT` | After git commit completed | `commit {hash}` |
-| `DISPATCH` | On pipeline/full dispatch | `Builder dispatch` or `Planner dispatch` |
-
----
-
-## Reference Collection Rules
-
-Cumulatively track files read during STARTUP and subsequent exploration, recording them all at once during the `REF` stage.
+# Work Activity Log
+
+Defines the rules for each agent to record WORK progress in the `works/{WORK_ID}/work_{WORK_ID}.log` file.
+
+---
+
+# 1. Stages and Log Content
+* On first execution: The received prompt message** Content of the prompt message received at agent startup (Required)
+* On Callback invocation: Called Callback URL, success status, Payload, Response (Required)
+* During work: Work items and work content
+* On task completion: The prompt message sent to other agents** Content of the prompt message received at agent startup (Required)
+
+## log_work Function
+
+```bash
+AGENT_NAME="ROUTER"  # Set appropriately in each agent file
+
+log_work() {
+  local WORK_ID="$1" AGENT="$2" STAGE="$3" DESC="$4"
+  mkdir -p "works/${WORK_ID}"
+  printf '[%s]_%s_%s_%s\n' \
+    "$(date '+%Y-%m-%dT%H:%M:%S')" "$AGENT" "$STAGE" "$DESC" \
+    >> "works/${WORK_ID}/work_${WORK_ID}.log"
+}
+```
+
+---
+
+## STAGE Table
+
+| STAGE | Timing | Description Example |
+|-------|--------|---------------------|
+| `INIT` | After WORK_ID determined | `WORK-NN created — Execution-Mode: direct/pipeline/full` |
+| `REF` | After STARTUP references | `References: CLAUDE.md, .agent/router_rule_config.json, agents/file-content-schema.md` |
+| `PLAN` | After PLAN.md + TASK files created | `PLAN.md, TASK-00.md created` |
+| `IMPL` | When direct mode code implementation starts | `Code implementation started — References: {modified file list}` |
+| `BUILD` | After self-check passes | `Build/lint passed` |
+| `COMMIT` | After git commit completed | `commit {hash}` |
+| `DISPATCH` | On pipeline/full dispatch | `Builder dispatch` or `Planner dispatch` |
+
+---
+
+## Reference Collection Rules
+
+Cumulatively track files read during STARTUP and subsequent exploration, recording them all at once during the `REF` stage.