1. Read meta.yaml to get all sections to be executed
2. Create git worktree for each section
3. Generate tmux session for each worktree
4. Initialize sub-coordinator in each session, passing:
   • section_path (directory path of the section, e.g.

     docs/prds/reddit-bot/sections/auth

     )
   • branch name
   • workspace path
5. Update section status in meta.yaml immediately after generation
6. Monitor completion signals
7. Clean up upon completion/failure

• ✅ Coordinate and generate tmux sessions
• ✅ Manage git worktrees
• ✅ Check progress of each section
• ✅ Call skills concisely
• ❌ Should not think about specific execution plans
• ❌ Should not directly modify business code

创建 worktree

创建 tmux 会话并初始化子协调器

更新 meta.yaml 状态

undefined

1. Verify worktree exists:

   git worktree list | grep {section-id}

2. Verify tmux session is running in worktree:

   -c ../worktrees/{section-id}

3. Never generate Claude for section work in the main repository

检查每个部分的状态

case "$status" in
  completed)
    ((completed_count++))
    echo "✅ $section: COMPLETE"
    ;;
  blocked)
    ((blocked_count++))
    echo "❌ $section: BLOCKED"
    ;;
  in_progress)
    ((in_progress_count++))
    # 检查 tmux 会话是否还在运行
    if ! tmux has-session -t "$section" 2>/dev/null; then
      echo "⚠️ $section: tmux 会话异常退出"
      yq -i ".sections.${section}.status = \"blocked\"" meta.yaml
    else
      # 检查最近输出
      last_output=$(tmux capture-pane -t "$section" -p | tail -20)
      echo "🔄 $section: WORKING"
    fi
    ;;
esac

检查是否所有部分都完成或阻塞

# 自动调用 merge-resolver
if [ $completed_count -gt 0 ]; then
  echo "调用 merge-resolver 处理已完成的部分..."
  # 这里 Claude 会调用 merge-resolver skill
  # 人工只需在 merge-resolver 完成后看到最终报告
else
  echo "没有已完成的部分可以合并"
  echo "所有部分都被阻塞，需要人工干预"
fi

undefined

1. WORKING → Continue monitoring
2. COMPLETE → Update meta.yaml, continue monitoring other sections
3. STUCK → Read error-report.md, decide:
   • Provide additional context via

     tmux send-keys

   • Or escalate to human (mark as blocked)
4. No output for more than 5 minutes → Check if stuck, send prompt:
   bash

   tmux send-keys -t {section-id} "状态更新？" Enter

• If tmux requires any permissions or prompts, generally just agree and point to the correct option
• If external information is needed → Obtain and inject:
  bash

  tmux send-keys -t {section-id} "额外上下文：..." Enter

• All sections are COMPLETE or BLOCKED → Call merge-resolver
• merge-resolver completes → Report final summary to human
• Fatal errors occur in multiple sections → Escalate and provide full report

completed

blocked

1. If there are any blocked sections:
   • Report blocked sections to human
   • Ask: "Proceed with merging completed sections? (y/n)"
   • If no response within 30 seconds, default to YES
2. Call merge-resolver:
   • Pass list of all

     completed

     sections
   • merge-resolver will handle merging, conflict resolution, testing and reporting
3. After merge-resolver returns:
   • If all merges succeed and tests pass → Report success
   • If there are conflicts → Report conflict files and resolution steps
   • If tests fail → Report failure reasons
4. Only return control to human after merge-resolver completes

• ✅ Generate all tmux sessions
• ✅ Monitor all sections until completion
• ✅ Automatically call merge-resolver
• ✅ Wait for merge-resolver to complete
• ✅ Report final results to human

• ❌ Return immediately after generating sessions
• ❌ Return when partially completed
• ❌ Let human manually trigger merging
• ❌ Return while merge-resolver is running

1. Initial PRD input
2. Final execution report (success or conflicts requiring handling)

• completed

  - Section completed, wait for all sections to complete before triggering merge-resolver

• blocked

  - Escalated to human, pause this section

• in_progress

  - Continue monitoring