qwen-dispatch

Route software-engineering tasks between Claude-style thinking and Qwen execution engines.

6|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/kmshihab7878/claude-code-setup --skill qwen-dispatch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qwen-dispatch
Source: https://github.com/kmshihab7878/claude-code-setup/tree/main/skills/qwen-dispatch
Command: npx skills add https://github.com/kmshihab7878/claude-code-setup --skill qwen-dispatch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route tasks between Claude-style thinking and Qwen execution to optimize the division of cognitive labor.

Core Features & Use Cases

  • Bidirectional task routing between Claude and Qwen engines based on task tier.
  • Supports thinking-only, planning, and auto-execute modes with the --think flag.
  • Escalation and model selection controls for optimized workloads across teams.

Quick Start

Run qwen-dispatch with a test task to route it to Claude or Qwen based on the task's complexity.

Frequently Asked Questions about qwen-dispatch

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

FAQPage Schema
How do I route AI tasks between different models for planning and execution?

You can route AI tasks by using bidirectional routing to direct Claude-style thinking for planning and Qwen engines for execution, optimizing the division of cognitive labor based on task complexity.

What is the best way to automate code reviews and documentation with tiered AI thinking?

Automating code reviews and documentation with tiered AI thinking involves applying plan-to-execute workflows that enforce model selection and contextual thinking storage for reproducible routing across software engineering tasks.

Does qwen-dispatch support escalating complex software engineering tasks to a more advanced model?

Yes, qwen-dispatch supports escalation and model selection controls, allowing you to manually or automatically escalate complex software engineering tasks to optimized workloads across different tiers.

How do I use the --think flag to control workflow routing in AI orchestration?

Use the --think flag in AI orchestration to switch between thinking-only mode for generating plans and auto-execute mode to let the Qwen execution engine directly process the software engineering tasks.

When should I not use bidirectional routing for code generation and exploration tasks?

You should not use bidirectional routing for code generation and exploration tasks when your workload does not require tiered thinking, contextual thinking storage, or strict plan-to-execution workflows.