┌─────────────────────────────────────────────────────────────┐
│  開發者工作流                                                  │
├─────────────────────────────────────────────────────────────┤
│                                                               │
│  [VS Code IDE]                    [Terminal / CLI]           │
│   ├── GitHub Copilot              ├── Claude Code + OMC      │
│   │   ├── 程式碼補完              │   ├── 架構規劃（ralplan）  │
│   │   ├── Inline Chat             │   ├── 多檔重構（ultrawork）│
│   │   └── PR Review               │   ├── 自動開發（autopilot）│
│   │                               │   ├── 安全審查            │
│   └── Agent Mode                  │   └── 持久執行（ralph）    │
│       └── 複雜任務 → 也可呼叫 OMC │                           │
└─────────────────────────────────────────────────────────────┘

User Input --> Hooks (事件偵測) --> Skills (行為注入)
           --> Agents (任務執行) --> State (進度追蹤)

┌────────────────────────────────────────────────────────────────────┐
│                    Team Mode 五階段管線                              │
│                                                                      │
│  team-plan → team-prd → team-exec → team-verify → team-fix (loop) │
│                                                                      │
│  規劃階段     需求文件     執行階段     驗證階段      修復迴圈       │
└────────────────────────────────────────────────────────────────────┘

explore --> analyst --> planner --> critic --> executor --> verifier
(探索)     (分析)     (排序)     (審查)     (實作)     (確認)

// Agent 委派範例
Task(
  subagent_type = "oh-my-claudecode:executor",
  model = "sonnet",
  prompt = "Implement feature..."
)

# GitHub Actions 整合範例
name: OMC Agent Review
on: [pull_request]
jobs:
  review:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Setup Claude Code
        run: |
          # 安裝 Claude Code CLI 並透過 plugin 方式安裝 OMC
          claude plugin marketplace add https://github.com/Yeachan-Heo/oh-my-claudecode
          claude plugin install oh-my-claudecode
      - name: Run Security Review
        run: |
          omc ask claude --agent-prompt security-reviewer \
            --prompt "review the changes in this PR for security issues"

# PR 架構審查（透過 Codex）
omc ask codex "review this PR for architecture risks"

# PR 安全審查（透過 Claude）
omc ask claude --agent-prompt security-reviewer --prompt "review auth changes"

# PR UI 審查（透過 Gemini）
omc ask gemini --prompt "review UI component accessibility"

# 設定 Discord 通知
omc config-stop-callback discord --enable \
  --webhook <webhook_url> \
  --tag-list "@here,123456789012345678"

# 設定 Telegram 通知
omc config-stop-callback telegram --enable \
  --token <bot_token> \
  --chat <chat_id> \
  --tag-list "@alice,bob"

# 設定 Slack 通知
omc config-stop-callback slack --enable \
  --webhook <webhook_url> \
  --tag-list "<!here>,<@U1234567890>"

# Step 1：新增 marketplace
/plugin marketplace add https://github.com/Yeachan-Heo/oh-my-claudecode

# Step 2：安裝 plugin
/plugin install oh-my-claudecode

# 使用 omc shim 啟動（推薦）
omc --plugin-dir /path/to/oh-my-claudecode

# 搭配 setup 啟用 dev 模式
omc setup --plugin-dir-mode

# ⚠️ 已棄用 — 不建議使用
npm i -g oh-my-claude-sisyphus@latest

# 在 Claude Code 會話中
/setup
# 或
/omc-setup

# 從終端機
omc setup

/oh-my-claudecode:omc-setup --local

/oh-my-claudecode:omc-setup

{
  "env": {
    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
  }
}

# 在 Claude Code 會話中執行診斷
/oh-my-claudecode:omc-doctor

# 若使用本地 checkout，可指定 plugin 路徑
omc doctor --plugin-dir /path/to/oh-my-claudecode

# 也支援 conflicts 子命令
omc doctor conflicts --plugin-dir /path/to/oh-my-claudecode

./.claude/CLAUDE.md  (專案)  →  覆蓋  →  ~/.claude/CLAUDE.md  (全域)

---
name: architect
description: Your custom description
tools: Read, Grep, Glob, Bash, Edit
model: opus  # 或 sonnet, haiku
# effort: high（可選，預設繼承父 session）
---
Your custom system prompt here...

┌──────────────────────────────────────────────────────────┐
│              模型路由決策樹                                 │
├──────────────────────────────────────────────────────────┤
│                                                            │
│  任務類型判斷                                               │
│  ├── 簡單查詢/文件撰寫 → Haiku（低成本）                    │
│  ├── 程式碼實作/除錯/測試 → Sonnet（平衡）                  │
│  └── 架構設計/策略分析/審查 → Opus（高品質）                │
│                                                            │
│  實際節省：30-50% Token 費用                                │
└──────────────────────────────────────────────────────────┘

// .claude/omc.jsonc（專案）或 ~/.config/claude-omc/config.jsonc（使用者）
{
  "companyContext": {
    "tool": "mcp__vendor__get_company_context",
    "onError": "warn"
  }
}

{
  "mcpServers": {
    "remoteOmc": {
      "url": "https://lab.example.com/mcp",
      "timeout": 30
    }
  }
}

---
name: Fix Proxy Crash
description: aiohttp proxy crashes on ClientDisconnectedError
triggers: ["proxy", "aiohttp", "disconnected"]
source: extracted
---
Wrap handler at server.py:42 in try/except ClientDisconnectedError...

pipeline: [deep-interview, omc-plan, autopilot]
next-skill: omc-plan
next-skill-args: --consensus --direct
handoff: .omc/specs/deep-interview-{slug}.md

# 快速開始 — 在 Claude Code 會話中
/autopilot "build a REST API for managing tasks"

# 自然語言方式（無需斜線指令）
autopilot: build a REST API for managing tasks

# 預設使用 critic agent 做驗證
/ralph "implement user authentication"

# 指定 architect 作為批評者（適合架構級任務）
/ralph --critic=architect "refactor the entire data access layer"

# 標準共識規劃
/ralplan "design the new microservice architecture"

# 深思模式（高風險決策）
/ralplan --deliberate "plan database migration from Oracle to PostgreSQL"

/deep-interview "I want to build a task management app"

# 啟動 deep-dive 追蹤
/deep-dive "why does the payment service timeout under load?"

/oh-my-claudecode:autoresearch "investigate performance bottleneck in the API"

# 使用 Autopilot 全流程生成 React 前端
/autopilot "build a React dashboard with:
- user authentication (OAuth2)
- role-based access control
- real-time notifications
- responsive design with Tailwind CSS"

# 使用 Designer Agent 處理 UI/UX
/team 2:executor "implement the frontend components"

# 使用 Team 模式開發 Spring Boot 後端
/team 3:executor "build a Spring Boot 3.x REST API with:
- Clean Architecture (domain/application/infrastructure layers)
- JPA entities for User, Role, Permission
- JWT authentication filter
- Global exception handler
- OpenAPI documentation"

# 使用 Architect Agent 進行 API 設計
/ralplan "design RESTful API for an e-commerce system with:
- product catalog CRUD
- shopping cart management
- order processing workflow
- payment integration interface"

# 使用 Analyst + Architect 協作
/deep-interview "I need a database schema for a multi-tenant SaaS platform"
# 釐清需求後
/autopilot "implement the database schema with Flyway migrations"

# Step 1：使用 Deep Interview 理解系統
/deep-interview "I need to reverse engineer a 10-year-old Java monolith
with no documentation. The system handles banking transactions."

# Step 2：使用 Explore Agent 探索程式碼
/ultrawork "analyze the codebase structure:
1. Map all packages and their dependencies
2. Identify entry points and main flows
3. Document all external integrations
4. List all database tables and relationships"

# 使用 Architect Agent 分析架構
/team 3:executor "reverse engineer this legacy system:
1. architect: analyze the overall architecture pattern
2. explore: map module dependencies
3. document-specialist: generate architecture documentation"

# 使用 Deepinit 生成階層式文件
/oh-my-claudecode:deepinit

# 使用 Writer Agent 產生詳細文件
/autopilot "generate comprehensive documentation for this codebase:
- System overview and architecture
- Module-by-module descriptions
- API endpoint documentation
- Database schema documentation
- Deployment guide"

# 使用 Architect + Critic 協作規劃重構
/ralplan "plan the modernization of this legacy system:
- Identify technical debt hot spots
- Propose microservice boundaries
- Design migration strategy (strangler fig pattern)
- Estimate effort for each phase"

# Step 1：使用 Analyst 分析影響
/deep-interview "upgrade Spring Boot from 2.7 to 3.2:
- Current dependencies and their compatibility
- Breaking changes analysis
- Migration path"

# Step 2：使用 Team 執行升級
/team 3:executor "execute Spring Boot upgrade:
1. Update pom.xml / build.gradle dependencies
2. Fix javax → jakarta namespace migration
3. Update deprecated APIs
4. Run and fix all tests
5. Verify application startup"

# Vue 2 → Vue 3 升級
/ralph "upgrade Vue 2 to Vue 3:
1. Analyze all components for breaking changes
2. Update Options API to Composition API where beneficial
3. Migrate Vuex to Pinia
4. Update Vue Router configuration
5. Fix template syntax changes
6. Run all tests"

# 使用 CCG 進行多角度依賴分析
/ccg "analyze all project dependencies:
- Codex: identify security vulnerabilities and outdated packages
- Gemini: suggest alternative libraries for deprecated ones
- Claude: create a prioritized upgrade plan"

┌──────────────────────────────────────────────────────────┐
│  保證層（Guarantee Layer）— 可選                           │
│  ralph: "在驗證完成前不可停止"                              │
└──────────────────────────────────────────────────────────┘
                          │
                          ▼
┌──────────────────────────────────────────────────────────┐
│  增強層（Enhancement Layer）— 0~N 個技能                   │
│  ultrawork (平行) | git-master (提交) | frontend-ui-ux    │
└──────────────────────────────────────────────────────────┘
                          │
                          ▼
┌──────────────────────────────────────────────────────────┐
│  執行層（Execution Layer）— 主要技能                       │
│  default (建構) | orchestrate (協調) | planner (規劃)     │
└──────────────────────────────────────────────────────────┘

# 範例：ultrawork + default + git-master
ultrawork: refactor API with proper commits
# 啟用技能：ultrawork（平行執行）+ default（建構）+ git-master（原子提交）

# 啟動 Team 模式
/team 3:executor "implement fullstack todo app"

# 管線自動執行：
# 1. team-plan：規劃任務
# 2. team-prd：產生需求文件
# 3. team-exec：執行實作
# 4. team-verify：驗證完成
# 5. team-fix：修復問題（迴圈）

# 生成 Codex workers 進行安全審查
omc team 2:codex "review auth module for security issues"

# 生成 Gemini workers 進行 UI 設計
omc team 2:gemini "redesign UI components for accessibility"

# 生成 Claude workers 實作功能
omc team 1:claude "implement the payment flow"

# 檢查 Team 狀態
omc team status auth-review

# 關閉 Team
omc team shutdown auth-review

# 透過 API 領取任務（進階）
omc team api claim-task --input '{"team_name":"auth-review","task_id":"1","worker":"worker-1"}' --json

# 混合 Codex + Gemini + Claude 分析
/ccg Review this PR — architecture (Codex) and UI components (Gemini)

# 全面程式碼審查
/oh-my-claudecode:ask claude --agent-prompt code-reviewer \
  "review the changes in src/auth/ for:
  - code quality and maintainability
  - API contract backward compatibility
  - error handling completeness
  - test coverage adequacy"

# 安全審查
/oh-my-claudecode:ask claude --agent-prompt security-reviewer \
  "review this codebase for:
  - OWASP Top 10 vulnerabilities
  - authentication/authorization issues
  - input validation gaps
  - sensitive data exposure
  - dependency vulnerabilities"

# 快速安全掃描（使用 haiku 降低成本）
/oh-my-claudecode:ask claude --agent-prompt security-reviewer-low \
  "quick security scan of the auth module"

.omc/self-improve/topics/
├── performance/         # 效能最佳化主題
│   ├── v1.md           # 第一代改進
│   ├── v2.md           # 第二代改進（錦標賽勝出）
│   └── tournament.json # 評估記錄
├── security/
│   └── ...
└── readability/
    └── ...

# 針對特定主題啟動自主改進
/self-improve "optimize database query performance"

# 比較截圖與設計稿
/visual-verdict "compare current login page with design mockup"

# 初始化寫作專案記憶
/writer-memory "technical documentation for our API"

# 管理技能
/skill list              # 列出所有技能
/skill add               # 新增技能
/skill remove <name>     # 移除技能
/skill edit <name>       # 編輯技能
/skill search <query>    # 搜尋技能

# 使用 Learner 從會話中提取可重用模式
/learner

# .omc/skills/fix-proxy-crash.md
---
name: Fix Proxy Crash
description: aiohttp proxy crashes on ClientDisconnectedError
triggers: ["proxy", "aiohttp", "disconnected"]
source: extracted
---
Wrap handler at server.py:42 in try/except ClientDisconnectedError...

~/.omc/skills/                  # 全域（跨專案）
├── company-coding-standards.md  # 公司程式碼規範
├── security-patterns.md         # 安全模式
├── db-optimization.md           # 資料庫最佳化
└── ci-cd-patterns.md            # CI/CD 模式

.omc/skills/                     # 專案層級
├── project-architecture.md      # 專案架構模式
├── api-conventions.md           # API 設計慣例
├── test-patterns.md             # 測試模式
└── deployment-checklist.md      # 部署清單

# 使用 Wiki skill 建立持久的 Markdown 知識庫
/oh-my-claudecode:wiki

<!-- 保留 7 天 -->
<remember>API endpoint changed to /v2</remember>

<!-- 永久保留 -->
<remember priority>Never access production DB directly</remember>

# 使用不同 Provider 進行交叉驗證
omc ask claude "review this migration plan"
omc ask codex --prompt "identify architecture risks"
omc ask gemini --prompt "propose UI polish ideas"

# 啟用最大平行度
/ultrawork "fix all TypeScript errors in the project"

# 3 個 Executor Agent 同時工作
/team 3:executor "implement all CRUD endpoints"

# 啟用/停用平行執行
export OMC_PARALLEL_EXECUTION=true

# 設定 HUD 預設值
/oh-my-claudecode:hud setup

{
  "omcHud": {
    "preset": "focused",
    "elements": {
      "cwd": true,
      "gitRepo": true,
      "gitBranch": true,
      "showTokens": true,
      "contextBar": true,
      "agents": true,
      "todos": true,
      "ralph": true,
      "autopilot": true
    }
  }
}

export OMC_SECURITY=strict

{
  "security": {
    "restrictToolPaths": true,
    "pythonSandbox": true,
    "disableRemoteMcp": true,
    "disableExternalLLM": true,
    "disableAutoUpdate": true,
    "hardMaxIterations": 200
  }
}

# 全面安全審查
/oh-my-claudecode:ask claude --agent-prompt security-reviewer \
  "perform a comprehensive security review:
  1. OWASP Top 10 analysis
  2. Authentication and authorization review
  3. Input validation and output encoding
  4. Cryptographic implementation review
  5. Session management analysis
  6. Error handling and logging review"

# 快速安全掃描
/oh-my-claudecode:ask claude --agent-prompt security-reviewer-low \
  "quick security scan of recent changes"

# 在 Team 模式中加入安全檢查階段
/team 3:executor "implement feature with security gates:
1. executor: implement the feature
2. security-reviewer: scan for vulnerabilities
3. test-engineer: write security test cases"

# 使用 Architect + Security Reviewer 進行威脅建模
/ralplan "perform threat modeling for the authentication system:
1. Identify trust boundaries
2. Map data flows
3. Identify threats (STRIDE)
4. Assess risks
5. Propose mitigations"

# 環境設定
export OMC_SECURITY=strict

// .claude/omc.jsonc
{
  "security": {
    "restrictToolPaths": true,
    "pythonSandbox": true,
    "disableRemoteMcp": true,
    "disableExternalLLM": true,
    "disableAutoUpdate": true,
    "hardMaxIterations": 200
  }
}

# 渲染 HUD 狀態列
omc hud

# 檢查 Team 工作狀態
omc team status <team-name>

# 檢視最近的 replay log
tail -20 .omc/state/agent-replay-*.jsonl

# 列出 session 摘要
ls .omc/sessions/*.json

# 搜尋歷史 session
omc session search "team leader stale"
omc session search notify-hook --since 7d
omc session search provider-routing --project all --json

# 執行全面診斷
/oh-my-claudecode:omc-doctor

# 停用所有 OMC Hook
export DISABLE_OMC=1

# 跳過特定 Hook
export OMC_SKIP_HOOKS="keyword-detector,persistent-mode"

# 檢查速率限制狀態
omc wait

# 啟用自動恢復 daemon
omc wait --start

# 停用 daemon
omc wait --stop

# 基本搜尋
omc session search "team leader stale"

# 時間範圍搜尋
omc session search notify-hook --since 7d

# 跨專案搜尋（JSON 輸出）
omc session search provider-routing --project all --json

.omc/
├── state/                    # 每模式狀態檔
│   ├── autopilot-state.json  # autopilot 進度
│   ├── ralph-state.json      # ralph 迴圈狀態
│   ├── team/                 # team 任務狀態
│   ├── interop/              # 跨工具任務/訊息信封
│   └── sessions/             # 每 session 狀態
│       └── {sessionId}/
├── notepad.md                # 壓縮抗性備忘錄
├── project-memory.json       # 專案知識庫
├── plans/                    # 執行計畫
├── notepads/                 # 每計畫知識擷取
│   └── {plan-name}/
│       ├── learnings.md
│       ├── decisions.md
│       ├── issues.md
│       └── problems.md
├── prompts/                  # 持久化 prompt/response artifacts
├── skills/                   # 專案層級 Skills
├── sessions/                 # session 摘要
├── artifacts/                # Ask 等產出的 artifacts
│   └── ask/
├── autopilot/                # autopilot artifacts
│   └── spec.md
├── research/                 # 研究結果
└── logs/                     # 執行日誌

# 在 shell profile 中設定（~/.bashrc, ~/.zshrc）
export OMC_STATE_DIR="$HOME/.claude/omc"

{
  "codeSimplifier": {
    "enabled": true,
    "extensions": [".ts", ".tsx", ".js", ".jsx", ".py", ".go", ".rs"],
    "maxFiles": 10
  }
}

外部事件 (GitHub/Slack/Cron/API)
        ↓
  OpenClaw Gateway
        ↓
  Event → Task 轉換
        ↓
  OMC Team / Ralph / Autopilot
        ↓
  結果回報（Webhook / Notification）

// .omc/openclaw.jsonc
{
  "enabled": true,
  "gateway": {
    "port": 8090,
    "auth": "bearer-token"   // 或 "webhook-secret"
  },
  "routes": [
    {
      "event": "github.pull_request.opened",
      "action": "team",
      "config": {
        "workers": "1:code-reviewer",
        "taskTemplate": "Review PR #{payload.number}: {payload.title}"
      }
    },
    {
      "event": "github.issues.assigned",
      "action": "ralph",
      "config": {
        "taskTemplate": "Implement issue #{payload.number}: {payload.title}"
      }
    },
    {
      "event": "cron.daily.security",
      "action": "ask",
      "config": {
        "agentPrompt": "security-reviewer",
        "task": "Run daily security audit on recent changes"
      }
    }
  ],
  "notifications": {
    "onComplete": ["github-comment", "slack"],
    "onFailure": ["slack", "email"]
  }
}

# 在 Claude Code 會話中
# Step 1：更新 marketplace clone
/plugin marketplace update omc

# Step 2：重新執行 setup 刷新設定
/setup

# ⚠️ 已棄用 — 不建議使用
npm i -g oh-my-claude-sisyphus@latest

# 如果是本地 checkout 或 git worktree
cd /path/to/oh-my-claudecode
git pull origin main

# 重新執行 setup
omc setup

# 升級後問題排除
/omc-doctor

./.claude/CLAUDE.md  (專案)  →  覆蓋  →  ~/.claude/CLAUDE.md  (全域)

# 使用 Claude Code plugin 管理
/plugin uninstall oh-my-claudecode@oh-my-claudecode

# 或手動移除
rm ~/.claude/agents/{architect,document-specialist,explore,designer,writer,vision,critic,analyst,executor,qa-tester}.md
rm ~/.claude/commands/{analyze,autopilot,deepsearch,plan,review,ultrawork}.md

# 遷移步驟
/plugin marketplace add https://github.com/Yeachan-Heo/oh-my-claudecode
/plugin install oh-my-claudecode
# 然後說 "setup omc"

# ❌ 舊方式（已棄用）
mcp__team__omc_run_team_start(...)

# ✅ 新方式（CLI-first）
omc team 2:codex "review auth flow"
omc team status review-auth-flow
omc team shutdown review-auth-flow --force

<repo>/.omc/team/<team-name>/worktrees/<worker-name>   # Worker worktree
<repo>/.omc/state/team/<team-name>                      # 狀態/協調根

# 好的 Prompt 範例
/team 3:executor "implement user authentication:
1. JWT token generation and validation
2. Refresh token mechanism
3. Password hashing with bcrypt
4. Rate limiting for login attempts
5. Session management with Redis

Technical constraints:
- Spring Boot 3.2 with Spring Security 6
- PostgreSQL for user storage
- Redis for session cache
- Must pass OWASP authentication checks"

/deep-interview "I want to build an enterprise task management system with:
- Multi-tenant support
- Role-based access control (Admin/Manager/Developer)
- Task lifecycle (Created → In Progress → Review → Done)
- Real-time notifications
- REST API + React frontend
- PostgreSQL database"

/ralplan "design the system architecture:
- Clean Architecture with domain-driven design
- Spring Boot 3.2 backend
- React 18 + TypeScript frontend
- PostgreSQL + Redis
- JWT authentication
- WebSocket for real-time updates"

# 使用 Team 模式平行開發
/team 3:executor "implement the task management system:
Agent 1: Backend API (Spring Boot + JPA + Security)
Agent 2: Frontend Components (React + TypeScript + Tailwind)
Agent 3: Database Schema + Migrations (Flyway)"

# 安全審查
/oh-my-claudecode:ask claude --agent-prompt security-reviewer \
  "review the entire codebase for security vulnerabilities"

# 程式碼審查
/oh-my-claudecode:ask claude --agent-prompt code-reviewer \
  "comprehensive code review focusing on:
  - API contract quality
  - Error handling
  - Test coverage
  - Performance concerns"

/ralph "ensure all components are working:
1. All unit tests pass
2. Integration tests pass
3. API documentation is complete
4. Frontend builds without errors
5. Database migrations run successfully"

/ultrawork "analyze this legacy banking system:
1. Map the package structure and dependencies
2. Identify all entry points (servlets, schedulers, message listeners)
3. Document all database tables and their relationships
4. List all external integrations (SWIFT, payment gateways, etc.)
5. Identify design patterns currently in use"

/team 3:executor "reverse engineer the architecture:
Agent 1 (architect): Draw the system architecture diagram
Agent 2 (explore): Map all inter-module dependencies
Agent 3 (document-specialist): Generate module documentation"

/ralplan "assess migration risks:
1. Identify tightly coupled modules
2. Find undocumented business rules in code
3. Assess test coverage gaps
4. List deprecated dependencies with CVEs
5. Propose strangler fig migration boundaries"

/ralph "refactor the authentication module:
1. Extract auth logic from monolith
2. Implement as standalone microservice
3. Add comprehensive test coverage
4. Ensure backward compatibility
5. Document API contracts"

/deep-interview "upgrade Spring Boot from 2.7 to 3.2:
Current state:
- 200+ Java files
- 50+ Spring Security configurations
- 30+ JPA entities
- Custom servlet filters
- Third-party library integrations"

/ccg "analyze all dependencies for Spring Boot 3.2 compatibility:
- Codex: identify incompatible libraries and suggest alternatives
- Gemini: check for deprecated APIs and migration guides
- Claude: create a prioritized upgrade plan"

/ralph "execute Spring Boot upgrade step by step:
1. Update parent POM to Spring Boot 3.2
2. Migrate javax.* → jakarta.* imports
3. Update Spring Security configuration to new API
4. Fix deprecated method calls
5. Update third-party libraries
6. Run all tests and fix failures
7. Verify application startup
8. Performance regression test"

/ultrawork "verify the upgrade:
1. All unit tests pass
2. All integration tests pass
3. Application starts successfully
4. API endpoints respond correctly
5. Security configurations work
6. Database operations function properly
7. No compilation warnings"

┌─────────────────────────────────────────────────────────────┐
│                    OMC 輔助開發流程                           │
├─────────────────────────────────────────────────────────────┤
│                                                               │
│  1. 需求理解      → /deep-interview "需求描述"               │
│  2. 架構設計      → /ralplan "設計需求"                       │
│  3. 程式碼實作    → /team N:executor "實作任務"               │
│  4. 程式碼審查    → code-reviewer + security-reviewer         │
│  5. 測試          → test-engineer + qa-tester                  │
│  6. 文件          → writer + document-specialist               │
│  7. Git 操作      → git-master                                │
│                                                               │
└─────────────────────────────────────────────────────────────┘

/autopilot "implement [FEATURE_NAME]:

Requirements:
1. [具體需求 1]
2. [具體需求 2]
3. [具體需求 3]

Technical constraints:
- [技術框架/版本]
- [資料庫/快取]
- [安全要求]

Acceptance criteria:
- [驗收標準 1]
- [驗收標準 2]
- All tests pass
- No security vulnerabilities"

/oh-my-claudecode:ask claude --agent-prompt code-reviewer \
  "review [TARGET] for:
  1. Code quality and maintainability
  2. API contract correctness
  3. Error handling completeness
  4. Test coverage adequacy
  5. Performance concerns
  6. Security best practices"

/ultrawork "analyze [LEGACY_SYSTEM]:
1. Map module structure and dependencies
2. Identify all entry points and data flows
3. Document business rules embedded in code
4. List all external integrations
5. Assess technical debt and risk areas
6. Generate architecture documentation"

/ralph "upgrade [FRAMEWORK] from [OLD_VERSION] to [NEW_VERSION]:
1. Update dependency definitions
2. Fix breaking API changes
3. Migrate deprecated features
4. Update configuration files
5. Run and fix all tests
6. Verify application startup
7. Performance regression check"

/oh-my-claudecode:ask claude --agent-prompt security-reviewer \
  "security review for [TARGET]:
  1. OWASP Top 10 analysis
  2. Authentication/authorization review
  3. Input validation and encoding
  4. Cryptographic implementation
  5. Session management
  6. Dependency vulnerabilities
  7. Configuration security"