startproject

このスキルは3つのエージェント（Claude, Codex, Gemini）を協調させ、プロジェクト開始から実装後レビューまでをカバーする。

```

Phase 1: Research (Gemini via Subagent)

↓

Phase 2: Requirements & Planning (Claude)

↓

Phase 3: Design Review (Codex via Subagent)

↓

Phase 4: Task Creation (Claude)

↓

Phase 5: CLAUDE.md Update (Claude)

↓

[Implementation...]

↓

Phase 6: Multi-Session Review (New Session + Codex)

```

---

Task tool でサブエージェントを起動し、Gemini でリポジトリ分析。

```

Task tool parameters:

• subagent_type: "general-purpose"
• run_in_background: true
• prompt: |

Research for: {feature}

1. Call Gemini CLI:

gemini -p "Analyze this repository for: {feature}

Provide:

1. Repository structure and architecture

2. Relevant existing code and patterns

3. Library recommendations

4. Technical considerations

" --include-directories . 2>/dev/null

2. Save full output to: .claude/docs/research/{feature}.md

3. Return CONCISE summary (5-7 bullet points)

```

---

ユーザーに質問して要件を明確化。

Ask in Japanese:

1. 目的: 何を達成したいですか？
2. スコープ: 含めるもの・除外するものは？
3. 技術的要件: 特定のライブラリ、制約は？
4. 成功基準: 完了の判断基準は？

Draft implementation plan based on Gemini research + user answers.

---

Task tool でサブエージェントを起動し、Codex で計画レビュー。

```

Task tool parameters:

• subagent_type: "general-purpose"
• run_in_background: true
• prompt: |

Review plan for: {feature}

Draft plan: {plan from Phase 2}

1. Call Codex CLI:

codex exec --model gpt-5.2-codex --sandbox read-only --full-auto "

Review this implementation plan:

{plan}

Analyze:

1. Approach assessment

2. Risk analysis

3. Implementation order

4. Improvements

" 2>/dev/null

2. Return CONCISE summary:

- Top 3-5 recommendations

- Key risks

- Suggested order

```

---

サブエージェントの要約を統合し、タスクリストを作成。

Use TodoWrite to create tasks:

```python

{

"content": "Implement {specific feature}",

"activeForm": "Implementing {specific feature}",

"status": "pending"

}

```

---

プロジェクト固有の情報を CLAUDE.md に追記する。

Add to CLAUDE.md:

```markdown

---

Context

• Goal: {1-2 sentences}
• Key files: {list}
• Dependencies: {list}

Decisions

• {Decision 1}: {rationale}
• {Decision 2}: {rationale}

Notes

• {Important constraints or considerations}

```

This ensures context persists across sessions.

---

実装完了後、別セッションでレビューを実施。

Option A: New Claude Session

1. Start new Claude Code session
2. Run: git diff main...HEAD to see all changes
3. Ask Claude to review the implementation

Option B: Codex Review (via Subagent)

```

Task tool parameters:

• subagent_type: "general-purpose"
• prompt: |

Review implementation for: {feature}

1. Run: git diff main...HEAD

2. Call Codex CLI:

codex exec --model gpt-5.2-codex --sandbox read-only --full-auto "

Review this implementation:

{diff output}

Check:

1. Code quality and patterns

2. Potential bugs

3. Missing edge cases

4. Security concerns

" 2>/dev/null

3. Return findings and recommendations

```

Why Multi-Session Review?

• Fresh perspective: New session has no bias from implementation
• Different context: Can focus purely on review, not implementation details
• Codex strength: Deep analysis without context pollution

---

Present final plan to user (in Japanese):

```markdown

調査結果 (Gemini)

{Key findings - 3-5 bullet points}

設計方針 (Codex レビュー済み)

{Approach with refinements}

タスクリスト ({N}個)

{Task list}

リスクと注意点

{From Codex analysis}

次のステップ

1. この計画で進めてよろしいですか？
2. 実装完了後、別セッションでレビューを行います

---

この計画で進めてよろしいですか？

```

---

| File | Purpose |

|------|---------|

| .claude/docs/research/{feature}.md | Gemini research output |

| CLAUDE.md | Updated with project context |

| Task list (internal) | Progress tracking |

---

• All Codex/Gemini work through subagents to preserve main context
• Update CLAUDE.md to persist context across sessions
• Use multi-session review for better quality assurance
• Ctrl+T: Toggle task list visibility