explainx.ainewsletter3.4k
Productivity

omx▌

supercent-io/skills-template · updated May 2, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/supercent-io/skills-template --skill omx
0 commentsdiscussion
summary

OMX implements a structured execution pipeline:

skill.md

oh-my-codex (OMX) - Multi-Agent Orchestration for Codex CLI

When to use this skill

  • Orchestrating complex multi-agent workflows with OpenAI Codex CLI
  • Running parallel team workers in tmux for coordinated task execution
  • Using persistent MCP servers for state, memory, and code intelligence
  • Executing staged pipelines (plan → prd → exec → verify → fix)
  • Leveraging role-based agent prompts for specialized tasks

1. Core Concepts

Role Prompts (30 Agents)

Agent Tier Agents Use Case
Core Development architect, planner, executor, debugger, verifier, explore Main development workflow
Quality Assurance style-reviewer, quality-reviewer, api-reviewer, security-reviewer, performance-reviewer Code review lane
Domain Experts dependency-expert, test-engineer, build-fixer, designer, writer, qa-tester Specialized tasks
Product Strategy product-manager, ux-researcher, product-analyst, information-architect Product planning

Workflow Skills (40+)

Skill Trigger Description
autopilot $autopilot Full autonomous execution from idea to working code
ralph $ralph Self-referential loop with verifier verification until completion
ultrawork $ulw Maximum parallelism with parallel agent orchestration
team $team N coordinated agents using Codex CLI native teams
plan $plan Strategic planning with consensus and review modes
research $research Parallel scientist agents for comprehensive research
tdd $tdd Test-first development with red-green-refactor cycle
build-fix $build-fix Fix build errors, type errors, and toolchain failures
code-review $code-review Comprehensive code review across all quality dimensions
security-review $security-review Security audit focusing on vulnerabilities and trust boundaries
cancel $cancel Stop execution modes and clear active state

MCP Servers

Server Purpose
omx_state Persistent mode lifecycle state
omx_memory Memory + notepad surfaces for long-running sessions
omx_code_intel Code intelligence and context
omx_trace Execution tracing and debugging

2. Installation & Setup

Prerequisites

  • macOS or Linux (Windows via WSL2)
  • Node.js >= 20
  • Codex CLI installed (npm install -g @openai/codex)
  • Codex auth configured

Install oh-my-codex

npm install -g oh-my-codex
omx setup
omx doctor

Recommended Launch Profile

# Trusted environment with high reasoning
omx --xhigh --madmax

3. Usage Patterns

Role Prompts (Inside Codex)

/prompts:architect "analyze current auth boundaries"
/prompts:executor "implement input validation in login"
/prompts:security-reviewer "audit OAuth flow"

Workflow Skills

$plan "ship OAuth callback safely"
$autopilot "implement user registration"
$team 3:executor "fix all TypeScript errors"

Team Mode (Terminal)

# Start parallel team workers
omx team 4:executor "parallelize a multi-module refactor"

# Monitor team status
omx team status <team-name>

# Resume team work
omx team resume <team-name>

# Shutdown team
omx team shutdown <team-name>

4. Launch Flags

Flag Description
--yolo Fast execution, minimal verification
--high High reasoning effort
--xhigh Extra-high reasoning effort
--madmax Maps to Codex --dangerously-bypass-approvals-and-sandbox
--force Force operation
--dry-run Preview without execution
--verbose Verbose output

5. Staged Pipeline

OMX implements a structured execution pipeline:

team-plan → team-prd → team-exec → team-verify → team-fix
  1. Plan: Strategic decomposition of work
  2. PRD: Product requirements definition
  3. Exec: Parallel execution by team workers
  4. Verify: Validation of deliverables
  5. Fix: Automated error resolution

6. Hook Extensions (v0.4.0+)

Native Lifecycle Events

  • session-start / session-end / session-idle
  • turn-complete

Plugin Workflow

# Enable hook plugins
OMX_HOOK_PLUGINS=1 omx hooks test

# Hook commands
omx hooks init     # Initialize hooks
omx hooks status   # Check hook status
omx hooks validate # Validate configuration
omx hooks test     # Test hook execution

Plugin files: .omx/hooks/*.mjs

7. Configuration

AGENTS.md Injection

By default, OMX injects project-level AGENTS.md:

-c model_instructions_file="<cwd>/AGENTS.md"

Environment Controls

# Disable AGENTS.md injection
OMX_BYPASS_DEFAULT_SYSTEM_PROMPT=0 omx

# Custom instructions file
OMX_MODEL_INSTRUCTIONS_FILE=/path/to/instructions.md omx

Quick Reference

Command Action
omx Launch Codex with HUD
omx setup Install prompts, skills, config wiring
omx doctor Installation/runtime diagnostics
omx doctor --team Team/swarm diagnostics
omx team <n>:<role> "<task>" Start team workers
omx team status <name> Show team status
omx team shutdown <name> Shutdown team
omx status Show active modes
omx cancel Cancel execution modes
omx reasoning <mode> Set reasoning (low/medium/high/xhigh)
omx hud HUD display options
omx help Show help

Resources

License

MIT License

how to use omx

How to use omx on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • ›Cursor installed and configured on your development machine
  • ›Node.js version 16.0+ with npm package manager (verify with node --version)
  • ›Active project directory or workspace where you want to add omx
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/supercent-io/skills-template --skill omx

The skills CLI fetches omx from GitHub repository supercent-io/skills-template and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/omx

Reload or restart Cursor to activate omx. Access the skill through slash commands (e.g., /omx) or your agent's skill management interface.

⚠

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

Additional Resources

›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases▌

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

✓

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

✓

Save 3-5 hours/week on communication overhead

Implementation Guide▌

Prerequisites

  • ›Claude Desktop or compatible AI client
  • ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • ›Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • ⚠Not validating competitive research—verify facts before sharing
  • ⚠Accepting user stories without involving engineering team
  • ⚠Over-relying on frameworks without qualitative judgment
  • ⚠Not customizing outputs to company culture and communication style
  • ⚠Skipping stakeholder validation of generated requirements

Best Practices▌

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • −Don't publish competitive analysis without fact-checking
  • −Don't finalize user stories without engineering review
  • −Don't make prioritization decisions solely on AI scoring
  • −Don't skip customer validation of generated requirements
  • −Don't ignore company-specific context and culture

💡 Pro Tips

  • ★Provide context: company goals, constraints, customer feedback
  • ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • ★Use skill for 70% generation + 30% customization to company needs

When to Use This▌

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path▌

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.6★★★★★36 reviews
  • ★★★★★Henry Khan· Dec 28, 2024

    omx fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • ★★★★★Diego Smith· Dec 8, 2024

    Keeps context tight: omx is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • ★★★★★Nia Rahman· Nov 27, 2024

    omx is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • ★★★★★Omar Rao· Nov 23, 2024

    Solid pick for teams standardizing on skills: omx is focused, and the summary matches what you get after install.

  • ★★★★★Olivia Park· Nov 19, 2024

    I recommend omx for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • ★★★★★Diego Zhang· Oct 18, 2024

    Useful defaults in omx — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Meera Okafor· Oct 14, 2024

    We added omx from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Jin Srinivasan· Oct 10, 2024

    omx reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • ★★★★★Piyush G· Sep 25, 2024

    Solid pick for teams standardizing on skills: omx is focused, and the summary matches what you get after install.

  • ★★★★★Hana Agarwal· Sep 25, 2024

    I recommend omx for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 36

1 / 4