carl-dev-flow-orchestrator

Coordinate multi-stage software delivery workflows across Sisyphus, Hephaestus, and the user.

1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/C-ra-ZY/carl-dev-flow-skills --skill carl-dev-flow-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: carl-dev-flow-orchestrator
Source: https://github.com/C-ra-ZY/carl-dev-flow-skills/tree/main/skills/carl-dev-flow-orchestrator
Command: npx skills add https://github.com/C-ra-ZY/carl-dev-flow-skills --skill carl-dev-flow-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Coordinate the full multi-stage software delivery workflow across Sisyphus, Hephaestus, and the user, providing a single governance layer for stage transitions, artifact lifecycles, and cross-skill coordination.

Core Features & Use Cases

  • Orchestrates stage order and routes work to the appropriate narrower skills (requirements, tech-spec, implementation, review-loop).
  • Enforces lifecycle rules, owner roles, and artifact location conventions across the entire workflow.
  • Supports open collaboration and explicit issue tracking when disagreements arise, ensuring traceable decisions.

Quick Start

Load carl-dev-flow-orchestrator to begin the workflow and route to the current stage.

Frequently Asked Questions about carl-dev-flow-orchestrator

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

FAQPage Schema
What is a multi-stage software delivery workflow orchestrator?

A multi-stage software delivery workflow orchestrator coordinates stage transitions, artifact lifecycles, and cross-skill routing to provide a single governance layer for team collaboration and delivery.

How do I enforce lifecycle contracts and owner roles across development stages?

You enforce lifecycle contracts and owner roles by applying centralized governance rules that validate stage transitions, manage artifact locations, and route work to the appropriate narrower skills.

How do I route work to narrower skills like tech specs and implementation automatically?

You route work to narrower skills by orchestrating the stage order and applying centralized lifecycle contracts that automatically direct requirements, tech specs, implementation, and review-loop tasks.

Can I track disagreements and decisions explicitly during the software delivery workflow?

Yes, you can track disagreements explicitly during the delivery workflow by supporting open collaboration and issue tracking to ensure all stage transition decisions remain fully traceable.

Does this workflow orchestration approach work without external dependencies?

Yes, this workflow orchestration approach works without external dependencies, relying entirely on its internal scripts to coordinate multi-stage delivery, artifact management, and team collaboration governance.