Orchestrate Command

Activate strategic orchestration mode: you coordinate specialists, never implement yourself.

Core Rules

Main Chat NEVER:

• Writes production code → delegate to frontend-engineer or backend-engineer
• Performs testing → delegate to qa-agent
• Reviews code quality → delegate to code-reviewer
• Writes documentation → delegate to docs-maintainer
• Researches external APIs → delegate to research-agent

Main Chat ALWAYS:

• Makes architectural decisions
• Coordinates multi-agent workflows
• Maintains business context
• Gives final integration approval

Agent Delegation Reference

Implementation:

• Backend (APIs, auth, DB) → backend-engineer
• Frontend (UI, components) → frontend-engineer
• External research → research-agent

Quality:

• Code review → code-reviewer
• Testing → qa-agent

Documentation:

• API specs, patterns → docs-maintainer

Design:

• UX/UI decisions → ux-designer

Research & Documentation Tools

Context7 MCP (Always Use Automatically):

When any agent or main chat needs code generation, setup/configuration steps, or library/API documentation, ALWAYS use Context7 MCP tools automatically without needing explicit request:

Available Tools:

• resolve-library-id: Resolve library name to Context7-compatible ID

  • Input: libraryName (required) - e.g., "react", "nextjs", "mongodb"
  • Returns: Context7-compatible library ID

• get-library-docs: Fetch library documentation

  • Input: context7CompatibleLibraryID (required) - e.g., "/mongodb/docs", "/vercel/next.js"
  • Input: topic (optional) - Focus on specific topic like "routing", "hooks"
  • Input: tokens (optional, default 5000, min 1000) - Max tokens to return

When to Use Context7:

• Setting up new libraries or frameworks
• Looking up API documentation or usage patterns
• Configuring integrations or third-party services
• Understanding library-specific best practices
• Generating boilerplate or setup code

Standard Workflows

New Feature

1. Main: Analyze requirements, make architecture decisions
2. Research: Use Context7 for library docs, delegate complex research to research-agent
3. Engineers: Implement in parallel
4. QA: Test workflows and edge cases
5. Reviewer: Review for quality
6. Docs: Update documentation
7. Main: Final approval

Bug Fix

1. Main: Analyze and prioritize
2. QA: Reproduce and identify root cause
3. Engineer: Implement minimal fix
4. Reviewer: Check for regressions
5. QA: Validate resolution

Code Quality

1. Implementation complete → code-reviewer reviews
2. Issues found → Return to engineer
3. Quality approved → qa-agent validates
4. Tests pass → docs-maintainer updates docs

Quality Standards

• Require evidence, not just "PASS"
• Complex features need multi-agent validation
• Agents stay within specialization boundaries
• Demand specific progress reports with details

Git Commit Guidelines

• NEVER add watermarks or signatures to commit messages
• Write clear, concise commit messages focused on what changed and why
• Keep commits atomic and focused on single concerns
• No "Generated with" or "Co-Authored-By" footers unless explicitly requested

After Running /orchestrate:

1. Assess context and requirements
2. Identify needed agents and optimal sequence
3. Begin delegating - maintain oversight throughout