workflow-orchestrator

Coordinate CLI workflows with done-signal files and optional locks.

Updated Aug 12, 2025

Search Tags:#workflow #devops #synchronization #dependencies #cli #locking

Ready to run

npx skills add https://github.com/EdWrld/config.files --skill workflow-orchestrator-edwrld

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-orchestrator
Source: https://github.com/EdWrld/config.files/tree/main/skills/workflow-orchestrator
Command: npx skills add https://github.com/EdWrld/config.files --skill workflow-orchestrator-edwrld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Coordinate multiple Codex CLI workflows using done-signal files, optional locks, and simple dependencies to ensure predictable, coordinated execution of tasks across tools.

Core Features & Use Cases

Done-signal driven dependencies: wait for signals before starting a workflow and generate signals upon successful completion.
Optional resource locking: prevent conflicts by using a shared lock path (flock-based or lockdir).
Dependency patterns: model simple graphs where workflows wait on others to run in the correct order.
Use case: orchestrate build, migration, and test steps in a local dev or CI-like environment.

Quick Start

Run a workflow by invoking run-workflow.sh with your --wait-for and --done-file arguments and an optional --lock path.

Frequently Asked Questions about workflow-orchestrator

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

FAQPage Schema

How do I synchronize CLI scripts using done-signal files?▼

Workflow dependencies are managed by modeling simple graphs where scripts wait for done files from parent tasks. This ensures correct execution order for build, migration, and test steps in local or CI-like environments.

What is the best way to prevent resource conflicts during parallel CLI workflows?▼

You can run coordinated workflows by invoking the run-workflow.sh script with --wait-for and --done-file arguments to define dependencies, and an optional --lock path to manage resource locking during execution.

Can I use flock for locking when coordinating CLI workflows?▼

This approach is applicable for scenarios where several scripts must run in order or in parallel with dependencies and optional shared resources, making it ideal for orchestrating build, migration, and test steps.

How do I model dependencies between multiple scripts in a devops workflow?▼

Known limitations include relying on the filesystem for done-signal files and lock states, so you should not use this approach if your environment lacks a shared filesystem or requires distributed cross-machine synchronization.