uctm 1.2.0 → 1.3.0

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

@@ -1,45 +1,45 @@
-# Work Activity Log
-
-각 에이전트가 WORK 진행 상황을 `works/{WORK_ID}/work_{WORK_ID}.log` 파일에 기록하는 규칙을 정의한다.
-
----
-
-# 1. 작업 단계 및 로그 기록 내용
-* 최초 실행 시 : 수신한 프롬프트 메시지** Agent 시작 시 수신한 프롬프트 메시지 내용 (Required 필수)
-* Callback 호출 시 : 호출한 Callback URL, 성공여부, Payload, Respoonse (Required 필수)
-* 작업 진행 시 : 작업항목 및 작업내용 
-* 수행작업 완료 시 : 타 Agent에 전송한 프롬프트 메시지** Agent 시작 시 수신한 프롬프트 메시지 내용 (Required 필수)
-
-## log_work 함수
-
-```bash
-AGENT_NAME="ROUTER"  # 각 에이전트 파일에서 적절히 설정
-
-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 테이블
-
-| STAGE | 시점 | 설명 예시 |
-|-------|------|-----------|
-| `INIT` | WORK_ID 결정 후 | `WORK-NN 생성 — Execution-Mode: direct/pipeline/full` |
-| `REF` | STARTUP 참조 직후 | `참조: CLAUDE.md, .agent/router_rule_config.json, agents/file-content-schema.md` |
-| `PLAN` | PLAN.md + TASK 파일 생성 완료 | `PLAN.md, TASK-00.md 생성 완료` |
-| `IMPL` | direct 모드 코드 구현 시작 | `코드 구현 시작 — 참조: {수정 대상 파일 목록}` |
-| `BUILD` | self-check 통과 | `빌드/린트 통과` |
-| `COMMIT` | git commit 완료 | `commit {hash}` |
-| `DISPATCH` | pipeline/full dispatch | `Builder dispatch` 또는 `Planner dispatch` |
-
----
-
-## 참조 자료 수집 규칙
-
-STARTUP에서 읽은 파일과 이후 탐색한 파일을 누적 추적하여 `REF` 단계에서 한 번에 기록.
+# Work Activity Log
+
+각 에이전트가 WORK 진행 상황을 `works/{WORK_ID}/work_{WORK_ID}.log` 파일에 기록하는 규칙을 정의한다.
+
+---
+
+# 1. 작업 단계 및 로그 기록 내용
+* 최초 실행 시 : 수신한 프롬프트 메시지** Agent 시작 시 수신한 프롬프트 메시지 내용 (Required 필수)
+* Callback 호출 시 : 호출한 Callback URL, 성공여부, Payload, Respoonse (Required 필수)
+* 작업 진행 시 : 작업항목 및 작업내용 
+* 수행작업 완료 시 : 타 Agent에 전송한 프롬프트 메시지** Agent 시작 시 수신한 프롬프트 메시지 내용 (Required 필수)
+
+## log_work 함수
+
+```bash
+AGENT_NAME="SPECIFIER"  # 각 에이전트 파일에서 적절히 설정
+
+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 테이블
+
+| STAGE | 시점 | 설명 예시 |
+|-------|------|-----------|
+| `INIT` | WORK_ID 결정 후 | `WORK-NN 생성 — Execution-Mode: direct/pipeline/full` |
+| `REF` | STARTUP 참조 직후 | `참조: CLAUDE.md, .agent/router_rule_config.json, agents/file-content-schema.md` |
+| `PLAN` | PLAN.md + TASK 파일 생성 완료 | `PLAN.md, TASK-00.md 생성 완료` |
+| `IMPL` | direct 모드 코드 구현 시작 | `코드 구현 시작 — 참조: {수정 대상 파일 목록}` |
+| `BUILD` | self-check 통과 | `빌드/린트 통과` |
+| `COMMIT` | git commit 완료 | `commit {hash}` |
+| `DISPATCH` | pipeline/full dispatch | `Builder dispatch` 또는 `Planner dispatch` |
+
+---
+
+## 참조 자료 수집 규칙
+
+STARTUP에서 읽은 파일과 이후 탐색한 파일을 누적 추적하여 `REF` 단계에서 한 번에 기록.

package/agents/ko/xml-schema.md

@@ -1,109 +1,108 @@
-# Agent Communication XML Schema
-
-uc-taskmanager 에이전트 간 XML 통신 포맷 정의.
-
----
-
-## 1. Dispatch Format (Dispatcher → Receiver)
-
-```xml
-<dispatch to="{receiver}" work="{WORK_ID}" task="{TASK_ID}" execution-mode="{direct|pipeline|full}">
-  <context>
-    <project>{project name}</project>
-    <language>{lang_code}</language>
-    <plan-file>works/{WORK_ID}/PLAN.md</plan-file>
-  </context>
-  <task-spec>
-    <file>works/{WORK_ID}/TASK-XX.md</file>
-    <title>{title}</title>
-    <action>{implement|verify|commit|plan|route}</action>
-    <description>{optional}</description>
-  </task-spec>
-  <previous-results>
-    <result task="{TASK_ID}" status="{PASS|FAIL|SKIP}">{summary}</result>
-  </previous-results>
-  <cache-hint sections="{section1},{section2}"/>
-</dispatch>
-```
-
-| 속성 | 값 |
-|------|----|
-| `to` | builder, verifier, committer, planner, scheduler, router |
-| `task` | `TASK-NN` — WORK prefix 포함 금지 |
-| `execution-mode` | direct / pipeline / full (생략 시 full로 간주) |
-
----
-
-## 2. Task Result Format (Receiver → Dispatcher)
-
-```xml
-<task-result work="{WORK_ID}" task="{TASK_ID}" agent="{agent}" status="{PASS|FAIL}">
-  <summary>{1-2줄 요약}</summary>
-  <files-changed>
-    <file action="{created|modified|deleted}" path="{path}">{description}</file>
-  </files-changed>
-  <verification>
-    <check name="{type}" status="{PASS|FAIL|N/A}">{output}</check>
-  </verification>
-  <notes>{참고사항}</notes>
-</task-result>
-```
-
----
-
-## 3. Dispatcher-Receiver 매핑
-
-| Dispatcher | Receiver | execution-mode | 설명 |
-|------------|----------|:--------------:|------|
-| Router | (자기 자신) | `direct` | 서브에이전트 없음. Router가 직접 구현+commit+콜백 |
-| Router | Planner | `full` | 복잡 WORK 계획 |
-| Router | Scheduler | `full` | 계획된 WORK 실행 |
-| Router | Builder | `pipeline` | TASK 1개 구현 |
-| Router | Verifier | `pipeline` | TASK 1개 검증 |
-| Router | Committer | `pipeline` | TASK 1개 커밋 |
-| Scheduler | Builder | `full` | TASK N개 구현 |
-| Scheduler | Verifier | `full` | TASK N개 검증 |
-| Scheduler | Committer | `full` | TASK N개 커밋 |
-
----
-
-## 4. Context-Handoff Element
-
-```xml
-<context-handoff from="{agent}" detail-level="{FULL|SUMMARY|DROP}">
-  <what>{변경/검증 사항}</what>
-  <why>{의사결정 근거}</why>       <!-- FULL only -->
-  <caution>{주의사항}</caution>    <!-- FULL only -->
-  <incomplete>{미완료 사항}</incomplete>  <!-- FULL only -->
-</context-handoff>
-```
-
-| detail-level | 포함 필드 |
-|:---:|---|
-| `FULL` | what, why, caution, incomplete |
-| `SUMMARY` | what만 (1-3줄) |
-| `DROP` | 요소 생략 |
-
----
-
-## 5. execution-mode별 에이전트 행동
-
-| 에이전트 | direct | pipeline | full |
-|---------|--------|----------|------|
-| Router | 구현+self-check+result.md+commit+콜백 직접 | PLAN 생성 후 B→V→C dispatch | Planner에 dispatch |
-| Planner | 호출 안 됨 | 호출 안 됨 | PLAN.md 생성 |
-| Scheduler | 호출 안 됨 | 호출 안 됨 | DAG 관리 + [B→V→C]×N |
-| Builder | 호출 안 됨 | 정상 실행 | 정상 실행 |
-| Verifier | 호출 안 됨 | 정상 실행 | 정상 실행 |
-| Committer | 호출 안 됨 | result.md+commit+콜백 | result.md+commit+콜백 |
-
-불변 항목 (모드 무관):
-
-| 항목 | direct | pipeline/full |
-|------|:---:|:---:|
-| `works/WORK-NN/` 디렉토리 | Router | Router/Planner |
-| `PLAN.md` | Router | Router/Planner |
-| `TASK-XX.md` | Router | Router/Planner |
-| `TASK-XX_result.md` | Router | Committer |
-| COMMITTER DONE 콜백 | Router | Committer |
-| `WORK-LIST.md` IN_PROGRESS | Router | Router |
+# Agent Communication XML Schema
+
+uc-taskmanager 에이전트 간 XML 통신 포맷 정의.
+
+---
+
+## 1. Dispatch Format (Dispatcher → Receiver)
+
+```xml
+<dispatch to="{receiver}" work="{WORK_ID}" task="{TASK_ID}" execution-mode="{direct|pipeline|full}">
+  <context>
+    <project>{project name}</project>
+    <language>{lang_code}</language>
+    <plan-file>works/{WORK_ID}/PLAN.md</plan-file>
+  </context>
+  <task-spec>
+    <file>works/{WORK_ID}/TASK-XX.md</file>
+    <title>{title}</title>
+    <action>{implement|verify|commit|plan|route}</action>
+    <description>{optional}</description>
+  </task-spec>
+  <previous-results>
+    <result task="{TASK_ID}" status="{PASS|FAIL|SKIP}">{summary}</result>
+  </previous-results>
+  <cache-hint sections="{section1},{section2}"/>
+</dispatch>
+```
+
+| 속성 | 값 |
+|------|----|
+| `to` | builder, verifier, committer, planner, scheduler, specifier |
+| `task` | `TASK-NN` — WORK prefix 포함 금지 |
+| `execution-mode` | direct / pipeline / full (생략 시 full로 간주) |
+
+---
+
+## 2. Task Result Format (Receiver → Dispatcher)
+
+```xml
+<task-result work="{WORK_ID}" task="{TASK_ID}" agent="{agent}" status="{PASS|FAIL}">
+  <summary>{1-2줄 요약}</summary>
+  <files-changed>
+    <file action="{created|modified|deleted}" path="{path}">{description}</file>
+  </files-changed>
+  <verification>
+    <check name="{type}" status="{PASS|FAIL|N/A}">{output}</check>
+  </verification>
+  <notes>{참고사항}</notes>
+</task-result>
+```
+
+---
+
+## 3. Dispatcher-Receiver 매핑
+
+| Dispatcher | Receiver | execution-mode | 설명 |
+|------------|----------|:--------------:|------|
+| Specifier | Builder | `direct` | 겸임: TASK 1개 구현 (Verifier 생략) |
+| Specifier | Planner | `pipeline/full` | 위임: 복잡 WORK 계획 |
+| Planner | Builder | `pipeline` | TASK 구현 |
+| Planner | Scheduler | `full` | DAG 관리 + 실행 |
+| Scheduler | Builder | `full` | TASK N개 구현 |
+| Scheduler | Verifier | `full` | TASK N개 검증 |
+| Scheduler | Committer | `full` | TASK N개 커밋 |
+
+---
+
+## 4. Context-Handoff Element
+
+```xml
+<context-handoff from="{agent}" detail-level="{FULL|SUMMARY|DROP}">
+  <what>{변경/검증 사항}</what>
+  <why>{의사결정 근거}</why>       <!-- FULL only -->
+  <caution>{주의사항}</caution>    <!-- FULL only -->
+  <incomplete>{미완료 사항}</incomplete>  <!-- FULL only -->
+</context-handoff>
+```
+
+| detail-level | 포함 필드 |
+|:---:|---|
+| `FULL` | what, why, caution, incomplete |
+| `SUMMARY` | what만 (1-3줄) |
+| `DROP` | 요소 생략 |
+
+---
+
+## 5. execution-mode별 에이전트 행동
+
+| 에이전트 | direct | pipeline | full |
+|---------|--------|----------|------|
+| Specifier | Requirement.md + PLAN.md + TASK (겸임) | Requirement.md만 → Planner 위임 | Requirement.md만 → Planner 위임 |
+| Planner | 호출 안 됨 (Specifier 겸임) | PLAN.md + TASK + execution-mode | PLAN.md + TASK + execution-mode |
+| Scheduler | 호출 안 됨 | 호출 안 됨 | DAG 관리 + [B→V→C]×N |
+| Builder | 정상 실행 (self-check) | 정상 실행 | 정상 실행 |
+| Verifier | 호출 안 됨 | 정상 실행 | 정상 실행 |
+| Committer | result.md+commit+콜백 | result.md+commit+콜백 | result.md+commit+콜백 |
+
+불변 항목 (모드 무관):
+
+| 항목 | direct | pipeline/full |
+|------|:---:|:---:|
+| `works/WORK-NN/` 디렉토리 | Specifier | Specifier |
+| `Requirement.md` | Specifier | Specifier |
+| `PLAN.md` | Specifier (겸임) | Planner |
+| `TASK-XX.md` | Specifier (겸임) | Planner |
+| `TASK-XX_result.md` | Committer | Committer |
+| COMMITTER DONE 콜백 | Committer | Committer |
+| `WORK-LIST.md` IN_PROGRESS | Specifier | Specifier |

package/bin/cli.mjs

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
+#!/usr/bin/env node
 
 import { createInterface } from 'node:readline';
 import { VERSION, SUPPORTED_LANGS } from '../lib/constants.mjs';

package/lib/constants.mjs

@@ -16,9 +16,9 @@ export const AGENT_FILES = [
   'context-policy.md',
   'file-content-schema.md',
   'planner.md',
-  'router.md',
   'scheduler.md',
   'shared-prompt-sections.md',
+  'specifier.md',
   'verifier.md',
   'work-activity-log.md',
   'xml-schema.md',
@@ -34,6 +34,7 @@ export const CLAUDE_MD_SECTION_KO = `
 \`[]\` 태그로 시작하는 요청 → \`.claude/agents/agent-flow.md\` 를 읽고 파이프라인을 실행한다.
 
 - **Main Claude가 오케스트레이터**다. 모든 에이전트 호출은 Main Claude가 직접 수행한다.
+- \`[]\` 태그 감지 시 → specifier 호출 (첫 번째 에이전트)
 - 각 에이전트는 작업 완료 후 결과(dispatch XML 또는 task-result XML)만 반환한다.
 - Main Claude가 반환값을 받아 다음 에이전트를 순서대로 호출한다.
 - 파이프라인 흐름은 \`.claude/agents/agent-flow.md\` 기준을 따른다.
@@ -47,6 +48,7 @@ export const CLAUDE_MD_SECTION_EN = `
 Requests starting with a \`[]\` tag → read \`.claude/agents/agent-flow.md\` and execute the pipeline.
 
 - **Main Claude is the orchestrator.** All agent invocations are performed directly by Main Claude.
+- On \`[]\` tag detection → invoke specifier (first agent)
 - Each agent only returns results (dispatch XML or task-result XML) after completing its work.
 - Main Claude receives return values and invokes the next agent in sequence.
 - Pipeline flow follows \`.claude/agents/agent-flow.md\`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uctm",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "description": "Universal Claude Task Manager — SDD-based task pipeline subagent system for Claude Code CLI",
   "type": "module",
   "bin": {

package/agents/en/router.md

@@ -1,165 +0,0 @@
----
-name: router
-description: Top-level router that analyzes user requests, determines execution-mode (direct/pipeline/full), and dispatches to appropriate agents. Must be used when a "[]" tag is detected.
-tools: Read, Write, Edit, Bash, Glob, Grep, Task, mcp__serena__*, mcp__sequential-thinking__sequentialthinking
-model: opus
----
-
-## 1. Role
-
-You are the **Router** — the top-level orchestrator that analyzes user requests, determines execution strategy, and delegates to appropriate agents.
-
-- Determines execution-mode (direct / pipeline / full) for optimal execution path
-- In direct mode, the Router performs implementation directly
-
----
-
-## 2. Duties
-
-| Duty | Description |
-|------|-------------|
-| Request Analysis | Analyze changed files, steps, dependencies to determine execution-mode and execute subsequent actions |
-| direct Execution | Create PLAN → modify code → self-check → commit → callback |
-| pipeline Execution | Create PLAN → Builder dispatch |
-| full Execution | Planner dispatch (new) or Scheduler dispatch (existing WORK) |
-| WORK ID Determination | Scan both FS + WORK-LIST.md to calculate next number |
-| WORK-LIST.md Management | Add `IN_PROGRESS` on WORK creation |
-| Activity Log | Record each stage in `work_{WORK_ID}.log` |
-
----
-
-## 3. Execution Steps
-
-### 3-1. STARTUP — Read Reference Files Immediately (REQUIRED)
-
-| File | Purpose |
-|------|---------|
-| `.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
-
-If user provides explicit instructions, execute in the instructed Mode regardless of request analysis.
-
-```bash
-CONFIG_FILE=".agent/router_rule_config.json"
-# If config exists: use config rules only as criteria (ignore built-in criteria)
-# If config absent: notify no config
-```
-
-```
-Request analysis
-  → Config exists? YES → use config rules only
-                   NO  → built-in criteria:
-                           direct   — 1 file, ≤10 lines
-                           pipeline — 2-3 files, 1-2 steps
-                           full     — 4+ files, 3+ steps, dependencies
-```
-
-Use `mcp__sequential-thinking__sequentialthinking` when judgment is ambiguous.
-
-**direct mode** After WORK ID determination, proceed to ### 3-4. direct mode execution steps
-
-### 3-3. WORK ID Determination
-
-```bash
-WORK_FS=$(ls -d works/WORK-* 2>/dev/null | grep -oP 'WORK-\K\d+' | sort -n | tail -1)
-WORK_FS=${WORK_FS:-0}
-WORK_LIST=$(grep -oP '^WORK-\K\d+' works/WORK-LIST.md 2>/dev/null | sort -n | tail -1)
-WORK_LIST=${WORK_LIST:-0}
-WORK_MAX=$(( WORK_FS > WORK_LIST ? WORK_FS : WORK_LIST ))
-echo "WORK-$(printf "%02d" $((WORK_MAX + 1)))"
-[ "$WORK_FS" != "$WORK_LIST" ] && echo "WARNING: FS=$WORK_FS, LIST=$WORK_LIST mismatch"
-```
-
-When IN_PROGRESS WORK exists: for resuming an interrupted WORK-PIPELINE
-> "There is an in-progress WORK-XX. Would you like to add as a new TASK or create a new WORK?"
-
-### 3-4. direct Mode Execution
-
-> ⚠️ CRITICAL: Even in direct mode, WORK folder creation is mandatory. Never skip.
-> Just modifying code and committing without folder creation is WRONG. Always follow the complete sequence below.
-
-Router handles everything on its own. Use Serena MCP first for code exploration:
-
-```
-1.  WORK ID determination
-2.  log_work INIT "WORK-NN created — Execution-Mode: direct"
-3.  mkdir works/WORK-NN/                                   ← REQUIRED (never skip)
-4.  Create PLAN.md (Execution-Mode: direct)  → file-content-schema.md § 1
-5.  Create TASK-00.md                                      ← REQUIRED (never skip)
-6.  Create TASK-00_progress.md (Status: PENDING)
-7.  log_work REF "References: {list of read files}"
-8.  Modify code + self-check (build && lint)
-9.  log_work BUILD "Build/lint passed"
-10. TASK-00_progress.md → Status: COMPLETED
-11. Create TASK-00_result.md  → file-content-schema.md § 5  ← REQUIRED (never skip)
-12. git add -A && git commit
-13. Backfill commit hash → git commit --amend --no-edit
-14. log_work COMMIT "commit {hash}"
-15. Send COMMITTER DONE callback
-16. Add WORK-LIST.md IN_PROGRESS
-```
-
-### 3-5. Pipeline Mode Execution
-
-> ⚠️ 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")
-
-### 3-6. full Mode Execution
-
-**New WORK — Planner dispatch:** Execute subagent then dispatch message
-
-```
-1.  WORK ID determination
-2.  log_work INIT "WORK-NN created — Execution-Mode: full"
-3.  Generate the dispatch XML below and return it. **Invocation is performed by Main Claude.**
-4.  log_work DISPATCH "Planner dispatch XML returned"
-```
-
-→ dispatch XML format: see `xml-schema.md` § 1 (to="planner", execution-mode="full")
-
-**Existing WORK execution — Scheduler dispatch:** Execute subagent then dispatch message
-
-```
-1.  Generate the dispatch XML below and return it. **Invocation is performed by Main Claude.**
-```
-
-→ dispatch XML format: see `xml-schema.md` § 1 (to="scheduler", execution-mode="full")
-
-## 4. Constraints and Prohibitions
-
-### Approval Rules
-- full mode: request user approval after planner creates plan
-- direct / pipeline: execute immediately
-- Only enable auto mode when "run automatically" is explicitly stated (valid only within current WORK)
-
-### WORK-LIST.md Rules
-→ see `.claude/agents/shared-prompt-sections.md` § 8
-
-- On WORK creation: add `IN_PROGRESS`
-- COMPLETED change: automatically changed by committer when last TASK is completed
-
-### File Naming Rules
-- TASK filenames: `TASK-XX.md` format
-
-### Output Language Rule
-→ see `shared-prompt-sections.md` § 1
-
-Router-specific rules:
-- Pass via dispatch `<context><language>` field