pipeline

Orchestrate OMX pipeline stages with state persistence and resume support.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/RJJJJ/project2 --skill pipeline-rjjjj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline
Source: https://github.com/RJJJJ/project2/tree/main/.codex/skills/pipeline
Command: npx skills add https://github.com/RJJJJ/project2 --skill pipeline-rjjjj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configurable pipeline orchestrator for OMX that sequences stages with state persistence and resume support.

Core Features & Use Cases

  • Sequencing of stages via a uniform PipelineStage interface.
  • State persistence with resume support across restarts.
  • Configurable pipeline parameters like maxRalphIterations, workerCount, and agentType.
  • Extensible API to compose pipelines with custom stages.

Quick Start

Configure the pipeline and call runPipeline to initiate the staged workflow.

Frequently Asked Questions about pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate OMX pipelines with resume support across restarts?

OMX pipeline orchestration with resume support is handled by sequencing stages via a uniform PipelineStage interface and storing progress in .omx/state/pipeline-state.json, allowing workflows to resume after interruptions.

What is a configurable pipeline orchestrator for end-to-end OMX workflows?

A configurable pipeline orchestrator for OMX workflows sequences planning, execution, and verification stages while supporting configurable parameters like maxRalphIterations, workerCount, and agentType for customized stage behavior.

How do I configure pipeline parameters like workerCount and agentType for OMX stages?

Configuring pipeline parameters like workerCount and agentType involves setting configurable defaults when initiating the staged workflow through runPipeline, enabling stage-specific behavior across OMX planning and execution phases.

Can I add custom stages to an OMX pipeline using a uniform interface?

Adding custom stages to an OMX pipeline is supported through an extensible API that implements the PipelineStage interface, allowing you to compose pipelines with tailored planning, execution, and verification logic.

Does state persistence work automatically for OMX pipeline stage sequencing?

State persistence for OMX pipeline stage sequencing works automatically by storing progress in .omx/state/pipeline-state.json, ensuring resume support across restarts without manual state management overhead.

What are the limitations of resuming OMX pipeline stages after a failure?

Resuming OMX pipeline stages after failure relies on the state stored in .omx/state/pipeline-state.json; limitations depend on the completeness of the persisted state and the configurable maxRalphIterations parameter governing retry behavior.