🚀 OMX + Superpowers + Gstack Complete Guide

Version: v1.0 | Updated: 2026-04-30

Complete guide to the three-layer architecture of Claude Code, making your AI assistant more powerful!

📐 1. Three-Layer Architecture Overview

┌──────────────────────────────────────────────────────────────┐
│                    🎯 OMX Orchestration Layer                  │
│            Unified Entry · Task Distribution · State Persistence              │
└──────────────────────────────────────────────────────────────┘
                              ↓
    ┌─────────────────┬─────────────────┬─────────────────┐
    │                 │                 │                 │
    ▼                 ▼                 ▼                 ▼
┌─────────┐     ┌─────────┐     ┌─────────┐     ┌─────────┐
│🧠 Thinking Layer│     │⚡ Execution Layer│     │🌐 Interaction Layer│     │🛡️ Guard Layer│
│Super-   │     │OMX Team │     │Gstack   │     │Guard    │
│powers   │     │         │     │         │     │         │
└─────────┘     └─────────┘     └─────────┘     └─────────┘

🎯 Division of Responsibilities Across Layers

💡 Division Principle: Superpowers thinks → OMX orchestrates → Gstack executes

🎯 2. Task Routing Decision Flow

                    User Task Input
                         ↓
                ┌────────────────┐
                │  🤔 Assess Task Size │
                └────────────────┘
                         ↓
    ┌────────────────────┼────────────────────┐
    │                    │                    │
    ▼                    ▼                    ▼
┌────────┐         ┌────────┐         ┌────────┐
│🟢 Lightweight │         │🟡 Medium │         │🔴 Large │
│ Task  │         │ Task  │         │ Task  │
└────────┘         └────────┘         └────────┘
    │                    │                    │
    │                    │                    │
    ▼                    ▼                    ▼
Implement Directly   Brainstorm + Plan   Full Closed Loop
    │                    │                    │
    ▼                    ▼                    ▼
 /browse            /qa Verify           omx team

📊 Task Type Quick Reference

🔄 3. Full Closed Loop Process

┌──────────────────────────────────────────────────────────────┐
│                                                              │
│  ┌─────┐   ┌─────┐   ┌─────┐   ┌─────┐   ┌─────┐   ┌─────┐  │
│  │🎨Design│→ │📋Review│→ │🔒Isolate│→ │⚡Parallel│→ │✅Verify│→ │🚀Deploy│  │
│  └─────┘   └─────┘   └─────┘   └─────┘   └─────┘   └─────┘  │
│                                                              │
│  brainstorm  plan-ceo   worktrees  omx team    qa      ship  │
│  writing-    plan-eng     TDD                  verify  deploy│
│  plans       plan-design                                  canary│
│                                                              │
└──────────────────────────────────────────────────────────────┘

🎬 Detailed Phase Descriptions

🤖 4. OMX Team Mode Details

4.1 🎭 Team Workflow

omx team N:agent "task"

┌─────────────────────────────────────────────┐
│         🎯 Leader (tmux main pane)            │
│      Task Distribution · Result Integration · Final Verification          │
└─────────────────────────────────────────────┘
                    ↓ Distribute tasks
    ┌───────────┬───────────┬───────────┐
    │           │           │           │
    ▼           ▼           ▼           ▼
┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐
│Worker 1│ │Worker 2│ │Worker 3│ │Worker N│
│executor│ │debugger│ │designer│ │  ...   │
│indep tree│ │indep tree│ │indep tree│ │indep tree│
└────────┘ └────────┘ └────────┘ └────────┘
    ↓           ↓           ↓           ↓
    └───────────┴───────────┴───────────┘
                    ↓ Each finishes
┌─────────────────────────────────────────────┐
│       ✅ Leader integrates + verifies                  │
│    omx team await / omx team shutdown       │
└─────────────────────────────────────────────┘

4.2 🧠 Agent Selection Guide

4.3 ⌨️ Team Command Quick Reference

# 🚀 Start a team
omx team 3:executor "task"           # Start 3 executor workers

# 📊 Status management
omx team status my-team              # View team running status
omx team await my-team               # Wait for all workers to complete

# 🔄 Resume mechanism
omx team resume my-team              # Resume an interrupted team

# 🛑 Shut down team
omx team shutdown my-team            # Shut down team

🧠 5. Superpowers Core Skills

5.1 🎯 Core Process Skills

5.2 👁️ Three Perspectives of Plan Review

┌─────────────────┬─────────────────┬─────────────────┐
│   👔 CEO Perspective    │   🔧 Engineering Perspective    │  🎨 Design Perspective  │
│                 │                 │                 │
│ /plan-ceo-      │ /plan-eng-      │ /plan-design-   │
│   review        │   review        │   review        │
│                 │                 │                 │
│ Re-examine problem    │ Lock execution details    │ UX review    │
│ Find better solutions │ Check feasibility      │ Interaction rationality      │
└─────────────────┴─────────────────┴─────────────────┘

🌐 6. Gstack Execution Layer Details

6.1 🌍 Browser as the Only Entry Point

⚠️ Only entry point: /browse

Do not use other browser MCP tools like mcp__claude-in-chrome__* or mcp__computer-use__*

6.2 ✅ QA Verification Process

6.3 🚀 Deployment Process

┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│    /ship    │ ──→ │ /land-and-  │ ──→ │   /canary   │
│             │     │   deploy    │     │             │
└─────────────┘     └─────────────┘     └─────────────┘
      ↓                    ↓                    ↓
  Detect changes           Merge PR              Monitor after deployment
  Merge base               Wait CI               Observe production
  Run tests                Trigger deployment    Alert on anomalies

6.4 🛡️ Safety Guards

🚨 Dangerous commands must pass guards first

The following commands must use /careful or /guard or /freeze before execution:

• rm -rf / DROP TABLE / git push --force
• git reset --hard / kubectl delete
• Any destructive operation

💾 7. Ensuring Uninterrupted Operation

7.1 🗄️ State Persistence

7.2 🔄 Resume Mechanism

# Resume last session
omx resume

# Resume interrupted team
omx team resume my-team

# View historical sessions
omx session

7.3 📢 Notification Configuration

✅ 8. Configuration Checklist

❓ 9. Frequently Asked Questions

A:

• Team mode: Persistent parallel execution (tmux split screen, independent worktree), suitable for large tasks
• Regular Subagent: Small-scale parallel within a session, suitable for lightweight tasks

A:

• OMX: Responsible for orchestration (how to distribute tasks)
• Superpowers: Responsible for thinking (how to do things correctly)
• For large tasks, use both together

A:

omx resume              # Resume last session
omx team resume my-team # Resume team

A: OMX Team uses independent worktrees by default, each worker has an independent branch, automatically avoiding conflicts.

🎯 Quick Start

# 1️⃣ Start a simple task
omx task "Implement user login functionality"

# 2️⃣ Start parallel team development
omx team 3:executor "Refactor API module"

# 3️⃣ Full process: Design → Implement → Verify → Deploy
/brainstorming    # Design
/writing-plans    # Plan
/plan-ceo-review  # Review
omx team 2:executor "Implement"  # Parallel
/qa               # Verify
/ship             # Deploy

💡 Tip: This document is continuously updated. For questions, please refer to the latest version or contact the maintainer.