oh-my-customcode 0.106.0 → 0.106.1

package/README.md

@@ -13,7 +13,7 @@
 
 **[한국어 문서 (Korean)](./README_ko.md)**
 
-48 agents. 113 skills. 22 rules. One command.
+49 agents. 113 skills. 22 rules. One command.
 
 ```bash
 npm install -g oh-my-customcode && cd your-project && omcustom init
@@ -111,7 +111,7 @@ Agent(arch-documenter):haiku      ┘
 
 ---
 
-### Agents (48)
+### Agents (49)
 
 | Category | Count | Agents |
 |----------|-------|--------|
@@ -126,7 +126,7 @@ Agent(arch-documenter):haiku      ┘
 | QA | 3 | qa-planner, qa-writer, qa-engineer |
 | Security | 1 | sec-codeql |
 | Managers | 6 | mgr-creator, mgr-updater, mgr-supplier, mgr-gitnerd, mgr-sauron, mgr-claude-code-bible |
-| System | 2 | sys-memory-keeper, sys-naggy |
+| System | 3 | sys-memory-keeper, sys-naggy, tracker-checkpoint |
 
 Each agent declares its tools, model, memory scope, and limitations in YAML frontmatter. Tool budgets are enforced per agent type for accuracy.
 
@@ -271,7 +271,7 @@ omcustom serve-stop            # Stop Web UI
 your-project/
 ├── CLAUDE.md                   # Entry point
 ├── .claude/
-│   ├── agents/                 # 48 agent definitions
+│   ├── agents/                 # 49 agent definitions
 │   ├── skills/                 # 113 skill modules
 │   ├── rules/                  # 22 governance rules (R000-R021)
 │   ├── hooks/                  # 15 lifecycle hook scripts

package/dist/cli/index.js

@@ -2334,7 +2334,7 @@ var init_package = __esm(() => {
     workspaces: [
       "packages/*"
     ],
-    version: "0.106.0",
+    version: "0.106.1",
     description: "Batteries-included agent harness for Claude Code",
     type: "module",
     bin: {

package/dist/index.js

@@ -2014,7 +2014,7 @@ var package_default = {
   workspaces: [
     "packages/*"
   ],
-  version: "0.106.0",
+  version: "0.106.1",
   description: "Batteries-included agent harness for Claude Code",
   type: "module",
   bin: {

package/package.json

@@ -3,7 +3,7 @@
   "workspaces": [
     "packages/*"
   ],
-  "version": "0.106.0",
+  "version": "0.106.1",
   "description": "Batteries-included agent harness for Claude Code",
   "type": "module",
   "bin": {

package/templates/.claude/agents/tracker-checkpoint.md

@@ -0,0 +1,72 @@
+---
+name: tracker-checkpoint
+description: Pipeline execution state tracker with checkpoint persistence. Reads/writes /tmp/.claude-pipeline-*-{PPID}.json state files and validates state transitions. Used by dag-orchestration for resume-after-failure and pipeline-guards for quality gate state.
+model: sonnet
+effort: medium
+tools: [Read, Write, Edit, Bash, Glob, Grep]
+memory: project
+skills: [dag-orchestration, pipeline-guards]
+domain: universal
+permissionMode: bypassPermissions
+---
+
+# Tracker Checkpoint Agent
+
+## Purpose
+
+Pipeline 실행 상태를 persistent checkpoint 파일로 관리. `/pipeline resume`, `dag-orchestration`, `pipeline-guards`와 협력하여 실패 후 재개를 가능하게 합니다.
+
+## Capabilities
+
+- Read/write `/tmp/.claude-pipeline-{name}-{PPID}.json` state files
+- Validate state transitions (pending → running → completed | failed)
+- Coordinate with dag-orchestration for step-level checkpointing
+- Coordinate with pipeline-guards for gate-level state snapshots
+- Support `/pipeline resume` by loading last known state
+
+## Workflow
+
+### 1. Pipeline Start (Bootstrap)
+- Create `/tmp/.claude-pipeline-{name}-{PPID}.json` with initial state
+- Record: pipeline name, started timestamp, total steps, current_step=0
+
+### 2. Per-Step Checkpoint
+- After each step: update state file atomically
+- Record: step name, status, duration_ms, output artifacts paths
+- Status transitions: pending → running → completed | failed
+
+### 3. Failure Freeze
+- On step failure: mark status=halted, preserve state for resume
+- Capture: error message, stack trace (if any), partial artifacts
+
+### 4. Resume Coordination
+- On `/pipeline resume`: scan `/tmp/.claude-pipeline-*-{PPID}.json`
+- Return state to orchestrator: name, failed step, error, options (retry/skip/abort)
+- On retry: reset failed step to pending, resume execution
+
+## State File Schema
+
+```json
+{
+  "pipeline": "{name}",
+  "started": "ISO-8601",
+  "status": "running|completed|halted",
+  "current_step": 0,
+  "steps": [
+    {"name": "triage", "status": "completed", "duration_ms": 5000, "artifacts": []},
+    {"name": "plan", "status": "running"}
+  ]
+}
+```
+
+## Integration Points
+
+- `dag-orchestration` skill — step dependency resolution + tracker coordination
+- `pipeline-guards` skill — guard gate state preservation
+- `pipeline` skill — `/pipeline resume` state loader
+
+## Rules Compliance
+
+- R006: Agent artifact; skills (dag-orchestration, pipeline-guards) are source
+- R010: File modifications via Write/Edit (prefer over Bash for .claude/ paths)
+- R017: Structural changes require sauron verification

package/templates/.claude/skills/dag-orchestration/SKILL.md

@@ -57,7 +57,7 @@ nodes:
     depends_on: [test, review, docs]
 
 config:
-  max_parallel: 4          # R009 limit
+  max_parallel: 4          # R009 soft default (hard cap: 5)
   failure_strategy: stop   # stop | skip | retry
   retry_count: 2           # Max retries per node (if strategy=retry)
   timeout_per_node: 300    # Seconds per node (0 = no limit)
@@ -76,7 +76,11 @@ config:
    c. On completion:
       - Success → decrement in-degree of dependents
       - Failure → apply failure_strategy
-   d. Enqueue newly-ready nodes (in-degree = 0)
+   d. Stall check:
+      - If running node duration > 2x average completed duration
+      - AND pending nodes exist with in-degree = 0 (ignoring stalled node's edges)
+      - THEN enqueue those independent nodes immediately (adaptive split)
+   e. Enqueue newly-ready nodes (in-degree = 0)
 6. Verify all nodes executed (detect unreachable nodes)
 ```
 
@@ -84,11 +88,12 @@ config:
 
 | Rule | Detail |
 |------|--------|
-| Max parallel | 4 concurrent nodes (R009) |
+| Max parallel | 5 concurrent nodes max, 4 default (R009) |
 | Agent Teams gate | 3+ parallel nodes → check R018 eligibility |
 | Orchestrator only | DAG scheduling runs in main conversation (R010) |
 | Node execution | Each node = one Task tool call to specified agent |
 | State tracking | `/tmp/.claude-dag-$PPID.json` |
+| Stall detection | Running node > 2x avg completed duration → enqueue independent pending nodes early |
 
 ## Failure Strategies
 
@@ -193,9 +198,47 @@ Execute? [Y/n]
 
 The orchestrator builds the DAG from this inline format and executes using the same algorithm.
 
+## State Management via tracker-checkpoint
+
+Pipeline 상태는 `tracker-checkpoint` 에이전트로 위임됩니다.
+
+### Flow
+
+1. Pipeline 시작 → orchestrator가 tracker-checkpoint 호출 → 초기 state 파일 생성 (`/tmp/.claude-pipeline-{name}-{PPID}.json`)
+2. 각 step 후 → tracker-checkpoint가 state 업데이트 (atomic write)
+3. step 실패 → tracker-checkpoint가 halted 상태로 freeze
+4. `/pipeline resume` → tracker-checkpoint가 state 로드 → orchestrator에 복원 옵션 제공
+
+### Integration
+
+- PPID-scoped state file 경로: `/tmp/.claude-pipeline-{name}-{PPID}.json`
+- step 실행 전후로 tracker-checkpoint delegation
+- resume 시 checkpoint → dag 재빌드 → 미완료 step부터 재개
+
+See `.claude/agents/tracker-checkpoint.md` for agent spec.
+
 ## Limitations
 
 - No cycles allowed (DAG = acyclic)
 - Max 20 nodes per workflow (complexity guard)
 - Nested DAGs not supported (flatten instead)
 - Cross-workflow dependencies not supported
+
+## External References
+
+### Multica — Managed Agent Platform
+
+> Reference: [Multica](https://github.com/multica-ai/multica) — managed agent platform for Claude Code/Codex.
+> Verdict: INTEGRATE (external reference, not internalize)
+
+Multica's task lifecycle pattern (enqueue → claim → start → complete/fail) is a useful reference for DAG node state management:
+
+| Multica State | DAG Equivalent | Notes |
+|---------------|---------------|-------|
+| enqueue | pending | Node waiting for dependencies |
+| claim | ready | Dependencies resolved, ready to execute |
+| start | running | Agent spawned and executing |
+| complete | completed | Node finished successfully |
+| fail | failed | Node execution failed |
+
+Consider this pattern when extending DAG node state tracking or implementing retry logic.

package/templates/.claude/skills/pipeline-guards/SKILL.md

@@ -19,11 +19,13 @@ Defines mandatory safety constraints for all pipeline, workflow, and iterative e
 | Max iterations | 3 | 5 | worker-reviewer-pipeline |
 | Max DAG nodes | 20 | 30 | dag-orchestration |
 | Max parallel agents | 4 | 5 | R009 (all pipelines) |
+| Max parallel steps   | 4        | 4        | pipeline parallel blocks |
 | Timeout per node | 300s | 600s | dag-orchestration nodes |
 | Timeout per pipeline | 900s | 1800s | worker-reviewer-pipeline |
 | Max retry count | 2 | 3 | Failure retry strategies |
 | Max PR improvement items | 20 | 50 | pr-auto-improve |
 | Max auto-improve items | 20 | 50 | omcustom-auto-improve |
+| Max files per agent | 10 | 15 | All agent spawns (advisory) |
 
 ## Enforcement
 
@@ -82,6 +84,23 @@ When guards are triggered, they integrate with existing advisory systems:
 | Timeout approaching (80%) | → warn user, suggest early termination |
 | Hard cap hit | → force stop, report to user |
 
+## Task Granularity Guard
+
+Advisory guard for agent task scope. When a single agent is assigned too many files, it becomes a bottleneck in parallel execution.
+
+| Signal | Default | Action |
+|--------|---------|--------|
+| Files per agent > 10 | Advisory warning | Suggest splitting by layer/domain |
+| Files per agent > 15 | Hard warning | Require explicit user override |
+
+Display:
+```
+[Guard] ⚠ Agent assigned {n} files (> 10) — consider splitting by layer
+[Guard] 🛑 Agent assigned {n} files (> 15) — requires explicit override
+```
+
+This integrates with R009 Adaptive Parallel Splitting: if a stalled agent is detected AND it was assigned > 10 files, the splitting recommendation is stronger.
+
 ## Guard Configuration
 
 Pipelines can override defaults (within hard caps):
@@ -157,6 +176,26 @@ Guard warnings appear inline:
 | omcustom-auto-improve | Auto-improve item count limits |
 | stuck-recovery | Guard triggers feed into stuck detection |
 | model-escalation | Repeated failures trigger escalation advisory |
+| task-decomposition | Subtask file counts validated against granularity guard thresholds |
+
+## Checkpoint Gate Integration
+
+각 guard 통과/실패 시 `tracker-checkpoint` 에이전트로 gate state 기록.
+
+### Flow
+
+1. Guard 진입 → tracker-checkpoint에 gate state: running 기록
+2. Guard 통과 → tracker-checkpoint에 gate state: passed + metrics 기록
+3. Guard 실패 → tracker-checkpoint에 gate state: failed + failure reason freeze
+4. 다음 단계는 checkpoint state 참조하여 재개/중단 판단
+
+### Benefits
+
+- 긴 파이프라인에서 guard 지점마다 복원점 확보
+- 부분 실패 시 직전 guard 지점부터 재시도 가능 (비용 절감)
+- guard metrics 축적으로 품질 추이 관찰 가능
+
+See `.claude/agents/tracker-checkpoint.md` for the tracker spec.
 
 ## Override Policy
 

package/templates/.claude/skills/sdd-dev/SKILL.md

@@ -2,7 +2,7 @@
 name: sdd-dev
 description: Spec-Driven Development workflow — enforces sdd/ folder hierarchy with planning-first gates, current-state artifacts, and completion verification
 scope: core
-version: 1.0.0
+version: 1.1.0
 user-invocable: true
 argument-hint: "[task description or leave empty for guided workflow]"
 ---
@@ -27,7 +27,8 @@ sdd/
 ├── 03_build/        # Current build state, implementation notes
 ├── 04_verify/       # Verification evidence, test results, residual risks
 ├── 05_operate/      # Deployment notes, runbooks (conditional)
-└── 99_toolchain/    # Tool configs, scripts, environment setup
+├── 99_toolchain/    # Tool configs, scripts, environment setup
+└── decisions/       # Decision records for major design choices
 ```
 
 **Key Principle**: These folders are **current-state artifacts**, not history archives. Each file reflects the current state of the work — update in place rather than appending new versions.
@@ -44,7 +45,7 @@ ls sdd/ 2>/dev/null || echo "sdd/ folder not found"
 
 If `sdd/` does not exist:
 1. Inform the user that SDD workflow requires a `sdd/` folder
-2. Offer to create the folder structure: `mkdir -p sdd/{01_planning,02_plan,03_build,04_verify,05_operate,99_toolchain}`
+2. Offer to create the folder structure: `mkdir -p sdd/{01_planning,02_plan,03_build,04_verify,05_operate,99_toolchain,decisions}`
 3. Ask user to confirm before proceeding
 
 If `sdd/` exists, continue to Step 1.
@@ -121,6 +122,7 @@ Artifact to produce or update: `sdd/03_build/current.md`
 
 ## Decisions Made
 - {decision}: {rationale}
+- Write DR for major decisions: sdd/decisions/{YYYY-MM-DD}-{topic}.md (template: templates/decision-record.md)
 
 ## Known Issues
 - {issue}: {planned resolution}
@@ -235,6 +237,18 @@ Final display:
 3. **Checkboxes reflect reality**: Do NOT pre-check criteria. Update checkboxes as work is verified.
 4. **Residual risks are honest**: List known risks even after passing. Hiding risks defeats the purpose.
 
+## Decision Record Template
+
+Major design decisions during Step 3 are recorded in `sdd/decisions/{YYYY-MM-DD}-{topic}.md` using the template at `templates/decision-record.md` (relative to this skill directory).
+
+When to create a Decision Record:
+- Architectural choice between 2+ viable options
+- Trade-off accepted (e.g., complexity for performance)
+- Deferred decision (waiting for data/approval)
+- Superseding a previous decision
+
+See `guides/harness-engineering/` for harness-level decision context that DRs may reference.
+
 ## Integration with Other Skills
 
 | Skill | When to Use Together |

package/templates/.claude/skills/sdd-dev/templates/decision-record.md

@@ -0,0 +1,45 @@
+---
+title: {Decision title}
+date: YYYY-MM-DD
+status: proposed | accepted | superseded | deprecated
+context: guides/harness-engineering/README.md
+decision_makers: [{agent or role}]
+---
+
+# {Decision title}
+
+## Context
+
+{What is the problem and why is a decision needed? Include relevant constraints, goals, and the situation that makes this decision necessary.}
+
+## Options Considered
+
+1. **Option A**: {Description}
+   - Pros: {benefits}
+   - Cons: {drawbacks, trade-offs}
+
+2. **Option B**: {Description}
+   - Pros: {benefits}
+   - Cons: {drawbacks, trade-offs}
+
+3. **Option C** *(if applicable)*: {Description}
+   - Pros: {benefits}
+   - Cons: {drawbacks, trade-offs}
+
+## Decision
+
+**Chosen**: Option {A|B|C}
+
+{Explain the rationale for the choice. Why does this option best satisfy the constraints and goals from the Context section?}
+
+## Consequences
+
+- **Positive**: {What improves as a result of this decision}
+- **Negative**: {Trade-offs and costs accepted}
+- **Risks**: {Future considerations, potential issues to monitor}
+
+## References
+
+- guides/harness-engineering/README.md
+- {related skill or agent, e.g. .claude/skills/action-validator/SKILL.md}
+- {link to issue or PR if applicable}

package/templates/CLAUDE.md

@@ -114,7 +114,7 @@ oh-my-customcode로 구동됩니다.
 project/
 +-- CLAUDE.md                    # 진입점
 +-- .claude/
-|   +-- agents/                  # 서브에이전트 정의 (48 파일)
+|   +-- agents/                  # 서브에이전트 정의 (49 파일)
 |   +-- skills/                  # 스킬 (113 디렉토리)
 |   +-- rules/                   # 전역 규칙 (R000-R022)
 |   +-- hooks/                   # 훅 스크립트 (보안, 검증, HUD)
@@ -173,8 +173,8 @@ oh-my-customcode는 소프트웨어 컴파일과 동일한 구조를 따릅니
 | Infra Engineer | 2 | infra-docker-expert, infra-aws-expert |
 | QA Team | 3 | qa-planner, qa-writer, qa-engineer |
 | Manager | 6 | mgr-creator, mgr-updater, mgr-supplier, mgr-gitnerd, mgr-sauron, mgr-claude-code-bible |
-| System | 3 | sys-memory-keeper, sys-naggy, wiki-curator |
-| **총계** | **48** | |
+| System | 4 | sys-memory-keeper, sys-naggy, tracker-checkpoint, wiki-curator |
+| **총계** | **49** | |
 
 ## Agent Teams (MUST when enabled)
 

package/templates/guides/harness-engineering/README.md

@@ -46,9 +46,9 @@ Deep Insight가 제안하는 4계층 구조는 oh-my-customcode에 이미 구현
 메인 대화 → Agent(mgr-creator, mode: "bypassPermissions") → Write(".claude/agents/new.md", content)
 ```
 
-### Tracker 체크포인트 패턴 (v0.106.0+ 이관)
+### Tracker 체크포인트 패턴
 
-현재 파이프라인 상태 추적은 `/tmp/.claude-pipeline-{PID}.json` 파일과 `.claude/outputs/sessions/{YYYY-MM-DD}/` 아티팩트 규약으로 구현되어 있습니다. 전용 Tracker 에이전트(dag-orchestration / pipeline-guards 통합형)는 `context: fork` cap 확장 이후 후속 릴리즈로 이관합니다.
+현재 파이프라인 상태 추적은 `/tmp/.claude-pipeline-{PID}.json` 파일과 `.claude/outputs/sessions/{YYYY-MM-DD}/` 아티팩트 규약으로 구현되어 있습니다. ✅ 구현 완료 (v0.106.1 via #983 — `.claude/agents/tracker-checkpoint.md`): 전용 Tracker 에이전트(dag-orchestration / pipeline-guards 통합형)가 배포되어 checkpoint persistence, resume-after-failure, gate state 기록을 담당합니다.
 
 ---
 
@@ -185,7 +185,7 @@ opt-in: hard-enforce (filter 모드, --hard-enforce 플래그) — 명시적 사
 
 | 항목 | 이관 이유 | 예상 릴리즈 |
 |------|----------|-----------|
-| **Tracker 체크포인트 에이전트** — dag-orchestration / pipeline-guards 통합형 전용 Tracker | `context: fork` cap(현재 12/12) 확장 필요 | v0.106.0+ |
+| **Tracker 체크포인트 에이전트** — dag-orchestration / pipeline-guards 통합형 전용 Tracker | ✅ 구현 완료 (v0.106.1 via #983 — `.claude/agents/tracker-checkpoint.md`) | — |
 | **hierarchical-agent-topology 스킬** — 4계층 구조를 자동 검증하는 전용 스킬 | fork 스킬 cap 해소 후 추가 | v0.106.0+ |
 | **sdd-dev Harness Decision Record 템플릿** — 하네스 설계 결정을 ADR 형식으로 기록 | sdd-dev 스킬 업데이트와 병행 | v0.107.0+ |
 | **harness-synthesizer 2단계 격리 구현 예시** — Base64 인코딩 + subprocess 격리의 실제 YAML 예시 | 보안 리뷰 후 추가 | v0.107.0+ |

package/templates/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.106.0",
+  "version": "0.106.1",
   "lastUpdated": "2026-04-24T07:30:00.000Z",
   "components": [
     {
@@ -12,7 +12,7 @@
       "name": "agents",
       "path": ".claude/agents",
       "description": "AI agent definitions (flat .md files with prefixes)",
-      "files": 48
+      "files": 49
     },
     {
       "name": "skills",