qcsd-cicd-swarm

name	qcsd-cicd-swarm
description	Use when enforcing CI/CD quality gates before release, running regression analysis, detecting flaky tests, or assessing deployment readiness in the QCSD Verification phase.
category	qcsd-phases
priority	critical
version	1.0.0
tokenEstimate	3500
domains	{"primary":[{"domain":"quality-assessment","agents":["qe-quality-gate"]},{"domain":"test-execution","agents":["qe-regression-analyzer"]},{"domain":"test-execution","agents":["qe-flaky-hunter"]}],"conditional":[{"domain":"security-compliance","agents":["qe-security-scanner"]},{"domain":"chaos-resilience","agents":["qe-chaos-engineer"]},{"domain":"coverage-analysis","agents":["qe-coverage-specialist"]},{"domain":"enterprise-integration","agents":["qe-middleware-validator","qe-soap-tester","qe-sod-analyzer"]}],"analysis":[{"domain":"quality-assessment","agents":["qe-deployment-advisor"]}]}
agents	{"core":["qe-quality-gate","qe-regression-analyzer","qe-flaky-hunter"],"conditional":["qe-security-scanner","qe-chaos-engineer","qe-coverage-specialist","qe-middleware-validator","qe-soap-tester","qe-sod-analyzer"],"analysis":["qe-deployment-advisor"],"total":10,"sub_agents":0}
skills	["shift-left-testing","shift-right-testing","regression-testing","security-testing"]
execution	{"primary":"task-tool","alternatives":["mcp-tools","cli"]}
swarm_pattern	true
parallel_batches	3
last_updated	"2026-02-03T00:00:00.000Z"
enforcement_level	strict
tags	["qcsd","verification","cicd","pipeline","quality-gate","regression","flaky","security","chaos","coverage","deployment","swarm","parallel","ddd"]
trust_tier	3
validation	{"schema_path":"schemas/output.json","validator_path":"scripts/validate-config.json","eval_path":"evals/qcsd-cicd-swarm.yaml"}

QCSD CI/CD Swarm v1.0

Shift-left quality engineering swarm for CI/CD pipeline verification and release readiness.

---

Overview

The CI/CD Swarm takes code that passed Development quality checks and validates it is safe to release through the CI/CD pipeline. Where the Development Swarm asks "Is the code quality sufficient to ship?", the CI/CD Swarm asks "Is this change safe to release?"

This swarm operates at the pipeline level, analyzing test results, regression risk, flaky test impact, security pipeline status, and infrastructure changes to render a RELEASE / REMEDIATE / BLOCK decision.

QCSD Phase Positioning

Phase	Swarm	Decision	When
Ideation	qcsd-ideation-swarm	GO / CONDITIONAL / NO-GO	PI/Sprint Planning
Refinement	qcsd-refinement-swarm	READY / CONDITIONAL / NOT-READY	Sprint Refinement
Development	qcsd-development-swarm	SHIP / CONDITIONAL / HOLD	During Sprint
Verification	qcsd-cicd-swarm	RELEASE / REMEDIATE / BLOCK	Pre-Release / CI-CD
Production	qcsd-production-swarm	HEALTHY / DEGRADED / CRITICAL	Post-Release

Parameters

• PIPELINE_ARTIFACTS: Path to CI/CD artifacts, test results, and build output (required, e.g., ci/artifacts/)
• BASELINE_REF: Git ref for baseline comparison (optional, default: main)
• OUTPUT_FOLDER: Where to save reports (default: ${PROJECT_ROOT}/Agentic QCSD/cicd/)
• DEPLOY_TARGET: Target deployment environment (optional, e.g., staging, production)

---

ENFORCEMENT RULES - READ FIRST

Rule	Enforcement
E1	You MUST spawn ALL THREE core agents (qe-quality-gate, qe-regression-analyzer, qe-flaky-hunter) in Step 2. No exceptions.