A production-grade orchestrated agent system that breaks down complex development tasks into specialized workflows with adaptive escalation, quality gates, and requirement clarification.
π‘ Tip: Start with the Orchestrator agent - it will automatically delegate to the right specialists!
graph TB
User[π€ User Request]
User --> Clarifier
subgraph "Entry Point"
Clarifier["π Clarifier<br/>Claude Sonnet 4.5<br/><i>Seeks clarification</i>"]
end
Clarifier --> Orchestrator
subgraph "Coordination Layer"
Orchestrator["π― Orchestrator<br/>Claude Sonnet 4.5<br/><i>Delegates & coordinates</i>"]
end
Orchestrator --> Planner
subgraph "Planning Layer"
Planner["π Planner<br/>GPT-5.2<br/><i>Creates strategies</i>"]
end
Orchestrator --> DevTeam
Orchestrator --> Designer
Orchestrator --> DataEng
Orchestrator --> Specialist
subgraph "Development Team - Adaptive Escalation"
DevTeam["π¨βπ» Developer Agents"]
Junior["β‘ Junior Developer<br/>Gemini 3 Flash<br/><i>Quick fixes, simple tasks</i>"]
Frontend["π¨ Frontend Dev<br/>Gemini 3 Pro<br/><i>UI, components</i>"]
Backend["βοΈ Backend Dev<br/>Claude Opus 4.6<br/><i>APIs, databases</i>"]
Fullstack["π Fullstack Dev<br/>Gemini 3 Pro<br/><i>End-to-end features</i>"]
SrFrontend["π Senior Frontend<br/>GPT-5.2-Codex<br/><i>Complex UI architecture</i>"]
SrBackend["π Senior Backend<br/>Claude Opus 4.6<br/><i>Distributed systems</i>"]
SrFullstack["π Senior Fullstack<br/>GPT-5.2-Codex<br/><i>Complex integrations</i>"]
DevTeam --> Junior
DevTeam --> Frontend
DevTeam --> Backend
DevTeam --> Fullstack
Frontend -.escalate.-> SrFrontend
Backend -.escalate.-> SrBackend
Fullstack -.escalate.-> SrFullstack
end
subgraph "Design Layer"
Designer["π¨ Designer<br/>Gemini 3 Pro<br/><i>UI/UX design</i>"]
end
subgraph "Data Layer"
DataEng["π Data Engineer<br/>Claude Opus 4.6<br/><i>SQL, ETL, analytics</i>"]
end
subgraph "Specialist Agents"
Specialist["π§ Specialists"]
PromptWriter["βοΈ Prompt Writer<br/>Gemini 3 Pro<br/><i>LLM prompt optimization</i>"]
DevOps["βοΈ DevOps<br/>GPT-5.2-Codex<br/><i>Git, dependencies, deployment</i>"]
end
Orchestrator --> Reviewer
subgraph "Quality Gate"
Reviewer["β
Reviewer<br/>Claude Sonnet 4.5<br/><i>Code review, security</i>"]
end
Reviewer --> User
style Clarifier fill:#e1f5ff,stroke:#01579b,stroke-width:2px
style Orchestrator fill:#fff3e0,stroke:#e65100,stroke-width:3px
style Planner fill:#f3e5f5,stroke:#4a148c,stroke-width:2px
style Junior fill:#e8f5e9,stroke:#1b5e20,stroke-width:2px
style Frontend fill:#e3f2fd,stroke:#0277bd,stroke-width:2px
style Backend fill:#f3e5f5,stroke:#6a1b9a,stroke-width:2px
style Fullstack fill:#fff3e0,stroke:#ef6c00,stroke-width:2px
style SrFrontend fill:#bbdefb,stroke:#01579b,stroke-width:3px
style SrBackend fill:#e1bee7,stroke:#4a148c,stroke-width:3px
style SrFullstack fill:#ffe0b2,stroke:#e65100,stroke-width:3px
style Designer fill:#fce4ec,stroke:#880e4f,stroke-width:2px
style DataEng fill:#e0f2f1,stroke:#00695c,stroke-width:2px
style Reviewer fill:#fff9c4,stroke:#f57f17,stroke-width:2px
| Agent | Install | Model | Primary Role |
|---|---|---|---|
| π Clarifier | Claude Sonnet 4.5 | Requirements Analysis | |
| π― Orchestrator | Claude Sonnet 4.5 | Coordination | |
| π Planner | GPT-5.2 | Strategy | |
| β‘ Junior Developer | Gemini 3 Flash | Quick Fixes | |
| π¨ Frontend Developer | Gemini 3 Pro | Component Implementation | |
| βοΈ Backend Developer | Claude Opus 4.6 | API Logic & CRUD | |
| π Fullstack Developer | Gemini 3 Pro | End-to-End Features | |
| π Senior Frontend Developer | GPT-5.2-Codex | Complex UI Architecture | |
| π Senior Backend Developer | Claude Opus 4.6 | Distributed Systems | |
| π Senior Fullstack Developer | GPT-5.2-Codex | Complex Integrations | |
| π Data Engineer | Claude Opus 4.6 | Analytics & Data Pipelines | |
| π¨ Designer | Gemini 3 Pro | Visual Design & Mockups | |
| βοΈ Prompt Writer | Gemini 3 Pro | Prompt Engineering | |
| βοΈ DevOps | GPT-5.2-Codex | Operations | |
| β Reviewer | Claude Sonnet 4.5 | Quality Assurance |
sequenceDiagram
actor User
participant C as π Clarifier<br/>Sonnet 4.5
participant O as π― Orchestrator<br/>Sonnet 4.5
participant P as π Planner<br/>GPT-5.2
participant JD as β‘ Junior Dev<br/>Gemini Flash
participant R as β
Reviewer<br/>Sonnet 4.5
User->>C: Fix typo: "Submitt" β "Submit"
C->>O: β Clear request
O->>P: Create plan for typo fix
P->>O: Single task: Update SubmitButton.tsx
O->>JD: Fix typo in button label
JD->>JD: Update file
JD->>O: β Complete
O->>R: Review changes
R->>O: β No issues found
O->>User: Typo fixed in submit button
sequenceDiagram
actor User
participant C as π Clarifier<br/>Sonnet 4.5
participant O as π― Orchestrator<br/>Sonnet 4.5
participant P as π Planner<br/>GPT-5.2
participant D as π¨ Designer<br/>Gemini Pro
participant FE as π¨ Frontend Dev<br/>Gemini Pro
participant SFE as π Senior Frontend<br/>Codex
participant R as β
Reviewer<br/>Sonnet 4.5
User->>C: Add dark mode to the app
C->>O: β Clear - theme toggle with persistence
O->>P: Create dark mode implementation plan
P->>O: Phase 1: Design<br/>Phase 2: Core (context, toggle)<br/>Phase 3: Apply theme
Note over O,D: Phase 1 - Design
par Design Tasks (Parallel)
O->>D: Create dark mode color palette
O->>D: Design toggle UI component
end
D->>O: β Design complete
Note over O,SFE: Phase 2 - Core Implementation
par Core Tasks (Parallel)
O->>FE: Implement theme context
FE->>FE: Working on persistence...
FE->>O: β οΈ Struggling with edge cases
O->>SFE: Complete theme context (escalated)
SFE->>O: β Context complete with persistence
and
O->>FE: Create toggle component
FE->>O: β Toggle complete
end
Note over O,SFE: Phase 3 - Apply
O->>SFE: Apply theme to all components
SFE->>O: β Theme applied
O->>R: Review implementation
R->>O: β Passed - no issues
O->>User: Dark mode implemented with toggle
sequenceDiagram
actor User
participant C as π Clarifier<br/>Sonnet 4.5
participant O as π― Orchestrator<br/>Sonnet 4.5
participant P as π Planner<br/>GPT-5.2
participant SBE as π Senior Backend<br/>Opus 4.6
participant Des as π¨ Designer<br/>Gemini Pro
participant R as β
Reviewer<br/>Sonnet 4.5
User->>C: Make the dashboard better
C->>C: Analyzing request...<br/>Too vague!
C->>User: β οΈ Need clarification:<br/><br/>**Scope:**<br/>1. Which aspects? (UI, performance, data)<br/>2. Which dashboard? (admin vs user)<br/><br/>**Priority:**<br/>1. Specific pain points?
User->>C: The admin dashboard is slow.<br/>Load time is 8+ seconds.
C->>O: Clarified: Optimize admin dashboard<br/>performance (target <2s load)
O->>P: Create performance optimization plan
P->>O: Phase 1: Profile<br/>Phase 2: Optimize queries<br/>Phase 3: Add caching
O->>SBE: Profile admin dashboard performance
SBE->>O: β Found: N+1 queries, no caching
O->>SBE: Optimize database queries
SBE->>O: β Queries optimized
O->>SBE: Implement caching layer
SBE->>O: β Redis cache added
O->>R: Review optimizations
R->>R: Security check:<br/>Cache invalidation OK<br/>No data leaks
R->>O: β Passed
O->>User: Dashboard optimized:<br/>Load time now ~1.2s
sequenceDiagram
actor User
participant O as π― Orchestrator<br/>Sonnet 4.5
participant JD as β‘ Junior Dev<br/>Gemini Flash
participant FS as π Fullstack Dev<br/>Gemini Pro
participant SFS as π Senior Fullstack<br/>Codex
participant SBE as π Senior Backend<br/>Opus 4.6
User->>O: Add user authentication
Note over O,JD: Start with Junior Dev
O->>JD: Create login form
JD->>JD: Building form...
JD->>O: β οΈ Need validation logic,<br/>session management
Note over O,FS: Escalate to Fullstack Dev
O->>FS: Complete login with validation
FS->>FS: Adding validation...
FS->>O: β οΈ Security concerns:<br/>token storage, XSS protection
Note over O,SFS: Escalate to Senior Fullstack
O->>SFS: Implement secure authentication
SFS->>SFS: Working on JWT...
SFS->>O: β οΈ Need architecture decision:<br/>Refresh tokens, session store
Note over O,SBE: Escalate to Senior Backend
O->>SBE: Design secure auth architecture
SBE->>SBE: Designing system with:<br/>- JWT access tokens (15min)<br/>- Refresh tokens (7 days)<br/>- Redis session store<br/>- CSRF protection
SBE->>O: β Auth system complete
O->>User: Secure authentication implemented
- Start with lightest agent (cost-effective)
- Escalate when complexity exceeds capacity
- Monitor context usage and progress
- File-based conflict detection
- Independent tasks run simultaneously
- Sequential execution only when needed
- Clarifier agent intercepts ambiguous requests
- Targeted questions with context
- Reasonable defaults when appropriate
- Reviewer agent checks all work
- Security, bugs, performance validation
- No code reaches user without review
- Gemini Flash for simple tasks (fastest, cheapest)
- Gemini Pro for standard work (balanced)
- GPT-5.2-Codex for speed-critical features
- Claude Opus only for critical/complex work
Clear separation of responsibilities to prevent overlap:
Data Engineer (Data-Centric Work)
- β Analytical SQL queries (aggregations, window functions, complex JOINs)
- β Data warehousing & ETL pipelines (Databricks, Spark, Airflow)
- β Batch data processing & transformations
- β Data quality validation & cleansing
- β Working with data files (CSV, JSON, Parquet)
- β Analytics, reporting queries, data modeling
- β CRUD APIs or real-time request handling
- β Application business logic
- β User authentication/authorization
Backend Developer (Application Logic)
- β REST/GraphQL API development
- β Business rules & workflows
- β CRUD operations for applications
- β Authentication, authorization, sessions
- β Real-time request/response handling
- β Microservices & application integration
- β Complex analytical queries or data warehousing
- β Large-scale ETL pipelines
- β Databricks/Spark jobs
Rule of Thumb: If it powers an API endpoint β Backend Developer. If it processes/analyzes bulk data β Data Engineer.
Designer (Visual Design & Planning)
- β Creating mockups, prototypes, wireframes
- β Defining color palettes, typography, spacing systems
- β Design tokens & style guides
- β User experience flows & interaction patterns
- β Brand guidelines & visual identity
- β Writing production code (React, Vue, etc.)
- β Implementing components with logic
- β API integration or state management
Frontend Developer (Implementation)
- β Implementing designs as functional components
- β Writing HTML/CSS/JavaScript/TypeScript
- β Component logic, state management, routing
- β API integration & data fetching
- β Form handling, validation, interactivity
- β Creating design systems from scratch
- β Making major design decisions (without Designer input)
- β Visual mockups or prototypes
Rule of Thumb: Designer creates the blueprint β Frontend Developer builds it. Designer hands off Figma/specs β Developer writes code.
| Task | Correct Agent | NOT This Agent |
|---|---|---|
| "Build a REST API for user management" | βοΈ Backend Developer | β Data Engineer |
| "Write SQL query to analyze last quarter's revenue" | π Data Engineer | β Backend Developer |
| "Create Databricks notebook for ETL pipeline" | π Data Engineer | β Backend Developer |
| "Design the color scheme and layout for dashboard" | π¨ Designer | β Frontend Developer |
| "Implement the login form with validation" | π¨ Frontend Developer | β Designer |
| "Build a React component from this Figma file" | π¨ Frontend Developer | β Designer |
| "Create mockup showing user flow for checkout" | π¨ Designer | β Frontend Developer |
| "Optimize this slow Spark job processing logs" | π Data Engineer | β Senior Backend Developer |
| "Create microservice architecture for payments" | π Senior Backend Developer | β Data Engineer |
| Task Complexity | Files | Lines | Start With |
|---|---|---|---|
| Typo fix, config change | 1-2 | <50 | β‘ Junior Developer |
| Standard feature | 3-5 | 50-300 | π¨ Frontend/Backend/Fullstack Developer |
| Multi-file feature, API integration | 5+ | 300-1000 | π Senior Frontend/Backend/Fullstack |
| Architecture, security, performance | Any | Any | π Senior Backend Developer |
| Sign | Action |
|---|---|
| Multiple clarification rounds | Escalate one level |
| Context usage >50% | Escalate one level |
| Security/performance concerns | Escalate to Senior Backend/Fullstack Developer |
| Agent indicates scope exceeds capability | Escalate one level |
- User makes request β Goes to Clarifier first
- Clarifier β Confirms clarity or asks questions
- Orchestrator β Calls Planner for strategy
- Planner β Returns phased implementation plan
- Orchestrator β Delegates to specialists, monitors progress
- Specialists β Execute tasks (with escalation as needed)
- Reviewer β Validates quality before user delivery
- Orchestrator β Reports results to user
β DO:
- Let Clarifier handle ambiguous requests
- Start with lightest appropriate agent
- Run independent tasks in parallel
- Review before finalizing
- Document assumptions when clarifying
β DON'T:
- Skip clarification for vague requests
- Over-assign (use Senior devs for simple tasks)
- Run file-overlapping tasks in parallel
- Skip review step
- Let specialists create their own documentation
| Model | Use Case | Strengths |
|---|---|---|
| Claude Sonnet 4.5 | Orchestration, Review, Clarification | Reasoning, coordination, analysis |
| Claude Opus 4.6 | Backend development, Data engineering | Deep technical expertise, careful design |
| GPT-5.2 | Planning | Strategic thinking, comprehensive plans |
| GPT-5.2-Codex | Senior Frontend/Fullstack, DevOps | Speed, code generation, tooling |
| Gemini 3 Pro | Frontend/Fullstack dev, Design, Prompt writing | Balanced performance, good at UI |
| Gemini 3 Flash | Junior developer tasks | Fastest execution, cost-effective |
orchestrator.agent.md- Main coordination logicclarifier.agent.md- Requirement clarificationplanner.agent.md- Strategy creationjunior-dev.agent.md- Quick fixes and simple tasksfrontend-dev.agent.md- UI and componentsbackend-dev.agent.md- APIs and databasesfullstack-dev.agent.md- End-to-end featuressr-frontend-dev.agent.md- Complex UI architecturesr-backend-dev.agent.md- Distributed systemssr-fullstack-dev.agent.md- Complex integrationsdata-engineer.agent.md- SQL, ETL, and analyticsdesigner.agent.md- UI/UX designprompt-writer.agent.md- Prompt engineeringdevops.agent.md- Operations and deploymentreviewer.agent.md- Quality assurance
System Rating: 10/10 ββββββββββ
A production-grade multi-agent development system with intelligent orchestration, adaptive resource allocation, comprehensive quality gates, and one-click installation.
Agents have access to specialized skills for domain-specific guidance:
- TypeScript Patterns - Advanced types, generics, type-safe APIs, React & Node.js patterns
- Code Quality & Clean Code - SOLID principles, design patterns, refactoring, code smells
- Data Transformation & ETL - CSV/JSON/XML parsing, validation, streaming/batch processing
- Frontend Architecture - Performance optimization, component design, state management
- API Design - RESTful patterns, versioning, error handling
- Database Optimization - Query optimization, indexing, performance tuning
- Testing & QA - Unit, integration, E2E testing strategies
- Security Best Practices - Authentication, encryption, vulnerability prevention
The adaptive escalation model optimizes costs by matching agent capability to task complexity:
- 70% of tasks β Junior Developer (Gemini Flash) - Quick fixes and simple implementations
- 20% of tasks β Frontend/Backend/Fullstack Developers - Standard features and APIs
- 10% of tasks β Senior Frontend/Backend/Fullstack Developers (Opus/Codex) - Complex architecture and critical systems
Key Benefits:
- Start with the most cost-effective agent appropriate for the task
- Escalate only when complexity demands it
- Parallel execution reduces overall time and token usage
- Mandatory clarification prevents costly rework
- Quality gates catch issues before production
This approach delivers enterprise-grade quality while keeping costs predictable and efficient. π