winston-router

Name: winston-router
Availability: InStock
Author: paulmalmquist

Route Winston/Novendor requests to correct agents and handoffs using surface rules.

Updated Jan 22, 2026

Search Tags:#workflow #routing #agents #orchestration #handoff #winston #novendor

Ready to run

npx skills add https://github.com/paulmalmquist/Consulting_app --skill winston-router

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: winston-router
Source: https://github.com/paulmalmquist/Consulting_app/tree/main/skills/winston-router
Command: npx skills add https://github.com/paulmalmquist/Consulting_app --skill winston-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route Winston/Novendor requests to the correct agents and handoffs after the repository-level router has already decided the surface.

Core Features & Use Cases

Handoff orchestration to the correct agent (dispatcher-winston, commander-winston, architect-winston, and others) based on surface and intent.
Maintain routing rules, surface mappings, and agent availability to ensure fast, accurate handoffs for Winston/Novendor workflows.
Supports repo-wide and surface-specific routing decisions, including CLAUDE/Codex harness requests and Novendor surfaces.

Quick Start

Route a Winston or Novendor request to the appropriate agent using the predefined handoff map.

Frequently Asked Questions about winston-router

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

FAQPage Schema

How do I route agent requests to the correct worker in an orchestration workflow?▼

Agent request routing is handled by applying an agent map and surface rules to direct handoffs to the correct worker based on intent. This ensures fast, accurate orchestration across repo surfaces after the initial routing decision.

What is agent handoff management and when do I need it for multi-agent workflows?▼

Agent handoff management coordinates the transfer of requests between specialized agents using a predefined handoff_to list. You need it when orchestrating multi-agent workflows that require safe and efficient task delegation across different surfaces.

Can I use surface-specific routing rules for CLAUDE and Codex harness requests?▼

Yes, surface-specific routing rules support CLAUDE and Codex harness requests by maintaining surface mappings and trigger handling. This allows the router to apply routing decisions tailored to each specific orchestration surface.

What's the best way to manage dispatcher and commander agent availability during task orchestration?▼

Managing agent availability for dispatcher and commander agents is achieved by maintaining routing rules and an agent map within the orchestration layer. This approach guarantees accurate handoffs by checking availability before routing requests.

Does this agent router work after the repository-level surface decision has already been made?▼

Yes, this routing mechanism operates after the repository-level router has decided the surface. It takes the determined surface and routes the request to the correct agents and handoffs using its internal agent map and trigger handling.

Why are my Winston workflow handoffs failing to reach the correct agents?▼

Winston workflow handoffs fail when surface mappings and trigger handling are not properly aligned with the agent map. Accurate routing requires maintaining updated agent availability and correct surface rules to ensure safe delegation.