From opsx-omc-bridge
Bridge skill that delegates complex OpenSpec changes to Oh My ClaudeCode (OMC) team/ralph mode. Triggered when user says "run with team", "parallelize", "delegate to ralph", "start big task", "delegate full implementation", or when an OpenSpec change has 4+ tasks, multiple domains, or phased structure. Best for large-scale parallelizable implementations and refactoring requiring iterative verification.
npx claudepluginhub kyongsik-yoon/opsx-omc-bridge --plugin opsx-omc-bridgeThis skill uses the workspace's default tool permissions.
Bridge skill that hands off complex OpenSpec planning artifacts to OMC team or ralph mode. Automatically determines the optimal execution strategy by running a preflight pass, resolving the canonical execution context, and analyzing task structure.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.
Bridge skill that hands off complex OpenSpec planning artifacts to OMC team or ralph mode. Automatically determines the optimal execution strategy by running a preflight pass, resolving the canonical execution context, and analyzing task structure.
Scan for active changes, same as quick.
ls -d openspec/changes/*/tasks.md 2>/dev/null | grep -v archive
If multiple changes exist, ask the user to select one.
Complex work requires the full artifact set and a clear execution context:
CHANGE_DIR="openspec/changes/<change-name>"
MISSING=""
test -f "$CHANGE_DIR/proposal.md" || MISSING="$MISSING proposal.md"
test -f "$CHANGE_DIR/design.md" || MISSING="$MISSING design.md"
test -f "$CHANGE_DIR/tasks.md" || MISSING="$MISSING tasks.md"
# Check for delta specs
ls "$CHANGE_DIR/specs/" 2>/dev/null | head -1 || MISSING="$MISSING delta-specs"
/opsx:continue or /opsx:ffPreferred compacted brief candidates:
ls "$CHANGE_DIR"/implementation-brief.md \
"$CHANGE_DIR"/brief.md \
"$CHANGE_DIR"/context.md \
"$CHANGE_DIR"/handoff.md 2>/dev/null | head -1
Preflight checklist:
Parse tasks.md to analyze the work structure:
Analysis criteria:
- [ ] items)## Phase, ## Stage, or similar headers)Strategy decision matrix:
| Condition | OMC Mode | Rationale |
|---|---|---|
| Sequential phases with strong dependencies | ralph | Step-by-step with verification |
| Independent tasks within a phase | team N:executor | Parallel processing |
| Single phase, 4+ tasks | team N:executor | Simple parallelization |
| Refactoring requiring iterative verification | ralph | Repeats until architect approval |
| Sequential phases + parallelizable tasks within | ralph + team per phase | Hybrid approach with phase gates |
Agent count calculation:
team 3:executorDefault recommendation rules:
ralph when the overall flow is sequential and mistakes in earlier phases will invalidate later workhybrid when the global phase order is sequential, but one or more phases have internally parallelizable tasksteam only when most work is independent and can safely proceed without serialized phase gatesExtract context from all artifacts with this precedence:
Also read openspec/project.md to include project-wide context (tech stack, conventions).
Important context handling rules:
ralph Implement the following changes. Do not stop until complete.
## Project Context
[Tech stack and conventions extracted from project.md]
## Change Background
[Summary from proposal.md]
## Architectural Decisions (must follow)
[Key content from design.md]
## Verification Scenarios
[GIVEN/WHEN/THEN from delta specs — criteria for Architect verification]
## Tasks (proceed in order)
[Full text of tasks.md]
## Guidelines
- Verify each phase against its GIVEN/WHEN/THEN scenarios upon completion
- Never deviate from design.md architectural decisions
- Update tasks.md with [x] as each task completes
- Fix immediately if existing tests break
- Run the full test suite after all phases are complete
Use ralph as the outer orchestrator. For phases that are parallelizable internally, instruct ralph to delegate only that phase's independent work to team, wait for verification, then continue to the next phase.
Prompt structure to compose:
ralph Implement the following phased change. Keep global phase order intact.
## Project Context
[Extracted from project.md]
## Change Background
[Summary from compacted brief or proposal.md]
## Architectural Decisions (must follow)
[Key content from design.md]
## Verification Scenarios
[GIVEN/WHEN/THEN from delta specs]
## Execution Plan
- Follow phases in order
- Use team mode only for the phases explicitly marked parallelizable
- Verify each phase before continuing
- If a phase fails verification, repair it before moving on
- If interrupted, resume from the last incomplete phase rather than restarting everything
## Parallelizable Phases
[Example: Phase 4 storage adapters, Phase 9 notification fan-out]
## Tasks
[Full text of tasks.md]
team [N]:executor Implement the following tasks in parallel.
## Project Context
[Extracted from project.md]
## Change Background
[Summary from proposal.md]
## Architectural Decisions (all agents must follow)
[Key content from design.md]
## Task Distribution
### Agent 1: [domain/role]
[Assigned task list]
### Agent 2: [domain/role]
[Assigned task list]
### Agent N: [domain/role]
[Assigned task list]
## Common Guidelines
- Check off completed tasks as [x] in tasks.md
- Strictly follow design.md architectural decisions
- Do not modify files owned by other agents
- Run tests for your assigned area upon completion
Show the analysis results and get user approval before delegating:
OpenSpec → OMC Delegation Analysis
Change: add-jmx-metrics-table
Tasks: 8 (3 phases)
Strategy: hybrid (ralph orchestrator with team inside Phase 4-5 and Phase 9-10)
Phase 1: DDL & Infrastructure (3 tasks)
Phase 2: Service Layer (3 tasks) — depends on Phase 1
Phase 3: Testing (2 tasks) — depends on Phase 2
Verification scenarios: 3 (from delta specs)
Resume support: start from last incomplete phase if interrupted
Proceed? [Y/n]
To change strategy, say "switch to team" or "use autopilot instead".
When the analysis shows a sequential global flow with only a few parallelizable phases, recommend hybrid instead of plain team.
Once OMC execution completes:
All tasks complete. What would you like to do next?
1. /opsx:verify — Validate implementation against delta spec scenarios
2. /opsx:archive — Archive this change (skip verification)
3. Skip — Do nothing for now
Choose [1/2/3]:
Use AskUserQuestion to present this choice. Based on the user's selection:
/opsx:verify skill/opsx:archive skillralph or hybrid should be the default. Plain team is for work that is genuinely independent.