om-superpowers
Claude Code plugin for Open Mercato developers. 16 skills covering the full OM lifecycle — from business requirements through implementation to code review.
Install
Claude Code (CLI & Desktop)
# Install the plugin
/plugin marketplace add SHGrowth/om-superpowers
# If prompted, confirm installation
/plugin install om-superpowers@SHGrowth/om-superpowers
Update to latest version
# Pull latest changes from GitHub
/plugin marketplace update SHGrowth/om-superpowers
# Reload without restarting the session
/reload-plugins
Auto-update is off by default for third-party plugins. Enable it in /plugin → Marketplaces tab.
Codex CLI
Codex does not support Claude Code plugins natively. To use OM skills in Codex:
- Copy the
skills/ directory into your project's .agents/skills/ (Codex auto-discovers skills from this path)
- Copy
om-reference/ into your project root (skills reference these for platform conventions)
- Skills that use the
Skill tool will need manual invocation — Codex doesn't have a skill tool equivalent
Alternatively, use the codex-plugin-cc to run Codex inside Claude Code sessions where OM skills are available.
Prerequisites
- Claude Code (or Cursor with plugin support)
- superpowers plugin — OM skills reference superpowers workflows (brainstorming, writing-plans, executing-plans, TDD)
- GitHub CLI (
gh) — authenticated, for om-cto platform search
How It Works
The plugin auto-detects OM projects on session start by checking for @open-mercato/ in package.json, "Open Mercato" in AGENTS.md, or an .ai/ directory. When detected, all 16 skills are injected into the session.
The Two Workflows
Manual (skill-by-skill): Invoke any skill directly — om-code-review, om-troubleshooter, etc.
Orchestrated (autonomous): Start with om-product-manager to define requirements, then om-cto takes over — autonomously writes specs, implements them one by one, runs tests, does code review, and checkpoints with you between each spec.
Manual Orchestrated
(pick any skill) (autonomous pipeline)
┌─────────────────┐ ┌─────────────────────────┐
│ om-cto │ │ om-product-manager │
│ (gap analysis) │ │ (App Spec with Mat) │
├─────────────────┤ └───────────┬─────────────┘
│ om-code-review │ │
│ (review code) │ ▼
├─────────────────┤ ┌─────────────────────────┐
│ om-troubleshoot│ │ om-cto │
│ (fix errors) │ │ Spec Orchestrator: │
├─────────────────┤ │ decompose → write specs│
│ om-integration │ │ → cross-validate │
│ -tests (QA) │ │ → execution plan │
├─────────────────┤ │ → you review │
│ om-spec-writing│ └───────────┬─────────────┘
│ (write a spec) │ │ (per spec)
├─────────────────┤ ▼
│ ...any skill │ ┌─────────────────────────┐
└─────────────────┘ │ om-cto │
│ Implementation Orch: │
│ implement → test → │
│ code review → you test │
│ on localhost → next │
└─────────────────────────┘
Skills
Spec & Design
| Skill | When to use |
|---|
om-product-manager | Defining business requirements — BEFORE any spec or code exists |
om-cto | Gap analysis, architecture decisions, or orchestrating the full spec→build pipeline |
om-ux | UI architecture review — navigation, task completion, cognitive load |
om-spec-writing | Creating architecturally compliant specifications |
om-pre-implement-spec | Pre-implementation backward compatibility and risk analysis |
Implementation
SHGrowth