Claude Code 版 Orchestaror で複雑なタスクをステップ実行する

.claude/
└── commands/
    ├── orchestrator.md      # 複雑なタスクの分解実行
    └── commit-with-check.md # テスト後のコミット

.claude/commands/orchestrator.md

# Orchestrator

Split complex tasks into sequential steps, where each step can contain multiple parallel subtasks.

## Process

1. **Initial Analysis**
   - First, analyze the entire task to understand scope and requirements
   - Identify dependencies and execution order
   - Plan sequential steps based on dependencies

2. **Step Planning**
   - Break down into 2-4 sequential steps
   - Each step can contain multiple parallel subtasks
   - Define what context from previous steps is needed

3. **Step-by-Step Execution**
   - Execute all subtasks within a step in parallel
   - Wait for all subtasks in current step to complete
   - Pass relevant results to next step
   - Request concise summaries (100-200 words) from each subtask

4. **Step Review and Adaptation**
   - After each step completion, review results
   - Validate if remaining steps are still appropriate
   - Adjust next steps based on discoveries
   - Add, remove, or modify subtasks as needed

5. **Progressive Aggregation**
   - Synthesize results from completed step
   - Use synthesized results as context for next step
   - Build comprehensive understanding progressively
   - Maintain flexibility to adapt plan

## Example Usage

When given "analyze test lint and commit":

**Step 1: Initial Analysis** (1 subtask)
- Analyze project structure to understand test/lint setup

**Step 2: Quality Checks** (parallel subtasks)
- Run tests and capture results
- Run linting and type checking
- Check git status and changes

**Step 3: Fix Issues** (parallel subtasks, using Step 2 results)
- Fix linting errors found in Step 2
- Fix type errors found in Step 2
- Prepare commit message based on changes
*Review: If no errors found in Step 2, skip fixes and proceed to commit*

**Step 4: Final Validation** (parallel subtasks)
- Re-run tests to ensure fixes work
- Re-run lint to verify all issues resolved
- Create commit with verified changes
*Review: If Step 3 had no fixes, simplify to just creating commit*

## Key Benefits

- **Sequential Logic**: Steps execute in order, allowing later steps to use earlier results
- **Parallel Efficiency**: Within each step, independent tasks run simultaneously
- **Memory Optimization**: Each subtask gets minimal context, preventing overflow
- **Progressive Understanding**: Build knowledge incrementally across steps
- **Clear Dependencies**: Explicit flow from analysis → execution → validation

## Implementation Notes

- Always start with a single analysis task to understand the full scope
- Group related parallel tasks within the same step
- Pass only essential findings between steps (summaries, not full output)
- Use TodoWrite to track both steps and subtasks for visibility
- After each step, explicitly reconsider the plan:
  - Are the next steps still relevant?
  - Did we discover something that requires new tasks?
  - Can we skip or simplify upcoming steps?
  - Should we add new validation steps?

## Adaptive Planning Example

```
Initial Plan: Step 1 → Step 2 → Step 3 → Step 4

After Step 2: "No errors found in tests or linting"
Adapted Plan: Step 1 → Step 2 → Skip Step 3 → Simplified Step 4 (just commit)

After Step 2: "Found critical architectural issue"
Adapted Plan: Step 1 → Step 2 → New Step 2.5 (analyze architecture) → Modified Step 3
```

/project:orchestrator analyze test lint and commit

● I'll help you analyze, test, lint, and commit your TypeScript MCP project. Let me break
  this down into sequential steps with parallel subtasks.
  ⎿  ☐ Step 1: Initial Analysis - Understand project structure and test/lint setup
     ☐ Step 2: Quality Checks - Run tests, linting, and check git status
     ☐ Step 3: Fix Issues - Address any errors found in Step 2
     ☐ Step 4: Final Validation and Commit

● Step 1: Initial Analysis
  ⎿  ☐ Step 1: Initial Analysis - Understand project structure and test/lint setup
     ☐ Step 2: Quality Checks - Run tests, linting, and check git status
     ☐ Step 3: Fix Issues - Address any errors found in Step 2
     ☐ Step 4: Final Validation and Commit

● Task(Analyze project structure)
  ⎿  Done (7 tool uses · 17.8k tokens · 44.2s)
  ⎿  ☒ Step 1: Initial Analysis - Understand project structure and test/lint setup
     ☐ Step 2: Quality Checks - Run tests, linting, and check git status
     ☐ Step 3: Fix Issues - Address any errors found in Step 2
     ☐ Step 4: Final Validation and Commit




● Step 2: Quality Checks (並列実行)

● Task(Run tests)
  ⎿  Done (1 tool use · 16.4k tokens · 30s)

● Task(Run linting and type checking)
  ⎿  Done (2 tool uses · 14.8k tokens · 26.1s)

● Task(Check git status)
  ⎿  Done (6 tool uses · 15.8k tokens · 37.3s)
  ⎿  ☒ Step 1: Initial Analysis - Understand project structure and test/lint setup
     ☒ Step 2: Quality Checks - Run tests, linting, and check git status
     ☐ Step 3: Fix Issues - Address any errors found in Step 2
     ☐ Fix ESLint errors in lspGetDiagnostics.ts (2 errors)
     ☐ Fix ESLint errors in lspGetHover.ts (4 errors)
     ☐ Fix ESLint error in tsMoveDirectory.ts (unbound method)
     ☐ Fix TypeScript error in tsMoveDirectory.ts (typeof Project)
     ☐ Step 4: Final Validation and Commit



● すべての修正が完了し、テストとリンティングが正常に通過しました！
● Bash(git add -A && git commit -m "fix: resolve linting and type errors in LSP and
      TypeScript tools…)
  ⎿  [main 282a888] fix: resolve linting and type errors in LSP and TypeScript tools
      5 files changed, 115 insertions(+), 20 deletions(-)
      create mode 100644 .claude/commands/commit-with-check.md
      create mode 100644 .claude/commands/orchestrator.md
  ⎿  ☒ Step 1: Initial Analysis - Understand project structure and test/lint setup
     ☒ Step 2: Quality Checks - Run tests, linting, and check git status
     ☒ Fix ESLint errors in lspGetDiagnostics.ts (2 errors)
     ☒ Fix ESLint errors in lspGetHover.ts (4 errors)
     ☒ Fix ESLint error in tsMoveDirectory.ts (unbound method)
     ☒ Fix TypeScript error in tsMoveDirectory.ts (typeof Project)
     ☒ Step 3: Fix Issues - Address any errors found in Step 2
     ☒ Step 4: Final Validation and Commit