oh-my-customcode 0.42.1 → 0.42.3

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "oh-my-customcode",
   "workspaces": ["packages/*"],
-  "version": "0.42.1",
+  "version": "0.42.3",
   "description": "Batteries-included agent harness for Claude Code",
   "type": "module",
   "bin": {

package/templates/.claude/rules/MUST-agent-design.md

@@ -203,10 +203,10 @@ Use `context: fork` for skills that orchestrate multi-agent workflows. Cap at **
 | Multi-agent coordination patterns | Single-agent reference skills |
 | Task decomposition/planning | External tool integrations |
 
-Current skills with `context: fork` (11/12 cap):
+Current skills with `context: fork` (9/12 cap):
 - secretary-routing, dev-lead-routing, de-lead-routing, qa-lead-routing
 - dag-orchestration, task-decomposition, worker-reviewer-pipeline, pipeline-guards
-- deep-plan, evaluator-optimizer, sauron-watch
+- deep-plan
 
 ## Naming
 

package/templates/.claude/rules/MUST-agent-teams.md

@@ -13,6 +13,7 @@ Available when `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` or TeamCreate/SendMessag
 | Scenario | Preferred | Reason |
 |----------|-----------|--------|
 | Simple independent subtasks | Agent Tool | Lower cost, no coordination overhead |
+| Sequential-dependency init/scaffolding | Agent Tool | Blocked agents waste tokens polling; single agent faster |
 | Multi-step with shared state | **Agent Teams** | Shared task list, peer messaging |
 | Research requiring discussion | **Agent Teams** | Iterative discovery, synthesis |
 | Cost-sensitive batch ops | Agent Tool | Minimal token overhead |
@@ -46,9 +47,14 @@ Before using Agent tool for 2+ agent tasks, complete this check:
 ║                                                                   ║
 ║  4. Are 2+ issues being fixed in the same release batch?        ║
 ║     YES → prefer Agent Teams (coordination benefit)              ║
-║     NO  → Proceed with Agent tool                                ║
+║     NO  → Check #5                                               ║
+║                                                                   ║
+║  5. Are tasks sequentially dependent (init/scaffold)?            ║
+║     YES → prefer Agent Tool (single agent, no coordination)     ║
+║     NO  → Continue with Agent Teams                              ║
 ║                                                                   ║
 ║  Simple rule: 3+ agents OR review cycle → use Agent Teams        ║
+║  Sequential deps / scaffolding → Agent Tool (single agent)       ║
 ║  2+ issues in same batch → prefer Agent Teams                    ║
 ║  Everything else → Agent tool                                    ║
 ╚══════════════════════════════════════════════════════════════════╝
@@ -189,6 +195,36 @@ When Agent Teams creates a new agent via mgr-creator:
 4. New agent joins team immediately
 5. Team continues with expanded capabilities
 
+## Blocked Agent Behavior
+
+When a team member is blocked by task dependencies:
+
+| Strategy | When | Benefit |
+|----------|------|---------|
+| Deferred spawn | Dependency chain is clear | No wasted tokens; spawn after blocker completes |
+| Silent wait | Agent already spawned, short wait expected | Minimal overhead |
+| Reassign | Agent blocked >2 min with no progress | Reuse agent for unblocked work |
+
+### Prompt Guidelines for Blocked Agents
+
+When spawning agents that may be blocked:
+1. Include explicit instruction: "If your task is blocked, wait silently. Do NOT send periodic status messages."
+2. Set check interval: "Check TaskList once per minute, not continuously."
+3. Prefer deferred spawn when the dependency resolution time is unpredictable.
+
+### Anti-Pattern: Idle Polling
+
+```
+❌ WRONG: Blocked agent sends repeated status messages
+   docker-dev: "Task #1 still pending..."  (×5 messages, wasting tokens)
+
+✓ CORRECT: Deferred spawn after dependency resolves
+   (Task #1 completes) → then spawn docker-dev for Task #3
+
+✓ ALSO CORRECT: Silent wait with infrequent checks
+   docker-dev spawned with: "Wait silently if blocked. Check TaskList once per minute."
+```
+
 ## Lifecycle
 
 ```

package/templates/.claude/skills/deep-plan/SKILL.md

@@ -2,6 +2,7 @@
 name: deep-plan
 description: Research-validated planning — research → plan → verify cycle for high-confidence implementation plans
 scope: core
+context: fork
 version: 1.0.0
 user-invocable: true
 argument-hint: "<topic-or-issue>"

package/templates/CLAUDE.md

@@ -131,11 +131,11 @@ project/
 +-- CLAUDE.md                    # 진입점
 +-- .claude/
 |   +-- agents/                  # 서브에이전트 정의 (44 파일)
-|   +-- skills/                  # 스킬 (74 디렉토리)
+|   +-- skills/                  # 스킬 (75 디렉토리)
 |   +-- rules/                   # 전역 규칙 (R000-R021)
 |   +-- hooks/                   # 훅 스크립트 (보안, 검증, HUD)
 |   +-- contexts/                # 컨텍스트 파일 (ecomode)
-+-- guides/                      # 레퍼런스 문서 (25 토픽)
++-- guides/                      # 레퍼런스 문서 (26 토픽)
 ```
 
 ## 오케스트레이션

package/templates/CLAUDE.md.en

@@ -133,7 +133,7 @@ project/
 |   +-- rules/                   # Global rules (R000-R020)
 |   +-- hooks/                   # Hook scripts (security, validation, HUD)
 |   +-- contexts/                # Context files (ecomode)
-+-- guides/                      # Reference docs (25 topics)
++-- guides/                      # Reference docs (26 topics)
 ```
 
 ## Orchestration

package/templates/CLAUDE.md.ko

@@ -133,7 +133,7 @@ project/
 |   +-- rules/                   # 전역 규칙 (R000-R020)
 |   +-- hooks/                   # 훅 스크립트 (보안, 검증, HUD)
 |   +-- contexts/                # 컨텍스트 파일 (ecomode)
-+-- guides/                      # 레퍼런스 문서 (25 토픽)
++-- guides/                      # 레퍼런스 문서 (26 토픽)
 ```
 
 ## 오케스트레이션

package/templates/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.42.1",
+  "version": "0.42.3",
   "lastUpdated": "2026-03-16T00:00:00.000Z",
   "components": [
     {