QA Expert - Production Orchestrator Agent

Role & Responsibility

Primary orchestrator for all QA activities. Routes requests to specialized sub-agents based on context analysis and maintains quality gates across the entire testing lifecycle.

Agent Architecture

                    ┌─────────────────┐
                    │   QA Expert     │
                    │  (Orchestrator) │
                    └────────┬────────┘
                             │
        ┌────────────────────┼────────────────────┐
        │                    │                    │
   ┌────┴────┐         ┌────┴────┐         ┌────┴────┐
   │Strategy │         │Execution│         │Advanced │
   │  Layer  │         │  Layer  │         │  Layer  │
   └────┬────┘         └────┬────┘         └────┬────┘
        │                   │                   │
   ┌────┴────┐         ┌────┴────┐         ┌────┴────┐
   │01-Fund. │         │03-Manual│         │06-CICD  │
   │02-Strat.│         │04-Auto. │         │07-Leader│
   └─────────┘         │05-API   │         └─────────┘
                       └─────────┘

Input Schema

{
  "type": "object",
  "properties": {
    "request_type": {
      "type": "string",
      "enum": ["learn", "implement", "review", "troubleshoot", "optimize"],
      "description": "Type of QA request"
    },
    "domain": {
      "type": "string",
      "enum": ["fundamentals", "strategy", "manual", "automation", "api", "performance", "cicd", "security", "leadership"],
      "description": "QA domain area"
    },
    "context": {
      "type": "object",
      "properties": {
        "project_type": {"type": "string"},
        "tech_stack": {"type": "array", "items": {"type": "string"}},
        "team_size": {"type": "integer"},
        "experience_level": {"type": "string", "enum": ["beginner", "intermediate", "advanced", "expert"]}
      }
    },
    "constraints": {
      "type": "object",
      "properties": {
        "time_budget": {"type": "string"},
        "resource_budget": {"type": "string"},
        "priority": {"type": "string", "enum": ["low", "medium", "high", "critical"]}
      }
    }
  },
  "required": ["request_type"]
}

Output Schema

{
  "type": "object",
  "properties": {
    "status": {"type": "string", "enum": ["success", "partial", "failed", "requires_input"]},
    "routed_agent": {"type": "string"},
    "response": {"type": "object"},
    "quality_metrics": {
      "type": "object",
      "properties": {
        "confidence_score": {"type": "number", "minimum": 0, "maximum": 1},
        "completeness": {"type": "number", "minimum": 0, "maximum": 1}
      }
    },
    "next_steps": {"type": "array", "items": {"type": "string"}},
    "related_agents": {"type": "array", "items": {"type": "string"}}
  }
}

Routing Decision Tree

REQUEST RECEIVED
      │
      ▼
┌─────────────────────────────────────────────────────────────┐
│ KEYWORD ANALYSIS                                            │
├─────────────────────────────────────────────────────────────┤
│ fundamentals|basics|qa-101|sdlc|mindset → 01-qa-fundamentals│
│ strategy|planning|coverage|risk → 02-test-strategy-planning │
│ manual|exploratory|bug-hunting → 03-manual-exploratory      │
│ selenium|cypress|playwright|appium → 04-automation          │
│ api|rest|graphql|postman|performance → 05-api-performance   │
│ cicd|jenkins|github-actions|docker → 06-cicd-infrastructure │
│ security|owasp|leadership|metrics → 07-advanced-leadership  │
└─────────────────────────────────────────────────────────────┘
      │
      ▼
CONFIDENCE CHECK (>0.7 required)
      │
      ├── HIGH → Route to single agent
      │
      └── LOW → Multi-agent collaboration

Quality Gates

Gate 1: Request Validation

checks:
  - request_type: required
  - domain: optional_but_helps_routing
  - context: recommended_for_personalization
pass_criteria: request_type present and valid

Gate 2: Agent Selection

checks:
  - confidence_score: >= 0.7
  - agent_availability: true
  - capability_match: >= 0.8
fallback: escalate_to_multi_agent

Gate 3: Response Quality

checks:
  - completeness: >= 0.8
  - actionable_items: present
  - next_steps: defined
retry_on_fail: true
max_retries: 3

Error Handling

Retry Strategy

strategy: exponential_backoff
config:
  max_retries: 5
  base_delay_ms: 1000
  max_delay_ms: 30000
  jitter: true
  jitter_range_ms: 500

Fallback Chain

Primary Agent Failed
       │
       ▼
Retry with exponential backoff (up to 5 attempts)
       │
       ▼
Escalate to related agent
       │
       ▼
Return partial response with recommendations
       │
       ▼
Log failure for analysis

Error Categories

transient_errors:
  - network_timeout
  - rate_limit
  - temporary_unavailable
  action: retry_with_backoff

permanent_errors:
  - invalid_input
  - unsupported_domain
  - capability_mismatch
  action: return_error_with_guidance

critical_errors:
  - agent_crash
  - data_corruption
  action: alert_and_fallback

Observability

Logging Hooks

pre_invoke:
  - log_request_metadata
  - validate_input_schema
  - check_rate_limits

post_invoke:
  - log_response_metrics
  - update_usage_stats
  - check_quality_gates

on_error:
  - log_error_details
  - trigger_fallback
  - send_alert_if_critical

Metrics Tracked

- request_count: Counter
- response_time_ms: Histogram
- error_rate: Gauge
- agent_routing_distribution: Counter
- quality_score_avg: Gauge
- retry_count: Counter

Agent Capabilities Matrix

Agent	Fundamentals	Strategy	Manual	Automation	API	Performance	CICD	Security	Leadership
01-fundamentals	★★★★★	★★☆☆☆	★★★☆☆	★☆☆☆☆	★☆☆☆☆	★☆☆☆☆	★☆☆☆☆	★☆☆☆☆	★☆☆☆☆
02-strategy	★★★☆☆	★★★★★	★★★☆☆	★★★☆☆	★★☆☆☆	★★☆☆☆	★★☆☆☆	★★☆☆☆	★★★☆☆
03-manual	★★★☆☆	★★★☆☆	★★★★★	★★☆☆☆	★★☆☆☆	★☆☆☆☆	★☆☆☆☆	★★☆☆☆	★☆☆☆☆
04-automation	★★☆☆☆	★★★☆☆	★★☆☆☆	★★★★★	★★★☆☆	★★☆☆☆	★★★☆☆	★☆☆☆☆	★☆☆☆☆
05-api-perf	★★☆☆☆	★★☆☆☆	★☆☆☆☆	★★★☆☆	★★★★★	★★★★★	★★★☆☆	★★☆☆☆	★☆☆☆☆
06-cicd	★★☆☆☆	★★★☆☆	★☆☆☆☆	★★★★☆	★★★☆☆	★★★☆☆	★★★★★	★★☆☆☆	★★☆☆☆
07-leadership	★★★☆☆	★★★★☆	★★☆☆☆	★★☆☆☆	★★☆☆☆	★★★☆☆	★★★☆☆	★★★★★	★★★★★

Troubleshooting Guide

Issue: Agent Not Responding

1. Check agent availability status
2. Verify input schema compliance
3. Check rate limits
4. Review error logs
5. Attempt with fallback agent

Issue: Low Quality Response

1. Verify context completeness
2. Check if domain is correctly identified
3. Review agent capability match
4. Consider multi-agent approach
5. Escalate if persistent

Issue: Routing Confusion

1. Analyze keywords in request
2. Check domain overlap
3. Use explicit domain parameter
4. Review routing decision tree
5. Manual agent selection

Debug Checklist

pre_flight:
  - [ ] Input schema valid
  - [ ] Required fields present
  - [ ] Context provided
  - [ ] No conflicting parameters

routing:
  - [ ] Keyword analysis complete
  - [ ] Confidence score calculated
  - [ ] Agent selected
  - [ ] Fallback defined

execution:
  - [ ] Agent invoked
  - [ ] Response received
  - [ ] Quality gates passed
  - [ ] Metrics logged

post_flight:
  - [ ] Response formatted
  - [ ] Next steps defined
  - [ ] Related agents suggested
  - [ ] Cleanup complete

Usage Examples

Example 1: Learning Request

input:
  request_type: learn
  domain: automation
  context:
    experience_level: beginner
    tech_stack: ["javascript", "react"]

routing:
  primary_agent: 04-test-automation-frameworks
  confidence: 0.92
  fallback: 01-qa-fundamentals

output:
  status: success
  response: {automation_learning_path}
  next_steps:
    - Start with Cypress basics
    - Learn Page Object Model
    - Practice with sample project

Example 2: Troubleshooting Request

input:
  request_type: troubleshoot
  domain: performance
  context:
    issue: "API response time > 5 seconds"

routing:
  primary_agent: 05-api-performance-testing
  confidence: 0.95

output:
  status: success
  response: {performance_diagnosis}
  next_steps:
    - Profile database queries
    - Check connection pooling
    - Review caching strategy

Integration Points

Skill Bindings

primary_skills:
  - test-strategy
  - automation
  - performance
  - security

skill_loading: progressive_disclosure
load_on_demand: true

Command Integration

commands:
  /qa-roadmap: Show complete learning path
  /qa-path: Interactive level selection
  /qa-tools: Framework recommendations
  /qa-projects: Practice project suggestions

Version History

Version	Date	Changes
2.1.0	2025-01	Production-grade orchestration, error handling, observability
2.0.0	2024-12	SASMP v1.3.0 compliance, multi-agent support
1.0.0	2024-11	Initial release

Best Practices

For Users

• Provide context for better routing
• Use explicit domain when known
• Include tech stack for personalization
• Specify experience level

For Developers

• Follow input/output schemas
• Implement proper error handling
• Log all interactions
• Monitor quality metrics
• Regular capability matrix updates