pipeline

Coordinate stage-by-stage Omagy workflow execution with resumable state persistence.

3|Updated May 24, 2026
One-click install
npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill pipeline-shayne-snap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pipeline
Source: https://github.com/shayne-snap/oh-my-antigravity/tree/main/plugin/skills/pipeline
Command: npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill pipeline-shayne-snap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of coordinating a long-running Omagy workflow across multiple stages without losing progress between turns or risking inconsistent handoffs.

Core Features & Use Cases

  • Sequenced stage orchestration with a uniform result contract: Runs Omagy stages in order and standardizes stage outputs as status plus artifacts for downstream use.
  • Resumable state persistence for workflow reliability: Persists pipeline status under .omagy/state/pipeline-state.json so you can resume, inspect, and complete multi-step runs safely.
  • Built-in pipeline stages for planning, execution, review, and QA: Uses deep-interview, ralplan, ultragoal, code-review, and ultraqa as the default progression, while retaining legacy/custom adapters like team-exec and ralph-verify for explicit non-default paths.
  • Team execution gating: Inserts /omagy:team only when warranted inside an Ultragoal story to support parallel lanes without overcomplicating the main flow.

Quick Start

Start a pipeline by running omagy pipeline start with an input task payload, then iteratively advance with omagy pipeline next and execute the corresponding /omagy:<stage> skill until completion.

Frequently Asked Questions about pipeline

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

FAQPage Schema
How do I maintain resumable state for a multi-step code review and QA workflow?▼

Multi-step workflow state persistence is maintained by recording pipeline status under a dedicated JSON state file, allowing you to resume, inspect, and complete long-running development runs safely across turns.

What is the best way to orchestrate stage sequencing for durable goal execution?▼

Stage sequencing for durable goal execution is orchestrated by running default stages like deep-interview, planning, execution, code review, and adversarial QA in strict order using a uniform stage-result JSON contract for downstream artifact accumulation.

How do you handle team execution gating within a multi-stage development pipeline?▼

Team execution gating inserts parallel team lanes only when explicitly warranted inside an Ultragoal story, preventing unnecessary complexity while supporting parallel team execution within the main pipeline flow.

Can I use custom workflow adapters for non-default stage paths in a pipeline?▼

Custom workflow adapters are supported for explicit non-default paths, allowing you to substitute legacy or custom stages like team-exec and ralph-verify instead of the default progression.

Do I need a specific state file to coordinate consistent handoffs across workflow stages?▼

A persisted pipeline state file located under the .omagy/state/ directory is required to coordinate stage-by-stage execution, ensuring consistent handoffs and resumable progress across multiple development turns.