workflow-orchestration

Orchestrate script sequences with error handling, logging, and rollback.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/zero-rehq/opencode-kit --skill workflow-orchestration-zero-rehq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-orchestration
Source: https://github.com/zero-rehq/opencode-kit/tree/main/.opencode/skill/workflow-orchestration
Command: npx skills add https://github.com/zero-rehq/opencode-kit --skill workflow-orchestration-zero-rehq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, git, jq, timeout, and includes scripts (resource) components.

What problem does it solve?

This skill provides a robust, deterministic way to run a sequence of scripts with centralized logging, error handling, and optional rollback to ensure reliability in complex workflows.

Core Features & Use Cases

  • Sequential phases: Initialize, Validate, Execute, Finalize, each encapsulated as independent scripts.
  • Robust error handling: Aborts the workflow on failure and optionally triggers a rollback.
  • Auditable logs & gates: Generates time-stamped logs and supports quality gates to validate outcomes.
  • Use Case: Orchestrate end-to-end deployment pipelines or E2E tests that require consistent, repeatable steps across multiple repos.

Quick Start

  • Run the full workflow: ./orchestrator.sh
  • Run with context: ./orchestrator.sh --task "catalogos" --repos "cloud_front,signage_service"
  • Execute selective phases: ./orchestrator.sh --phases "1,2"
  • Dry-run: ./orchestrator.sh --dry-run

Frequently Asked Questions about workflow-orchestration

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

FAQPage Schema
How do I orchestrate multi-script workflows with rollback for multi-step deployments?

You can orchestrate multi-script workflows by executing four standard phases: Initialize, Validate, Execute, and Finalize. The process aborts on failure, optionally triggers a rollback, and generates traceable logs for deterministic pipeline results.

What is the best way to automate E2E test pipelines across multiple repositories?

Automating E2E pipelines across multiple repos requires a deterministic orchestrator that executes sequential phases with quality gates and timeouts. This ensures repeatable steps and traceable results across all targeted repositories with centralized logging.

Can I run selective phases or dry-runs in a workflow orchestration pipeline?

Yes, workflow orchestration supports selective phases and dry-runs. You can execute specific phases using the `--phases` argument and simulate the pipeline without side effects using the `--dry-run` flag.

Do I need Node and Git to run workflow orchestration scripts?

Yes, workflow orchestration requires Node, Git, jq, and timeout installed in your environment. These dependencies support executing scripts, processing JSON context, managing repositories, and enforcing execution limits.

How does error handling and logging work in a multi-step deployment sequence?

Error handling in multi-step deployments aborts the workflow immediately upon script failure and optionally triggers a rollback. Logging generates time-stamped records for every phase, ensuring outcomes are auditable and traceable across the pipeline.