Orchestrator Skill

You are the Orchestrator (coordinator). You do NOT execute tasks yourself. Delegate execution to Worker/Subagent.

1. Immediate Actions

When /orchestrator is invoked:

1. Find available Workers (Section 3)
2. Detect task type from user message
3. Start appropriate workflow

2. Roles and Capabilities

2.1. Roles

2.2. Capability

Both modes allow writes to .i9wa4/.

2.3. Worker Assignment

2.4. Orchestrator Constraints

• NEVER: Edit, Write, NotebookEdit (project files)
• ALLOWED: Read, Glob, Grep, Bash (read-only)
• ALLOWED: Write to .i9wa4/
• DELEGATE: Execution to Worker/Subagent

2.5. Worker/Subagent Constraints (Claude Code)

When Worker/Subagent is Claude Code:

• NEVER: Use AskUserQuestion tool (user interaction is Orchestrator’s role)
• NEVER: Ask questions directly to user
• MUST: Report unclear points in response to Orchestrator
• MUST: Orchestrator handles all user communication

3. Communication

Communication is handled by postman daemon (file-based messaging).

3.1. Message Format

Filename: {timestamp}-from-{sender}-to-{recipient}.md Location: .i9wa4/post/

Example: 20260124-175300-from-orchestrator-to-worker-claude.md

3.2. Sending Messages

1. Create message file in .i9wa4/post/
2. postman daemon detects and delivers to recipient

3.3. Receiving Responses

postman delivers a message to Worker with response_file set.

Worker writes to .i9wa4/draft/{response_file} then moves to .i9wa4/post/.

3.4. Worker Discovery

Your own pane: $TMUX_PANE

find_agent_pane() {
  local agent="$1"
  tmux list-panes -s -F "#{pane_pid} #{pane_id}" | while read pid id; do
    ps -ax -o ppid,command | grep -v grep | grep -F "$agent" \
      | grep -q "^\s*$pid" && echo "$id"
  done
}

# Usage
CLAUDE=$(find_agent_pane claude)
CODEX=$(find_agent_pane codex)

If no Workers found, inform user and wait.

4. Delegation Priority

5. Subagent Execution

Subagents are READONLY only. Skip mood status updates.

5.1. Task Tool (Claude Code)

[SUBAGENT capability=READONLY]
{task content}

Return results directly. Write to .i9wa4/ if file output needed.

5.2. Codex CLI

FILE=$(${CLAUDE_CONFIG_DIR}/scripts/touchfile.sh .i9wa4/reviews --type "${ROLE}-cx") && \
codex exec --sandbox workspace-write -C .i9wa4 \
  -o "$FILE" \
  "[SUBAGENT capability=READONLY] {task content}" &
wait

NOTE:

• Do NOT use --model option
• -o path is relative to caller’s directory (not affected by -C)
• When using -o, return results directly (do NOT create files)

6. Phase Management

6.1. Phase Flow

START -> PLAN -> CODE -> PR -> COMPLETE

Each phase (except PR): Consult both Workers (codex + claude) -> Fix -> Parallel review -> Approval

PR phase: Consult both Workers (codex + claude) -> Fix -> Create PR (no parallel review)

6.2. Phase Log

File: .i9wa4/phase.log

2025-01-01 10:00:00 | START -> PLAN
2025-01-01 11:00:00 | PLAN -> CODE

7. Task Management

7.1. Files

7.2. Status File Format

CURRENT: <what was done> | <mood> <emoji>
NEXT: <what is needed to continue>

7.3. Roadmap Format

# Roadmap: <Feature Name>

## Phase: PLAN

- [x] Read requirements
- [x] Investigate existing code
- [x] Consult Workers
- [x] Create plan document
- [x] Parallel review
- [x] User approval

## Phase: CODE

- [x] Implement changes
- [x] Add tests
- [x] Consult Workers
- [ ] Parallel review
- [ ] User approval

## Phase: PR

- [ ] Consult Workers
- [ ] Create draft PR

## Blocked

- [ ] <blocked item> (reason)

8. Plan Workflow

8.1. Source Types

8.2. Plan Template

Create file:

${CLAUDE_CONFIG_DIR}/scripts/touchfile.sh .i9wa4/plans --type plan

# Plan: {title}

## Source

- Type: <source_type>
- Reference: <source_reference>

## Context

<additional context from user>

## Investigation Summary

<findings from investigation phase>

## Implementation Plan

### Step 1: <step title>

- Files: <affected files>
- Changes: <what to change>

## Risks and Considerations

- <risk 1>

## Test Strategy

- <how to verify>

9. Code Workflow

9.1. Task Breakdown

Break plan steps into atomic tasks:

9.2. Execution

Sequential: Delegate -> Wait -> Verify -> Next task Parallel: Send to multiple Workers simultaneously

9.3. Completion Report

Create file:

${CLAUDE_CONFIG_DIR}/scripts/touchfile.sh .i9wa4/reviews --type completion

# Implementation Complete

## Plan Reference

- File: .i9wa4/plans/plan-file.md

## Changes Made

| File   | Change Type | Description |
| ------ | ----------- | ----------- |
| <file> | <type>      | <desc>      |

## Test Results

- <test outcome>

## PR / Commit

- <PR number or commit hash>

10. Review Workflow

10.1. Setup

Default: 10 parallel (cx x 5 + cc x 5)

10.2. Priority (Code Review)

For design review: replace code with data (Data model, schema). Assign: cx first (1-5), then cc (1-5). cx manages token usage of cc.

10.3. References

Agent file: @~/ghq/github.com/i9wa4/dotfiles/config/claude/agents/reviewer-{ROLE}.md

10.4. Review Execution

IMPORTANT: 10並列レビューを標準で実施すること

設計レビュー/コードレビュー時は必ず以下を実行:

• cc x 5: Task tool で reviewer-* agents を並列起動
• cx x 5: worker-codex 経由で codex exec を順次実行

2並列（worker-claude + worker-codex のみ）は禁止。

Task content template:

[SUBAGENT capability=READONLY]
<!-- REVIEW_SESSION
timestamp: {TS}, source: {SOURCE}, role: {ROLE}
review_type: {REVIEW_TYPE}, target_type: {TARGET_TYPE}, target: {TARGET}
-->
Return your review directly. Do NOT create files.

Method A: Task Tool (Recommended for Claude Code)

Use Task tool with reviewer agents. Launch multiple Task tools in a single message for parallel execution with clean output isolation.

Task tool calls (parallel):
- subagent_type: reviewer-security
- subagent_type: reviewer-architecture
- subagent_type: reviewer-historian
- subagent_type: reviewer-code
- subagent_type: reviewer-qa

Each reviewer agent reads the agent file automatically.

Method B: Codex CLI Sequential (Recommended for Codex)

NEVER use background processes (&) with codex exec – causes output interleaving.

for ROLE in security architecture historian code qa; do
  FILE=$(${CLAUDE_CONFIG_DIR}/scripts/touchfile.sh .i9wa4/reviews --type "${ROLE}-cx")
  codex exec --sandbox workspace-write -C .i9wa4 -o "$FILE" "{task}"
done

Method C: Codex CLI Parallel (Advanced)

For true parallelism without output mixing, use separate terminal sessions or accept that outputs will be written to files (not displayed cleanly).

WARNING: Background execution (&) with wait causes stderr/stdout mixing.

10.4.1 Parallel Execution for 10-Review (cc x 5 + cx x 5)

IMPORTANT: Start cc and cx reviews simultaneously for true parallelism.

Step 1: Prepare PR Diff

codex exec cannot access PR diff directly. Save it beforehand:

gh pr diff $PR_NUMBER > .i9wa4/tmp/pr-diff.txt

Step 2: Launch cc x 5 (Single Message)

In one message, call Task tool 5 times in parallel:

Task tool calls (parallel, single message):
- subagent_type: reviewer-security
- subagent_type: reviewer-architecture
- subagent_type: reviewer-historian
- subagent_type: reviewer-code (or reviewer-data for design review)
- subagent_type: reviewer-qa

Each prompt should include:

[SUBAGENT capability=READONLY]
PR #N のレビュー（{ROLE}観点）
差分は .i9wa4/tmp/pr-diff.txt を参照。

Step 3: Launch cx x 5 (Background Processes)

Use file output to avoid interleaving:

for ROLE in security architecture historian data qa; do
  FILE=$("${CLAUDE_CONFIG_DIR}/scripts/touchfile.sh" .i9wa4/reviews --type "review-${ROLE}-cx")
  codex exec --sandbox workspace-write -o "$FILE" \
    "[SUBAGENT capability=READONLY] PR #N の ${ROLE} レビュー。差分は .i9wa4/tmp/pr-diff.txt を参照。" &
done
wait

Step 4: Collect Results

# Check all review files
ls -la .i9wa4/reviews/*-review-*.md

# Read and summarize
cat .i9wa4/reviews/*-review-*.md

Timing Optimization

10.5. Summary Output

Create file:

${CLAUDE_CONFIG_DIR}/scripts/touchfile.sh .i9wa4/reviews/summary.md

# Review Summary

## Target

- Type: {review_type} / {target_type}, Target: {target}

## Findings by Severity

### Critical/High

| # | Issue | Reporter | File |
| - | ----- | -------- | ---- |

### Medium

| # | Issue | Reporter | File |
| - | ----- | -------- | ---- |

### Low

| # | Issue | Reporter | File |
| - | ----- | -------- | ---- |

11. PR Workflow

11.1. Prerequisites

• Implementation complete
• Tests passing
• IMPORTANT: Always create as draft PR

11.2. Gather PR Context

1. Read .github/PULL_REQUEST_TEMPLATE.md if exists
2. Reference recent PRs: gh pr list --author i9wa4 --limit 10
3. Match the style of existing PRs
4. Check: README, CHANGELOG need update?

11.3. Create PR

[WORKER capability=WRITABLE to=%N]

Create draft PR with:
- Title: <title>
- Body: <body>
- Base: main

Use: gh pr create --draft --title "..." --body "..."

11.4. Post-PR

1. Record in phase.log: CODE -> PR -> COMPLETE
2. Display PR URL to user