qwen-orchestrator
Health Pass
- License Γ’β¬β License: MIT
- Description Γ’β¬β Repository has a description
- Active repo Γ’β¬β Last push 0 days ago
- Community trust Γ’β¬β 31 GitHub stars
Code Fail
- execSync Γ’β¬β Synchronous shell command execution in mcp-server/src/orchestration-tools.ts
Permissions Pass
- Permissions Γ’β¬β No dangerous permissions requested
No AI report is available for this listing yet.
π Multi-agent orchestration for Qwen Code CLI. 24 specialized AI agents and 82+ skills working as a professional dev department. Built for Alibaba's open-source AI coding assistant.
Qwen Orchestrator β Multi-Agent AI Development Team for Qwen Code
English Β· EspaΓ±ol Β· δΈζ Β· ζ₯ζ¬θͺ Β· νκ΅μ΄ Β· PortuguΓͺs Β· FranΓ§ais Β· Ψ§ΩΨΉΨ±Ψ¨ΩΨ©
π€ The enterprise-grade multi-agent AI orchestration extension exclusively for Qwen Code CLI
Turn your AI coding assistant into a full software development department β 24 specialized agents, 82 professional skills, 6 slash commands, persistent memory, and MCP tool integration.
Author: Omar-Obando Β· License: MIT Β· Version: 0.0.6
π Table of Contents
- What is Qwen Orchestrator?
- Quick Install
- Quick Start
- Key Features
- Agent Team (24 Specialized Agents)
- Skills (82 Professional Skills)
- Commands (6 Slash Commands)
- How It Works
- Installation Guide
- Model Configuration
- CLI Mode Recommendations
- Advanced Tools
- Integrations
- Quality Standards
- Project Structure
- First Usage Examples
- Documentation
- Author
- Keywords
β‘ What is Qwen Orchestrator?
Qwen Orchestrator is a powerful extension built exclusively for Qwen Code β the open-source AI coding CLI by Alibaba. It transforms a single AI coding assistant into a coordinated team of 24 specialized AI agents that work together like a professional software development department.
Why Qwen Orchestrator?
Imagine having an entire engineering team at your fingertips: a Commander that orchestrates, a Planner that architects, Frontend and Backend Developers that code in parallel, a Reviewer that gatekeeps quality, a QA Engineer that tests, a Cybersecurity Engineer that audits vulnerabilities, a DevOps Engineer that deploys β and 16 more specialists, all coordinated automatically.
No other AI coding extension provides this level of professional multi-agent orchestration.
Built Exclusively For
|
|
Qwen Code by QwenLM / Alibaba β The open-source AI-powered coding assistant CLI that supports multiple LLM providers (Qwen, DeepSeek, OpenAI, Anthropic, local models). Qwen Orchestrator is a community-built extension and is not affiliated with or endorsed by Alibaba. |
β οΈ This extension ONLY works with Qwen Code CLI. It is NOT a standalone tool, NOT a VS Code extension, and NOT compatible with other AI coding assistants. If you don't have Qwen Code installed, install it first.
β οΈ IDE Compatibility Notice: This extension has NOT been tested with Visual Studio, VS Code extensions, JetBrains IDEs, or any integrations outside of the Qwen Code CLI. It is designed exclusively for the Qwen Code terminal/CLI experience.
π Quick Install
qwen extensions install https://github.com/Omar-Obando/qwen-orchestrator
That's it! The extension automatically registers all 24 agents, 82 skills, 6 commands, and the MCP Memory Server.
π See the full Installation Guide for manual install, MCP tools server setup, and troubleshooting.
π― Quick Start
Once installed, just type in your Qwen Code CLI:
/orchestrator Create a REST API for user management
/orchestrator Build a responsive e-commerce website
/plan Design a database schema for a blog
/review Check all authentication controllers
/test Run all tests in the current project
/deploy Deploy the application to production
The /orchestrator command is the main entry point. It activates the full 24-agent team with the complete professional workflow:
- CLARIFY β Asks targeted questions if anything is ambiguous
- DISCOVER β Scans your project, detects tech stack, reads configs
- PLAN β Decomposes the mission into milestones with parallel execution groups
- EXECUTE β Launches specialized agents simultaneously for max throughput
- VERIFY β Reviewer + QA confirm everything works, zero regressions
- DELIVER β Summary of what was built, changed, and evidence
π Key Features
| Feature | Description |
|---|---|
| 24 Specialized Agents | Commander, Planner, Frontend/Backend Devs, Reviewer, QA, PM, DevOps, Security, and more |
| 82 Professional Skills | TDD, security audit, anti-pattern detection, design system, SQL best practices, Docker, Kubernetes, and 75 more |
| 6 Slash Commands | /orchestrator, /orchestrate, /plan, /review, /test, /deploy |
| Ask Before Building | Agents ask clarifying questions via AskUserQuestion before writing code |
| Parallel Execution | Commander delegates tasks to multiple agents simultaneously |
| Persistent Memory | Knowledge Graph via MCP Memory Server stores decisions across sessions |
| Zero Model Lock-In | Works with Qwen, DeepSeek, OpenAI, Anthropic, or any local model |
| Multi-Language | TypeScript, PHP (Laravel), Python (Django), Dart (Flutter), Rust, Go, Java, C# |
| Loop Protection | Monitor agent detects and breaks LLM infinite loops automatically |
| Quality Gates | Reviewer is the ONLY agent that can approve tasks |
| Security First | OWASP Top 10 compliance via security-audit skill and Reviewer agent |
| No Mockups | Agents are forbidden from writing stubs or placeholders |
| Compaction Recovery | State persists to .qwen-orchestrator/ β survives context window compression |
π₯ Agent Team (24 Specialized Agents)
| # | Agent | Role | Superpower |
|---|---|---|---|
| 1 | Commander π΄ | Master Orchestrator | Parallel delegation, relentless execution |
| 2 | Planner π΅ | Research & Architecture | File-level planning, design decisions |
| 3 | Frontend Developer π΅ | UI/UX Implementation | Components, responsive, accessible, fast |
| 4 | Backend Developer π’ | Server-Side Logic | APIs, auth, caching, database ops |
| 5 | Reviewer π£ | Quality Gatekeeper | ONLY agent that can approve tasks |
| 6 | QA Engineer π | Quality Assurance | Test strategy, edge case discovery |
| 7 | Project Manager π΅ | Delivery Management | Scope control, risk assessment |
| 8 | Doc Researcher π£ | Context7 Knowledge | Live doc lookup, anti-hallucination |
| 9 | Tech Lead π‘ | Standards & Guidance | Module completeness, CRUD verification |
| 10 | Database Architect π’ | Data Layer Specialist | Schema design, migration safety |
| 11 | Product Owner π‘ | Business Value | User stories, acceptance criteria |
| 12 | DevOps Engineer π | Infrastructure | CI/CD, Docker, deployment automation |
| 13 | Code Quality Guard πΉ | Quality Sentinel | Syntax check, lint, typecheck |
| 14 | Monitor π‘οΈ | Loop Guardian | Detect/break LLM loops, runtime watchdog |
| 15 | SEO Specialist π΅ | SEO & Web Performance | Meta tags, structured data, Core Web Vitals |
| 16 | Tech Selector π£ | Technology Advisor | Framework/DB selection with pros/cons |
| 17 | Cybersecurity Eng. π΄ | Application Security | OWASP, threat modeling, dependency audit |
| 18 | Performance Eng. β‘ | Speed & Scale | Profiling, query optimization, load testing |
| 19 | Release Manager π·οΈ | Release & Versioning | SemVer, changelogs, rollback planning |
| 20 | API Specialist π | API & Integration | REST/GraphQL, versioning, third-party APIs |
| 21 | Mobile Engineer π± | Mobile Apps | Flutter, React Native, offline-first |
| 22 | Localization Eng. π | i18n/L10n | Multi-language, RTL, cultural adaptation |
| 23 | Documenter π | Technical Writing | README, API docs, ADRs, knowledge base |
| 24 | Skill Creator π οΈ | Skill Authoring | Skill creation, documentation, testing |
π οΈ Skills (82 Professional Skills)
Containerization & Orchestration
| Skill | Purpose |
|---|---|
| Docker Containerization | Multi-stage builds, security hardening, image optimization, Docker Compose |
| Kubernetes Orchestration | Deployments, HPA, service mesh, ingress, GitOps with ArgoCD/Flux |
Infrastructure as Code
| Skill | Purpose |
|---|---|
| Terraform IaC | Modules, state management, workspaces, Sentinel policies, Terratest |
CI/CD Automation
| Skill | Purpose |
|---|---|
| GitHub Actions CI/CD | Workflows, matrices, environments, caching, composite actions, security |
Caching & Performance
| Skill | Purpose |
|---|---|
| Redis Caching | Data structures, caching patterns, session management, pub/sub, Lua scripting |
API Design
| Skill | Purpose |
|---|---|
| GraphQL API Design | Schema design, resolvers, DataLoader, pagination, Apollo Federation |
Multi-Platform
| Skill | Purpose |
|---|---|
| Multi-Platform Dev | Cross-platform commands, path handling, line endings, permissions, package managers |
LLM & Agents
| Skill | Purpose |
|---|---|
| LangGraph | Agent workflows, state management, multi-agent systems |
| LangChain | LLM chains, agents, tools, memory, RAG |
| Qwen Agent | Qwen-specific agent development and integration |
| LLM Integrations | Multi-provider LLM integration (OpenAI, Anthropic, Google, etc.) |
Cloud Platforms
| Skill | Purpose |
|---|---|
| Vercel Deployment | Serverless functions, edge computing, Next.js optimization |
| Cloudflare Pages | Edge functions, global distribution, caching |
| Cloudflare Workers | Edge computing, request/response manipulation |
| AWS Serverless | Lambda, API Gateway, SAM, event-driven architectures |
SEO
| Skill | Purpose |
|---|---|
| SEO LLM | Optimization for ChatGPT, Perplexity, Gemini, Claude, Bing AI, Qwen |
| Technical SEO | Site speed, mobile optimization, structured data, Core Web Vitals |
Leadership & Architecture
| Skill | Purpose |
|---|---|
| Strategic Leadership | Team management, decision-making, stakeholder alignment |
| Requirements Engineering | Use cases, user stories, acceptance criteria |
| Microservices Architecture | Domain-driven design, service boundaries, event-driven communication |
| Technology Evaluation | Framework/DB selection, pros/cons analysis |
Product & Team
| Skill | Purpose |
|---|---|
| Product Owner | Backlog management, user stories, sprint planning |
| Scrum Master | Ceremony facilitation, team coaching, impediment removal |
Software Development
| Skill | Purpose |
|---|---|
| Testing Strategy | Test pyramid, coverage targets, automation |
| Security Auditor | OWASP Top 10, vulnerability assessment, compliance |
| DevOps Pipeline | CI/CD design, deployment strategies, IaC |
| Architecture Patterns | Layered, DDD, microservices, event-driven, CQRS |
| Documentation | README, API docs, ADRs, knowledge base |
| Debugging | Systematic investigation, hypothesis-driven debugging |
| Refactoring | Code smell detection, safe transformations |
Security & Quality
| Skill | Purpose |
|---|---|
| Security Code Review | OWASP Top 10, vulnerability patterns, secure coding |
| Threat Modeling | STRIDE, DREAD, attack trees, threat identification |
| Test Automation | Framework design, page object patterns, parallel execution |
| Load Testing | Load, stress, endurance, spike testing |
| Code Review | OWASP + SOLID + Clean Code systematic review |
Database & Data
| Skill | Purpose |
|---|---|
| Database Design | Schema design, relationships, indexing strategies |
| Database Security | Encryption, access control, audit logging, compliance |
| SQL Best Practices | Query optimization, indexing, N+1 prevention |
| SQL Query Assistant | Query assistance, best practices, optimization |
Frontend & Mobile
| Skill | Purpose |
|---|---|
| Accessibility | WCAG 2.1 AA, semantic HTML, ARIA, keyboard navigation |
| Design System | Color palettes, typography, spacing, component architecture |
| Website Redesign | URL/screenshot-based redesign, analysis workflow |
| Flutter Web | Responsive layouts, adaptive widgets, state management |
| Mobile Performance | App optimization, startup time, memory usage |
| Offline-First | Local storage, sync, conflict resolution |
Backend & APIs
| Skill | Purpose |
|---|---|
| API Design | RESTful standards, response envelopes, pagination |
| API Documentation | OpenAPI specification, Swagger, GraphQL schemas |
| Third-Party Integration | Stripe, PayPal, AWS, Google, Twilio |
| Laravel | Eloquent ORM, Form Requests, queues, API patterns |
| NestJS | Modules, guards, pipes, interceptors, request lifecycle |
| Supabase | RLS policies, Edge Functions, auth, auto-generated APIs |
DevOps & Infrastructure
| Skill | Purpose |
|---|---|
| Disaster Recovery | Backup strategies, restore procedures, failover, RTO/RPO |
| Release Workflow | SemVer, changelogs, staging, production, rollback |
| Git Workflow | Branching strategies, commit conventions, PR templates |
| Deployment | CI/CD, Docker, release management |
LLM-Specific
| Skill | Purpose |
|---|---|
| Anti-Hallucination | Source verification, evidence-based claims, validation |
| Loop Detection | LLM loop detection, tool call loops, escape routes |
| Context7 Docs | Live documentation lookup via Context7 MCP |
| Compaction Recovery | Context preservation across session compaction |
Project & Team
| Skill | Purpose |
|---|---|
| Agile Project Management | Scrum ceremonies, backlog grooming, sprint planning |
| User Story Mapping | Story mapping, epic breakdown, timeline visualization |
| CRUD Completeness | Create, Read, Update, Delete patterns, validation |
| Project Conventions | Project structure, coding standards, conventions |
| ERP/SaaS Organization | Large project organization, module structure |
Localization
| Skill | Purpose |
|---|---|
| Translation Workflow | Translation memory, machine translation, TMS |
| Multi-Language | i18n, l10n patterns, RTL support |
Additional Skills
| Skill | Purpose |
|---|---|
| Domain-Driven | DDD patterns, bounded contexts, aggregates, value objects |
| Performance | Profiling, optimization, benchmarks |
| TDD Workflow | Test-Driven Development (Red/Green/Refactor) |
| Security Audit | OWASP Top 10 vulnerability detection |
| Agent Task Coordinator | Agent coordination, MCP protocol |
| Skill Creation | Skill authoring, documentation, testing |
| Multi-Channel Funnels | Marketing funnels, conversion optimization |
| Architecture | System design, patterns, trade-offs |
| Code Quality | Linting, formatting, type checking |
| Monitoring | Observability, logging, alerting |
| Compliance | GDPR, HIPAA, SOC 2, PCI-DSS |
| Testing | Unit, integration, E2E testing |
β¨οΈ Commands (6 Slash Commands)
| Command | Description |
|---|---|
/orchestrator [goal] β |
Main entry point β Full team with clarity protocol (asks questions first) |
/orchestrate [mission] |
Direct mission execution β no clarity questions, just builds |
/plan [feature] |
Create implementation plan only β research + architecture |
/review [target] |
Comprehensive code review β security, quality, patterns |
/test [target] |
Execute and analyze test suite β coverage, gaps, edge cases |
/deploy [target] |
Deploy with pre/post verification β CI/CD, rollback plan |
When to use
/orchestratorvs/orchestrate?
/orchestratorβ When starting a new feature, project, or complex task. The team will ask clarifying questions first./orchestrateβ When you already know exactly what you want and just need it executed fast.
π§ How It Works
Execution Flow
User types /orchestrator "Build a payment system"
β
βΌ
βββββββββββββββββββββββ
β COMMANDER π΄ β
β Clarifies scope β
β via AskUserQuestionβ
ββββββββββββ¬βββββββββββ
β
ββββββββββββΌβββββββββββ
β PLANNER π΅ β
β Analyzes project β
β Creates milestones β
ββββββββββββ¬βββββββββββ
β
ββββββββββββββββΌβββββββββββββββββββ
βΌ βΌ βΌ
βββββββββββ ββββββββββββ ββββββββββββββββββββ
βFE DEV β βBE DEV β βDB ARCHITECT β
βTask 1 β βTask 2 β βSchema + Migrationβ
ββββββ¬βββββ ββββββ¬ββββββ ββββββββββ¬ββββββββββ
β β β
βΌ βΌ βΌ
βββββββββββ ββββββββββββ ββββββββββββββββββββ
βREVIEWER β βQA ENG β βCODE QUALITY GUARDβ
βApproves β βTests β βLint + Typecheck β
ββββββ¬βββββ ββββββ¬ββββββ ββββββββββ¬ββββββββββ
β β β
ββββββββββββββΌββββββββββββββββββ
βΌ
βββββββββββββββββββββββ
β COMMANDER π΄ β
β Concludes mission β
β Delivers summary β
βββββββββββββββββββββββ
User Clarity: Ask Before Building
The orchestrator never assumes what you want. When a mission starts, the Commander and Planner agents use the AskUserQuestion tool to clarify requirements before writing code.
Example interaction:
π€ User: /orchestrator Build an e-commerce checkout
π€ Commander: I need to clarify a few things before planning:
π Payment Provider (Question 1/3)
Which payment gateway should I integrate?
β Stripe β Industry standard, great API, supports subscriptions
β PayPal β Widely trusted, good international support
β MercadoPago β Best for Latin American markets
π Checkout Flow (Question 2/3)
What type of checkout experience?
β Single Page β All steps on one page (simpler, faster)
β Multi-Step β Separate pages per step (more controlled)
π Guest Checkout (Question 3/3)
Should users be able to checkout without an account?
β Yes β Lower friction, higher conversion
β No β Required account, better for retention
π€ User selects: MercadoPago β Multi-Step β Yes
π€ Commander: Perfect. Planning checkout with MercadoPago, multi-step flow, guest support.
Agents that ask questions:
| Agent | When It Asks |
|---|---|
| Commander | Before every mission β scope, priorities, constraints |
| Planner | Before architecture decisions β tech stack, patterns |
| Product Owner | When defining user stories β acceptance criteria, edge cases |
| QA Engineer | When designing test strategy β critical paths, thresholds |
| Project Manager | When scoping β deadlines, risk tolerance, resources |
| Tech Selector | When tech stack is unspecified β presents frameworks, databases, languages with pros/cons |
| SEO Specialist | When building web projects β target audience, content type, region |
Tip: You can always provide full details upfront and skip questions. The agents only ask when they detect ambiguity.
Architecture Diagram
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β QWEN ORCHESTRATOR v0.0.6 β
β by Omar-Obando (GitHub) β
β βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ£
β β
β βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β
β β COMMANDER π΄ β β
β β "I orchestrate. I never stop until done." β β
β β EXPLORE β LEARN β ADAPT β ACT β VERIFY β DELIVER β β
β ββββββββ¬ββββββββββ¬ββββββββββ¬ββββββββββ¬βββββββββββββββββββββββββββββ β
β β β β β β
β ββββββββΌβββ ββββββΌβββββββ ββΌβββββββββ ββΌβββββββββββββββ β
β β PLANNER β βFE DEV+BE β βREVIEWER β β QA ENGINEER β β
β β π΅ β β π’π β β π£ β β π β β
β βResearch β β TDD Code β βGatekeep β βTest Strategy β β
β βDesign β β Deliver β βApprove β βCoverage β β
β βββββββββββ βββββββββββββ βββββββββββ βββββββββββββββββ β
β β β β β β
β ββββββββΌββββββββββΌββββββββββΌββββββββββΌβββββββββββββββββββββββββββ β
β β PROJECT MANAGER π΅ β β
β β Scope Β· Risk Β· Progress Β· Delivery β β
β ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β
β β
β ββββββββββββββββ ββββββββββββββββ βββββββββββββββββββββββββββββββ β
β βDOC RESEARCHERβ β TECH LEAD β β DATABASE ARCHITECT β β
β β π£ Magenta β β π‘ Gold β β π’ Teal β β
β β Context7 β β CRUD Verify β β Schema & Migration β β
β ββββββββββββββββ ββββββββββββββββ βββββββββββββββββββββββββββββββ β
β β
β ββββββββββββββββ ββββββββββββββββ βββββββββββββββββββββββββββββββ β
β βPRODUCT OWNER β βDEVOPS ENGINEERβ β CODE QUALITY GUARD β β
β β π‘ Amber β β π Slate β β πΉ Rose β β
β βUser Stories β β CI/CD β β Syntax Β· Lint Β· Types β β
β ββββββββββββββββ ββββββββββββββββ βββββββββββββββββββββββββββββββ β
β β
β Agents: 24 | Skills: 82 | Commands: 6 | MCP Tools: 7 | Languages: 8+ β
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
π¦ Installation Guide
Quick Install (Recommended)
qwen extensions install https://github.com/Omar-Obando/qwen-orchestrator
The extension automatically:
- β Registers all 24 specialized agents
- β Loads all 82 professional skills
- β Activates all 6 slash commands
- β Sets up the MCP Memory Server for persistent knowledge
- β Configures everything for immediate use
Manual Install
1. Get the extension:
git clone https://github.com/Omar-Obando/qwen-orchestrator.git
2. Tell Qwen Code about it. Add to your Qwen Code configuration (~/.qwen/settings.json):
{
"extensions": ["/full/path/to/qwen-orchestrator"]
}
π‘ To find your full path, run
pwdinside the cloned directory.
MCP Tools Server (Optional)
For advanced features like mission status checking and agent roster tools:
cd qwen-orchestrator
npm install
npm run build
Then add to your Qwen Code MCP configuration:
{
"mcpServers": {
"qwen-orchestrator": {
"command": "node",
"args": ["./qwen-orchestrator/mcp-server/dist/index.js"]
}
}
}
Available MCP tools:
| Tool | Purpose |
|---|---|
get_mission_status |
Get current mission progress |
validate_project |
Validate project structure and health |
generate_todo |
Generate structured TODO from mission description |
get_agent_roster |
List all 24 agents with capabilities |
context7_resolve_library |
Resolve Context7 library IDs |
check_crud_completeness |
Verify full CRUD for all entities |
create_checkpoint |
Create state checkpoint for compaction recovery |
Troubleshooting
| Problem | Solution |
|---|---|
| "Command not found" after install | Restart Qwen Code CLI to reload extensions |
| "Permission denied" on npm commands | Windows: run terminal as Administrator. Mac/Linux: use sudo if needed |
| Where are session files stored? | .qwen-orchestrator/ directory in your project |
| Extension not loading | Verify path in settings.json is absolute and correct |
Need more help? Open an issue on GitHub.
βοΈ Model Configuration
By default, all agents use your Qwen Code default model. There is no hardcoded model β zero lock-in.
β οΈ CRITICAL: Set Temperature to 0.1 (TP 0.1) on ALL models
For the orchestrator to follow instructions strictly and reliably, every model used by any agent MUST be configured with Temperature 0.1 (TP 0.1). Higher temperatures introduce randomness that causes agents to deviate from their assigned roles, ignore constraints, hallucinate tools, or produce inconsistent output.
Why TP 0.1?
- Ensures strict adherence to system prompts and agent instructions
- Eliminates creative drift that breaks multi-agent coordination
- Produces deterministic, reproducible results across sessions
- Prevents agents from inventing tools, files, or behaviors
How to configure:
{ "modelConfig": { "temperature": 0.1 } }This applies to every model β Qwen, DeepSeek, OpenAI, Anthropic, local models, or any other provider. If your provider or model does not support temperature configuration, consider switching to one that does. TP 0.1 is not optional β it is a hard requirement for reliable multi-agent orchestration.
β οΈ CRITICAL: Enable YOLO Mode for Full Agent Autonomy
For agents to operate autonomously without requiring manual approval on every file edit, shell command, or tool invocation, you MUST set Qwen Code CLI to YOLO mode. Without it, every agent action will prompt for confirmation, making multi-agent orchestration impractical.
Why YOLO mode?
- Agents execute tasks without interruption β no per-action confirmation dialogs
- Enables true parallel execution across multiple agents simultaneously
- Required for the Commander to delegate and forget without getting stuck on prompts
- Without it, a single agent task can require dozens of manual approvals
How to configure:
# Set YOLO mode in Qwen Code CLI /yoloAlternative modes:
Mode Behavior Recommended for YOLO Full autonomy β no confirmations. Required for orchestrator. Production use Auto-Edit Auto-approves file edits, confirms shell commands. Development / testing Default Confirms every file edit and shell command. Learning / evaluation Plan Read-only β no file writes allowed. Planning-only sessions YOLO mode is not optional for production orchestrator use. Without it, you will be prompted to confirm every single tool call across all 24 agents, making the orchestrator unusable at scale.
Using the default model (recommended)
Just install and use. Every agent picks up whatever model you have configured in Qwen Code.
Setting a specific model per agent
Edit the agent's .md file in agents/ and uncomment the model line:
---
name: commander
# ... other fields ...
# model: uncomment below to override the user's default model
model: qwen-max
---
Recommended models per role
| Agent | Recommended Model | Why |
|---|---|---|
| Commander | qwen-max or qwen-plus |
Needs strong reasoning for orchestration |
| Planner | qwen-max or qwen-plus |
Needs strong analysis for architecture |
| Frontend Developer | qwen3-coder-plus |
Optimized for code generation |
| Backend Developer | qwen3-coder-plus |
Optimized for code generation |
| Reviewer | qwen-max |
Needs deep understanding for quality gates |
| QA Engineer | qwen-plus |
Balanced for test strategy |
| Code Quality Guard | qwen-plus |
Fast for syntax/lint checks |
| All others | User's default | No special needs |
Any model supported by your Qwen Code installation works β including DeepSeek, OpenAI, Anthropic, or local models.
ποΈ CLI Mode Recommendations
For maximum autonomy, set your Qwen Code CLI mode before running /orchestrator:
| CLI Mode | Setting | What Happens |
|---|---|---|
| Auto-Edit | auto-edit |
Agents edit/write freely. User confirms shell. Recommended. |
| YOLO | yolo |
Full autonomy. No confirmations. Maximum speed. |
| Default | default |
User confirms every edit. Slower but maximum control. |
| Plan | plan |
Planning only β agents can't write files. |
Agents intentionally have no
approvalMode,runConfig, orbackgroundfields β you control autonomy from the CLI, not the extension.
π§ Advanced Tools
Inter-Agent Communication
The Commander can send messages to background agents mid-task:
SendMessage({ task_id: "worker-auth", message: "User clarified: use JWT, not sessions." })
Real-Time Monitoring
The DevOps Engineer can watch long-running processes:
Monitor({ command: "docker compose logs -f app", description: "Watch app logs during deploy" })
Scheduled Tasks
Schedule recurring quality checks and reports:
CronCreate({ cron: "0 6 * * 1-5", prompt: "Run security audit", recurring: true })
Agent-Tool Matrix
| Tool | Cmd | Plan | FE | BE | Rev | QA | PM | Doc | TL | DB | PO | Dev | CQG | Mon | SEO | TSel |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AskUserQuestion | β | β | β | β | β | β | β | β | ||||||||
| Agent (sub-agents) | β | β | ||||||||||||||
| Skill (load skill) | β | |||||||||||||||
| SendMessage | β | β | β | |||||||||||||
| Monitor (watchdog) | β | β | β | |||||||||||||
| TaskStop | β | β | ||||||||||||||
| CronCreate/List | β | β | β | β | ||||||||||||
| ExitPlanMode | β | |||||||||||||||
| SaveMemory | β | β | β | β | β | β | β | β | β | β | β | β | β | |||
| Lsp (diagnostics) | β | β | β | β | β | β | β | β | β | |||||||
| WebFetch | β | β | β | β | β | β | β | β | β | β | β | β | β | β | β |
π Integrations
Context7 (Optional)
Context7 provides real-time, version-specific documentation.
With Context7: Doc Researcher fetches live docs, zero hallucination on API signatures.
Without Context7: Agents fall back to web search and training knowledge β no errors.
To install, add to your Qwen Code MCP configuration:
{
"mcpServers": {
"context7": {
"command": "npx",
"args": ["-y", "@upstash/context7-mcp@latest"]
}
}
}
MCP Memory Server
The @modelcontextprotocol/server-memory MCP server provides a Knowledge Graph that persists across sessions.
What it stores:
- Project decisions: Database choice, framework, architecture patterns
- User preferences: CSS framework, naming conventions, dark/light mode
- Architecture records: Component hierarchy, API conventions, deployment targets
- Session continuity: Last task, next step, known issues
How agents use it:
create_entities({
entities: [{ name: "database", entityType: "decision",
observations: ["PostgreSQL 16", "RLS enabled", "UUID primary keys"] }]
})
read_graph({})
The Memory MCP server is configured in qwen-extension.json and runs automatically. No additional setup needed.
UI/UX Skills (Recommended)
The Frontend Developer agent can leverage external UI/UX repos for design intelligence:
| Skill | Install | What It Provides |
|---|---|---|
| UI UX Pro Max | npx uipro-cli init |
161 reasoning rules, 67 UI styles, design system generator, domain search |
| Designer Skills | /plugin marketplace add Owl-Listener/designer-skills |
87 skills, 27 commands across 8 design plugins |
| Taste Skill | npx skills add https://github.com/Leonxlnx/taste-skill |
Anti-slop frontend framework β premium layout, typography, motion, spacing |
β Quality Standards
Every line of code produced by the orchestrator meets:
| Standard | Requirement |
|---|---|
| Complexity | β€ 10 cyclomatic per function |
| Size | β€ 40 lines per function, β€ 4 parameters |
| Types | Strict types, no any |
| Testing | TDD mandatory, 80%+ coverage |
| Security | OWASP Top 10 compliance |
| SQL | Uppercase keywords, one column per line, indented JOINs, N+1 prevention |
| Review | Multi-dimensional code review before merge |
| Languages | Not TypeScript-only β adapts to project's tech stack |
π Project Structure
qwen-orchestrator/
βββ qwen-extension.json # Extension manifest
βββ package.json # NPM package config
βββ AGENTS.md # Agent operational rules
βββ LICENSE # MIT License
βββ CHANGELOG.md # Release history
βββ SECURITY.md # Security policy
β
βββ agents/ # 24 Agent definitions
β βββ commander.md
β βββ planner.md
β βββ frontend-developer.md
β βββ backend-developer.md
β βββ reviewer.md
β βββ qa-engineer.md
β βββ project-manager.md
β βββ doc-researcher.md
β βββ tech-lead.md
β βββ database-architect.md
β βββ product-owner.md
β βββ devops-engineer.md
β βββ code-quality-guard.md
β βββ monitor.md
β βββ seo-specialist.md
β βββ tech-selector.md
β βββ cybersecurity-engineer.md
β βββ performance-engineer.md
β βββ release-manager.md
β βββ api-specialist.md
β βββ mobile-engineer.md
β βββ localization-engineer.md
β βββ documenter.md
β βββ skill-creator.md
β
βββ skills/ # 82 Skill definitions
β βββ docker-containerization/
β βββ kubernetes-orchestration/
β βββ terraform-iac/
β βββ github-actions-cicd/
β βββ redis-caching/
β βββ graphql-api-design/
β βββ multi-platform-dev/
β βββ langgraph/
β βββ langchain/
β βββ qwen-agent/
β βββ llm-integrations/
β βββ vercel-deployment/
β βββ cloudflare-pages/
β βββ cloudflare-workers/
β βββ aws-serverless/
β βββ seo-llm/
β βββ technical-seo/
β βββ strategic-leadership/
β βββ requirements-engineering/
β βββ microservices-architecture/
β βββ technology-evaluation/
β βββ product-owner/
β βββ scrum-master/
β βββ testing-strategy/
β βββ security-auditor/
β βββ devops-pipeline/
β βββ architecture-patterns/
β βββ documentation/
β βββ debugging/
β βββ refactoring/
β βββ security-code-review/
β βββ threat-modeling/
β βββ test-automation/
β βββ load-testing/
β βββ code-review/
β βββ database-design/
β βββ database-security/
β βββ sql-best-practices/
β βββ sql-query-assistant/
β βββ accessibility/
β βββ design-system/
β βββ website-redesign/
β βββ flutter-web/
β βββ mobile-performance/
β βββ offline-first/
β βββ api-design/
β βββ api-documentation/
β βββ third-party-integration/
β βββ laravel/
β βββ nestjs/
β βββ supabase/
β βββ disaster-recovery/
β βββ release-workflow/
β βββ git-workflow/
β βββ deployment/
β βββ anti-hallucination/
β βββ loop-detection/
β βββ context7-docs/
β βββ compaction-recovery/
β βββ agile-project-management/
β βββ user-story-mapping/
β βββ crud-completeness/
β βββ project-conventions/
β βββ erp-saas-organization/
β βββ translation-workflow/
β βββ multi-language/
β βββ domain-driven/
β βββ performance/
β βββ tdd-workflow/
β βββ security-audit/
β βββ agent-task-coordinator/
β βββ skill-creation/
β βββ multi-channel-funnels/
β βββ architecture/
β βββ code-quality/
β βββ monitoring/
β βββ compliance/
β βββ testing/
β βββ debugging-skill/
β
βββ commands/ # 6 Slash commands
β βββ orchestrator.md
β βββ orchestrate.md
β βββ plan.md
β βββ review.md
β βββ test.md
β βββ deploy.md
β
βββ context/
β βββ QWEN.md
β
βββ mcp-server/src/
β βββ index.ts
β
βββ docs/
β βββ ARCHITECTURE.md
β βββ QUICK-START.md
β βββ INSTALLATION.md
β βββ HOOKS-BEST-PRACTICES.md
β βββ SUBAGENT-MONITORING.md
β βββ README.es.md
β βββ README.zh.md
β βββ README.ja.md
β βββ README.ko.md
β βββ README.pt.md
β βββ README.fr.md
β βββ README.ar.md
β
βββ scripts/
βββ setup.sh
π― First Usage Examples
Once installed, try these in your Qwen Code CLI:
/orchestrator Create a REST API for user management
/orchestrator Build a responsive e-commerce website with Stripe payments
/plan Design a database schema for a blog platform
/review Check all authentication controllers for security issues
/test Run all tests in the current project and report coverage gaps
/deploy Deploy the application to production with rollback plan
π Documentation
| Document | Description |
|---|---|
| ARCHITECTURE.md | Detailed architecture and design decisions |
| QUICK-START.md | Getting started guide |
| INSTALLATION.md | Full installation instructions |
| HOOKS-BEST-PRACTICES.md | Qwen Code hooks integration guide |
| SUBAGENT-MONITORING.md | Sub-agent monitoring and lifecycle |
| QWEN_CODE_PATTERNS.md | MCP servers, hooks, and session management |
| SECURITY.md | Security policy |
| CHANGELOG.md | Release history |
| AGENTS.md | Agent operational rules |
π€ Author
Omar Obando
- GitHub: @Omar-Obando
- License: MIT
π Keywords
qwen-code Β· qwen-code-extension Β· multi-agent Β· ai-agents Β· orchestration Β· ai-coding Β· ai-development Β· tdd Β· code-review Β· devops Β· cicd Β· mcp Β· model-context-protocol Β· ai-orchestrator Β· software-engineering Β· ai-assistant Β· coding-agent Β· enterprise-ai Β· multi-agent-system Β· ai-coding-assistant Β· qwen Β· deepseek Β· openai Β· flutter Β· laravel Β· nestjs Β· supabase Β· typescript Β· python Β· php Β· rust Β· golang Β· java Β· csharp Β· sql Β· security-audit Β· owasp Β· test-driven-development Β· code-quality Β· frontend Β· backend Β· mobile Β· devops Β· database Β· api-design Β· i18n Β· localization Β· seo Β· performance Β· refactoring Β· anti-patterns
Built with β€οΈ for the Qwen Code community
Reviews (0)
Sign in to leave a review.
Leave a reviewNo results found