Workflow Orchestrator

Coordinates automated end-to-end Dev workflows for Claude Code with tiered agents and repo-scoped persistence.

1|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill workflow-orchestrator-zb-ss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Workflow Orchestrator
Source: https://github.com/zb-ss/claude-plugin-workflow/tree/main/skills/start
Command: npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill workflow-orchestrator-zb-ss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of coordinating a complex multi-phase software development process—planning, implementing, reviewing, security hardening, and testing—without the user needing to micromanage every step.

Core Features & Use Cases

  • Repo-scoped workflow state management: Keeps progress isolated per repository and persists plans for auditability and live editing in org-mode or Markdown.
  • Tiered autonomous agent orchestration: Routes tasks across different model tiers and phases (planning, execution, code review, security, quality gate, and completion guard) with looped remediation until PASS.
  • Configurable execution modes: Supports standard/turbo/eco for different speed-quality tradeoffs and thorough/swarm behaviors, plus an epic mode for multi-component projects with worktree isolation and integration.
  • Safety and permissions guardrails: Enforces a permission model (autonomous vs ask-before vs blocked actions) and uses a hardened review system with zero-tolerance gates.

Quick Start

Ask Claude to start a feature workflow by running: /workflow:start feature Add user authentication with JWT tokens

Frequently Asked Questions about Workflow Orchestrator

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

FAQPage Schema
How do I automate complex multi-phase development workflows with autonomous agents?▼

Automated multi-phase development workflows are orchestrated by routing tasks across tiered agents for planning, execution, code review, security, and testing. It coordinates these phases sequentially using repo-scoped persistent state, applying looped remediation until review gates pass.

What is the best way to manage state and permissions for autonomous code generation pipelines?▼

Autonomous code generation pipelines manage state by persisting progress per repository for auditability and live editing. Permissions are enforced through a tiered guardrail model categorizing actions as autonomous, ask-before, or blocked to ensure safety during execution.

How do I start an autonomous feature implementation workflow using Claude Code?▼

Feature implementation workflows start by triggering the entrypoint with a command like `/workflow:start feature` followed by the task description. The orchestrator then executes mode-driven planning, implementation, and review phases automatically.

Can I use workflow orchestration for epic multi-component projects with worktree isolation?▼

Epic multi-component projects are supported using an epic mode that provides worktree isolation and integration. This allows large-scale tasks to be broken down and managed with thorough or swarm behaviors across different execution tiers.

Does the orchestration framework support configurable execution modes for speed-quality tradeoffs?▼

Configurable execution modes including standard, turbo, and eco are supported to adjust speed-quality tradeoffs. These modes determine how agents approach planning, execution, and quality verification gates throughout the workflow lifecycle.

Why does automated code review require strict PASS iterations before workflow completion?▼

Strict PASS iterations are required to enforce zero-tolerance security and quality gates before completion. The completion guard ensures no workflow finishes until looped remediation successfully resolves all code review and testing failures.