pipeline

Orchestrates multi-stage workflows with persistent state and resume capability for OMX pipelines.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/YeaChan05/Remittance --skill pipeline-yeachan05
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline
Source: https://github.com/YeaChan05/Remittance/tree/main/.codex/skills/pipeline
Command: npx skills add https://github.com/YeaChan05/Remittance --skill pipeline-yeachan05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OMX pipelines require reliable sequencing of multiple stages with state persistence and the ability to resume after interruptions. This skill provides a configurable orchestrator that coordinates stages and persists progress to enable robust automation workflows.

Core Features & Use Cases

  • Stage-based orchestration with a uniform PipelineStage interface
  • Built-in resume and state persistence across runs
  • End-to-end OMX workflows including autopilot, team execution, and verification
  • Easy configuration of the stages array to tailor pipelines for different scenarios

Quick Start

Configure and run an autopilot pipeline with predefined stages to execute a build feature X.

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 workflows with state persistence?

OMX pipelines use a configurable stages array with a uniform PipelineStage interface to sequence multi-stage workflows, persisting state throughout the process to support resume and traceability across runs.

What is pipeline state persistence and how does it handle workflow interruptions?

Pipeline state persistence saves the execution progress of multi-stage workflows, allowing the orchestrator to resume from the last completed stage after an interruption rather than restarting the entire OMX workflow from the beginning.

How do I configure a stages array for autopilot and team execution pipelines?

You configure a stages array by defining a sequence of PipelineStage interface objects tailored to your scenario, enabling the orchestrator to run end-to-end workflows for OMX autopilot, team execution, and verification flows.

Can I resume an interrupted OMX verification flow without restarting?

Yes, the pipeline orchestrator supports resume capability by persisting state throughout the verification flow, allowing you to restart the workflow from the last known state instead of rerunning previously completed stages.

What's the best way to structure multi-stage workflows for OMX traceability?

The best way to structure OMX workflows for traceability is using the configurable stages array with the PipelineStage interface, which provides persistent state management to track progress and support restart across autopilot and team execution flows.

Do I need specific dependencies to run configurable OMX pipeline stages?

No specific dependencies are required to run configurable OMX pipeline stages, as the orchestrator applies across autopilot, team-exec, and ralph verification flows using a built-in PipelineStage interface and state persistence management.