oe-workflow-routing

shami-ah's avatarfrom shami-ah

Fast routing triage for workflow messages; points to docs/workflow-routing-map.md.

⭐0stars🔀1forks📁View on GitHub🕐Updated Jan 8, 2026
[Tool Routing and Orchestration]

When & Why to Use This Skill

This Claude skill provides high-efficiency routing triage and debugging capabilities for complex message-based workflows. It streamlines the diagnostic process for identifying routing errors, step detours, and out-of-context message drops by providing immediate access to routing maps and systematic troubleshooting protocols for backend workflow runtimes.

Use Cases

  • Debugging routing bugs where messages are incorrectly directed, stuck in loops, or sent to the wrong workflow step.
  • Quickly accessing and sharing the 'workflow-routing-map.md' to provide a visual or structural reference for system architecture.
  • Investigating 'out-of-context' (OOC) message drops by verifying unified intent against the current state and thread history.
  • Validating pre-route logic, including early exits, guardrail forcing, and billing/deposit bypasses before inspecting individual step handlers.
  • Triage of change-propagation detours and site visit intercepts that may interrupt standard routing loops.
nameoe-workflow-routing
descriptionFast routing triage for workflow messages; points to docs/workflow-routing-map.md.

When to use

  • Routing bugs, wrong step, detours, out-of-context, or "where did this message go?".
  • Requests for a quick routing reference or map.
  • Need to point people to the routing doc fast.

Quick start (do this first)

  1. Open docs/workflow-routing-map.md and share it.
  2. Ask for the minimal routing state (current_step, caller_step, thread_state, key hashes) and any pre-route action.
  3. Check pre-route early exits (OOC/duplicate/manager escalation) before step logic.
  4. Verify guard forcing (Steps 2-4) and billing/deposit bypasses.
  5. Only then inspect step handlers or change-propagation detours.

Fast response snippet

  • "Routing map lives at docs/workflow-routing-map.md. Start with state fields, pre-route early exits, guard forcing, then router loop."

Key files to open

  • docs/workflow-routing-map.md
  • backend/workflow_email.py
  • backend/workflows/runtime/pre_route.py
  • backend/workflows/runtime/router.py
  • backend/workflow/guards.py
  • backend/workflows/change_propagation.py

Notes

  • OOC can drop messages before routing; confirm unified intent vs current step.
  • Site visit intercept can fire at any step.
  • Step 6/7 HIL tasks are currently skipped.