pipeline

Orchestrate multi-stage OMX pipelines with state persistence and resume support.

24|2|Updated Mar 12, 2025
One-click install
npx skills add https://github.com/Orinks/AccessiWeather --skill pipeline-orinks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline
Source: https://github.com/Orinks/AccessiWeather/tree/main/.codex/skills/pipeline
Command: npx skills add https://github.com/Orinks/AccessiWeather --skill pipeline-orinks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates multi-stage OMX pipelines to enable reliable, resumed execution across complex workflows.

Core Features & Use Cases

  • Supports a uniform PipelineStage interface to compose and execute sequential stages
  • Provides default autopilot pipeline with stages: ralplan, team-exec, ralph-verify
  • Persists state for resume and supports configuration of per-run parameters (maxRalphIterations, workerCount, agentType)
  • Integrates with OMX for scalable, repeatable pipeline executions across development, testing, and production

Quick Start

Create an autopilot pipeline configuration and run it to execute the default stages (ralplan, team-exec, and ralph-verify).

Frequently Asked Questions about pipeline

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

FAQPage Schema
How do I orchestrate multi-stage OMX pipelines with reliable resume execution?

You can orchestrate multi-stage OMX pipelines by using a uniform PipelineStage interface that executes sequential stages and persists state in .omx/state/pipeline-state.json, enabling reliable resumed execution after interruptions across development, testing, and production.

What default stages are included in an OMX autopilot pipeline?

The default OMX autopilot pipeline includes three sequential stages: ralplan, team-exec, and ralph-verify. These stages provide a structured workflow for planning, parallel execution, and verification across your pipeline runs.

Can I tune per-run parameters like workerCount and maxRalphIterations in OMX pipelines?

Yes, you can tune per-run parameters such as maxRalphIterations, workerCount, and agentType in your OMX pipeline configuration. This allows you to adjust execution behavior dynamically for each pipeline run.

How does pipeline state persistence work for interrupted OMX workflows?

Pipeline state persistence works by saving execution progress to the .omx/state/pipeline-state.json file. This mechanism captures stage completion data, allowing the OMX pipeline to resume execution reliably from the exact point of interruption.

What is the best way to configure a custom PipelineStage interface for OMX workflows?

The best way to configure a custom PipelineStage interface is to implement the uniform stage interface provided by the orchestrator, allowing you to compose and execute custom sequential stages alongside the default ralplan, team-exec, and ralph-verify stages.