workflow-router

Route BAZINGA workflow transitions to the next agent via database state-machine rules.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/mehdic/CDC --skill workflow-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-router
Source: https://github.com/mehdic/CDC/tree/main/.claude/skills/workflow-router
Command: npx skills add https://github.com/mehdic/CDC --skill workflow-router

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It decides the next step in the BAZINGA workflow by consulting the seeded transitions and applying testing, escalation, and security rules to determine the next agent and action.

Core Features & Use Cases

  • Reads transitions and special rules from the database
  • Applies testing_mode, escalation, and security overrides
  • Outputs a structured JSON decision (next_agent, action, model, etc.)

Quick Start

After an agent responds, invoke this skill to determine the next actor (e.g., developer -> qa_expert) and whether to spawn or respawn.

Frequently Asked Questions about workflow-router

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

FAQPage Schema
How do I route workflow agents deterministically based on responses?

Workflow routing determines the next agent in a sequence by consulting state-machine transitions stored in a database. After any agent responds, the router applies the seeded transitions and rules to output the next target agent, action type, and contextual flags for spawning or respawning.

What database setup do I need before using workflow routing?

You need an initialized bazinga/bazinga.db with pre-seeded state-machine transitions and configuration rules. The router reads these transitions to make routing decisions, so the database must be populated with valid transition paths and any testing, escalation, or security override rules before invoking the skill.

Can workflow routing handle testing modes and security overrides?

Yes. Workflow routing applies testing_mode, escalation, and security overrides when determining the next action. These special rules modify routing behavior based on context, allowing you to bypass normal transitions during testing or escalate to different agents when security conditions are met.

What output does the workflow router produce?

The router outputs a structured JSON object describing the routing decision, including the next_agent to spawn, the action type to perform, the model to use, and contextual flags. This output directly feeds the next step in your BAZINGA workflow.

Do I need prior agent responses to use workflow routing?

Yes. Workflow routing operates after an agent has responded. It takes the latest agent response as input, consults the state-machine transitions, and determines which agent should act next based on the current workflow state and configured rules.