routing-gate

Determine the next CHAIN-phase cycle action from next_work_id and has_plan signals.

1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/Rwb3n/haios --skill routing-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: routing-gate
Source: https://github.com/Rwb3n/haios/tree/main/.claude/skills/routing-gate
Command: npx skills add https://github.com/Rwb3n/haios --skill routing-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridge routing logic for CHAIN phase decisions to determine the next cycle skill based on work item signals.

Core Features & Use Cases

  • Centralizes work-type routing for CHAIN phases (implementation-cycle, investigation-cycle, close-work-cycle).
  • Enforces cycle-locking checks to avoid blocked queues and ensures safe transitions between cycles.
  • Dispatches to the appropriate sub-skill (investigation-cycle, implementation-cycle, work-creation-cycle) based on input signals like next_work_id and has_plan.
  • Use Case: In a multi-cycle workflow, routing-gate selects the next action for a new work item, reducing duplication and ensuring consistent routing.

Quick Start

Use the routing-gate skill to determine the next cycle action by supplying the signals next_work_id and has_plan.

Frequently Asked Questions about routing-gate

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

FAQPage Schema
How does cycle routing work for CHAIN phase work items?

Cycle routing for CHAIN phase work items evaluates signals like next_work_id and has_plan to determine the next action. It performs cycle-locking checks and dispatches the work item to the appropriate sub-skill for safe transitions.

What is the best way to prevent blocked queues during multi-cycle workflow transitions?

To prevent blocked queues during multi-cycle workflow transitions, routing-gate enforces cycle-locking checks before dispatching work items. This ensures safe transitions between implementation, investigation, and work-creation cycles.

How do I determine the next cycle action for an investigation-cycle or implementation-cycle?

You determine the next cycle action by supplying work-item signals such as next_work_id and has_plan to the routing logic. The system evaluates these inputs to select and return the target sub-skill action.

When do I need centralized routing logic for work-creation cycles?

You need centralized routing logic for work-creation cycles when managing multi-cycle workflows to reduce duplication. It ensures consistent routing by evaluating work-item signals and dispatching to the correct sub-skill.

Can I use decision-table logic to route work items across different cycle phases?

Yes, you can route work items across cycle phases using decision-table logic that evaluates next_work_id and has_plan. This centralizes work-type routing for implementation, investigation, and close-work cycles.

Why does my work item fail to transition to the next implementation cycle?

Work items fail to transition to the next implementation cycle when cycle-locking checks detect unsafe conditions. The routing gate evaluates work-item signals to enforce safe transitions and avoid blocked queues.