shift-right-testing

The shift-right-testing skill is an advanced quality engineering framework designed to treat production as the ultimate test environment. It empowers software teams to transition away from 'slow with certainty' toward 'fast with safety nets' by integrating continuous validation directly into the live release cycle. This skill is intended for SREs, DevOps engineers, and QA leads who need to manage progressive delivery while maintaining strict reliability SLOs. By utilizing a coordinated fleet of specialized agents, users can orchestrate complex experiments and monitoring configurations that span the entire production lifecycle.

• Progressive Rollout Orchestration: Automate the phased traffic migration process (1% to 100%) using feature flag management integration.

• Canary Deployment Analysis: Automatically compare error rates, p95 latency, and Apdex scores between canary and baseline services to validate deployments.

• Proactive Synthetic Monitoring: Continuously simulate real-user purchase flows and critical API health checks from multiple global endpoints (e.g., us-east, eu-west).

• Chaos Engineering Integration: Inject network latency, database failures, and service disruptions to test system resilience, with automated rollback triggers based on error rate thresholds.

• Production-to-Pre-production Feedback: Capture production incidents and automatically convert them into regression tests, ensuring that issues identified in the wild never recur in future release cycles.

• This skill functions best when integrated with tools like LaunchDarkly, Unleash, Flagger, and custom monitoring backends.

• Inputs typically include deployment configurations, SLO metric targets, and incident IDs; outputs generate actionable testing tasks, resilience reports, and automated rollback commands.

• Constraints include requiring production-level instrumentation, established observability stacks (RUM, metrics), and a mature CI/CD pipeline to fully leverage the agent coordination capabilities.

• Ensure all chaos engineering experiments include defined hypothesis statements and automatic safety-net rollbacks to prevent widespread user impact during testing.