HAS_SECURITY_PIPELINE = FALSE
  Set TRUE if pipeline contains ANY of: security scan results, SAST output,
  DAST output, dependency audit results, CVE reports, container scan,
  secrets detection output, compliance check results, SBOM generation,
  penetration test results, security gate failures, auth-related changes,
  certificate changes, encryption changes, API key rotation

HAS_PERFORMANCE_PIPELINE = FALSE
  Set TRUE if pipeline contains ANY of: load test results, performance
  benchmark output, latency metrics, throughput data, stress test results,
  memory profiling output, CPU profiling data, response time baselines,
  scalability test results, database query performance, cache hit ratios,
  CDN performance data, API response times, SLA compliance metrics

HAS_INFRA_CHANGE = FALSE
  Set TRUE if changes include ANY of: Dockerfile, docker-compose,
  kubernetes manifests, terraform files, CloudFormation templates,
  CI/CD pipeline config (.github/workflows, .gitlab-ci, Jenkinsfile),
  infrastructure as code, helm charts, ansible playbooks,
  environment variables, nginx config, database migrations,
  service mesh config, load balancer config, DNS changes

HAS_MIDDLEWARE = FALSE
  Set TRUE if pipeline artifacts or changes reference ANY of:
  middleware, ESB, message broker, MQ, Kafka, RabbitMQ,
  integration bus, API gateway, message queue, pub/sub,
  event bus, service bus, ActiveMQ, NATS, Redis Streams

HAS_SAP_INTEGRATION = FALSE
  Set TRUE if pipeline artifacts or changes reference ANY of:
  SAP, RFC, BAPI, IDoc, OData, S/4HANA, EWM, ECC, ABAP,
  CDS view, Fiori, SAP Cloud Integration, SAP PI/PO,
  SAP Gateway, SOAP service, SAP connector

HAS_AUTHORIZATION = FALSE
  Set TRUE if pipeline artifacts or changes reference ANY of:
  SoD, segregation of duties, role conflict, authorization object,
  T-code, user role, access control matrix, GRC, RBAC policy,
  permission matrix, privilege escalation, role assignment

+-- I have read the pipeline artifacts and test results
+-- I have read the CI/CD configuration files
+-- I have reviewed the change diff against baseline
+-- I have evaluated ALL SIX flags
+-- I have recorded which flags are TRUE
+-- I understand which conditional agents will be needed

+-------------------------------------------------------------+
|                    FLAG DETECTION RESULTS                    |
+-------------------------------------------------------------+
|                                                             |
|  HAS_SECURITY_PIPELINE:    [TRUE/FALSE]                     |
|  Evidence:                 [what triggered it - specific]   |
|                                                             |
|  HAS_PERFORMANCE_PIPELINE: [TRUE/FALSE]                     |
|  Evidence:                 [what triggered it - specific]   |
|                                                             |
|  HAS_INFRA_CHANGE:         [TRUE/FALSE]                     |
|  Evidence:                 [what triggered it - specific]   |
|                                                             |
|  HAS_MIDDLEWARE:            [TRUE/FALSE]                     |
|  Evidence:                 [what triggered it - specific]   |
|                                                             |
|  HAS_SAP_INTEGRATION:      [TRUE/FALSE]                     |
|  Evidence:                 [what triggered it - specific]   |
|                                                             |
|  HAS_AUTHORIZATION:        [TRUE/FALSE]                     |
|  Evidence:                 [what triggered it - specific]   |
|                                                             |
|  EXPECTED AGENTS:                                           |
|  - Core: 3 (always)                                         |
|  - Conditional: [count based on TRUE flags]                 |
|  - Analysis: 1 (always)                                     |
|  - TOTAL: [3 + conditional count + 1]                       |
|                                                             |
+-------------------------------------------------------------+

+-------------------------------------------------------------+
|  YOU MUST INCLUDE ALL THREE TASK CALLS IN YOUR NEXT MESSAGE  |
|                                                              |
|  - Task 1: qe-quality-gate                                  |
|  - Task 2: qe-regression-analyzer                           |
|  - Task 3: qe-flaky-hunter                                  |
|                                                              |
|  If your message contains fewer than 3 Task calls, you have |
|  FAILED this phase. Start over.                              |
+-------------------------------------------------------------+

Task({
  description: "Quality gate threshold evaluation",
  prompt: `You are qe-quality-gate. Your output quality is being audited.

undefined

Task({
  description: "Regression risk analysis and test selection",
  prompt: `You are qe-regression-analyzer. Your output quality is being audited.

undefined

Task({
  description: "Flaky test detection and pipeline stability assessment",
  prompt: `You are qe-flaky-hunter. Your output quality is being audited.

undefined

I've launched 3 core agents in parallel:

  qe-quality-gate [Domain: quality-assessment]
   - Evaluating quality gate thresholds (8 dimensions)
   - Analyzing test results by category (unit, integration, e2e, contract)
   - Calculating coverage delta against baseline

  qe-regression-analyzer [Domain: test-execution]
   - Computing change impact blast radius
   - Scoring regression risk across 5 factors
   - Evaluating test selection effectiveness

  qe-flaky-hunter [Domain: test-execution]
   - Detecting flaky tests with root cause analysis
   - Assessing pipeline stability (5 metrics)
   - Calculating stability trends

  WAITING for all agents to complete before proceeding...

+-------------------------------------------------------------+
|  YOU MUST WAIT FOR ALL THREE BACKGROUND TASKS TO COMPLETE    |
|                                                              |
|  DO NOT summarize what agents "would" find                   |
|  DO NOT proceed to Phase 4 early                             |
|  DO NOT provide your own analysis as substitute              |
|                                                              |
|  WAIT for actual agent results                               |
|  ONLY proceed when all three have returned                   |
+-------------------------------------------------------------+

From qe-quality-gate:
[ ] qualityGateStatus = PASSED/FAILED (X/Y gates passed)
[ ] testPassRate = __% overall pass rate
[ ] coverageDelta = +/-__% coverage change
[ ] failedTests = __ count of failed tests
[ ] qualityGateScore = __/50

From qe-regression-analyzer:
[ ] regressionRisk = __/50 risk score
[ ] blastRadius = __ files in blast radius
[ ] changedFiles = __ files changed
[ ] missingCoverage = __ uncovered changes
[ ] regressionRiskLevel = High/Medium/Low

From qe-flaky-hunter:
[ ] flakyTests = __ total flaky tests detected
[ ] criticalFlaky = __ blocking releases
[ ] pipelineStability = __% pass rate
[ ] stabilityScore = __/100
[ ] flakyRate = __% flaky rate

+-------------------------------------------------------------+
|                    BATCH 1 RESULTS SUMMARY                   |
+-------------------------------------------------------------+
|                                                              |
|  Quality Gate:             PASSED/FAILED (X/Y gates)         |
|  Test Pass Rate:           __%                               |
|  Coverage Delta:           +/-__%                            |
|  Failed Tests:             __                                |
|  Quality Gate Score:       __/50                              |
|                                                              |
|  Regression Risk:          __/50 (High/Med/Low)              |
|  Blast Radius:             __ files                          |
|  Changed Files:            __                                |
|  Missing Coverage:         __ uncovered changes              |
|                                                              |
|  Flaky Tests:              __                                |
|  Critical Flaky:           __                                |
|  Pipeline Stability:       __%                               |
|  Stability Score:          __/100                            |
|  Flaky Rate:               __%                               |
|                                                              |
+-------------------------------------------------------------+

+-------------------------------------------------------------+
|  IF A FLAG IS TRUE, YOU MUST SPAWN THAT AGENT                |
|                                                              |
|  HAS_SECURITY_PIPELINE = TRUE    -> MUST spawn qe-security-scanner   |
|  HAS_PERFORMANCE_PIPELINE = TRUE -> MUST spawn qe-chaos-engineer     |
|  HAS_INFRA_CHANGE = TRUE         -> MUST spawn qe-coverage-specialist|
|  HAS_MIDDLEWARE = TRUE            -> MUST spawn qe-middleware-validator|
|  HAS_SAP_INTEGRATION = TRUE      -> MUST spawn qe-soap-tester        |
|  HAS_AUTHORIZATION = TRUE        -> MUST spawn qe-sod-analyzer       |
|                                                              |
|  Skipping a flagged agent is a FAILURE of this skill.        |
+-------------------------------------------------------------+

IF HAS_SECURITY_PIPELINE == FALSE AND HAS_PERFORMANCE_PIPELINE == FALSE AND HAS_INFRA_CHANGE == FALSE AND HAS_MIDDLEWARE == FALSE AND HAS_SAP_INTEGRATION == FALSE AND HAS_AUTHORIZATION == FALSE:
    -> Skip to Phase 5 (no conditional agents needed)
    -> State: "No conditional agents needed based on pipeline analysis"

ELSE:
    -> Spawn ALL applicable agents in ONE message
    -> Count how many you're spawning: __

Task({
  description: "CI/CD security pipeline validation",
  prompt: `You are qe-security-scanner. Your output quality is being audited.

undefined

Task({
  description: "Performance pipeline validation and resilience assessment",
  prompt: `You are qe-chaos-engineer. Your output quality is being audited.

undefined

Task({
  description: "Infrastructure change coverage and impact analysis",
  prompt: `You are qe-coverage-specialist. Your output quality is being audited.

undefined

Task({
  description: "Middleware and message broker pipeline verification",
  prompt: `You are qe-middleware-validator. Your output quality is being audited.

undefined

Task({
  description: "SAP SOAP service and integration pipeline verification",
  prompt: `You are qe-soap-tester. Your output quality is being audited.

undefined

Task({
  description: "Segregation of duties and authorization verification in pipeline",
  prompt: `You are qe-sod-analyzer. Your output quality is being audited.

undefined

+-------------------------------------------------------------+
|                   AGENT COUNT VALIDATION                     |
+-------------------------------------------------------------+
|                                                              |
|  CORE AGENTS (ALWAYS 3):                                     |
|    [ ] qe-quality-gate - SPAWNED? [Y/N]                     |
|    [ ] qe-regression-analyzer - SPAWNED? [Y/N]              |
|    [ ] qe-flaky-hunter - SPAWNED? [Y/N]                     |
|                                                              |
|  CONDITIONAL AGENTS (based on flags):                        |
|    [ ] qe-security-scanner - SPAWNED? [Y/N] (HAS_SEC_PIPE)  |
|    [ ] qe-chaos-engineer - SPAWNED? [Y/N] (HAS_PERF_PIPE)   |
|    [ ] qe-coverage-specialist - SPAWNED? [Y/N] (HAS_INFRA)  |
|    [ ] qe-middleware-validator - SPAWNED? [Y/N] (HAS_MIDDLEWARE)  |
|    [ ] qe-soap-tester - SPAWNED? [Y/N] (HAS_SAP_INTEG)          |
|    [ ] qe-sod-analyzer - SPAWNED? [Y/N] (HAS_AUTHORIZATION)     |
|                                                              |
|  VALIDATION:                                                 |
|    Expected agents: [3 + count of TRUE flags]                |
|    Actual spawned:  [count]                                  |
|    Status:          [PASS/FAIL]                              |
|                                                              |
|  If ACTUAL < EXPECTED, you have FAILED. Spawn missing        |
|  agents before proceeding.                                   |
|                                                              |
+-------------------------------------------------------------+

I've launched [N] conditional agent(s) in parallel:

[IF HAS_SECURITY_PIPELINE]    qe-security-scanner [Domain: security-compliance]
                              - SAST/DAST validation, dependency audit, container scan
[IF HAS_PERFORMANCE_PIPELINE] qe-chaos-engineer [Domain: chaos-resilience]
                              - Performance regression detection, resource analysis, resilience
[IF HAS_INFRA_CHANGE]         qe-coverage-specialist [Domain: coverage-analysis]
                              - Infrastructure change coverage, config drift, artifact verification
[IF HAS_MIDDLEWARE]           qe-middleware-validator [Domain: enterprise-integration]
                              - Middleware pipeline verification, broker health, message flow testing
[IF HAS_SAP_INTEGRATION]     qe-soap-tester [Domain: enterprise-integration]
                              - SAP SOAP service validation, WSDL contracts, integration gateway health
[IF HAS_AUTHORIZATION]        qe-sod-analyzer [Domain: enterprise-integration]
                              - SoD compliance verification, role change impact, access control testing

  WAITING for conditional agents to complete...

STEP 1: Derive composite metrics
-----------------------------------------------------------
qualityGatesPassed = (qualityGateStatus == "PASSED")
testPassRate = testPassRate from qe-quality-gate
regressionRisk = regressionRisk from qe-regression-analyzer (0-50 scale)
flakyRate = flakyRate from qe-flaky-hunter
criticalFlaky = criticalFlaky from qe-flaky-hunter
failedTests = failedTests from qe-quality-gate
securityFindings = (critical + high severity findings from security, if ran)
performanceRegressions = (count of regressions from chaos engineer, if ran)

STEP 2: Check BLOCK conditions (ANY triggers BLOCK)
-----------------------------------------------------------
IF qualityGatesPassed == FALSE        -> BLOCK ("Quality gates failed")
IF testPassRate < 95                  -> BLOCK ("Test pass rate critically low")
IF failedTests > 0 AND critical       -> BLOCK ("Critical test failures")
IF regressionRisk > 40               -> BLOCK ("Regression risk too high")
IF securityFindings > 0 (critical)    -> BLOCK ("Critical security vulnerabilities")

STEP 3: Check RELEASE conditions (ALL required for RELEASE)
-----------------------------------------------------------
IF qualityGatesPassed == TRUE
   AND testPassRate >= 99
   AND regressionRisk <= 15
   AND flakyRate <= 2
   AND criticalFlaky == 0
   AND failedTests == 0
   AND securityFindings == 0          -> RELEASE

STEP 4: Default
-----------------------------------------------------------
ELSE                                  -> REMEDIATE

METRICS:
- qualityGatesPassed = TRUE/FALSE
- testPassRate = __%
- regressionRisk = __/50
- flakyRate = __%
- criticalFlaky = __
- failedTests = __
- securityFindings = __ (if applicable)
- performanceRegressions = __ (if applicable)

BLOCK CHECK:
- qualityGatesPassed == FALSE? __ (YES/NO)
- testPassRate < 95? __ (YES/NO)
- critical test failures? __ (YES/NO)
- regressionRisk > 40? __ (YES/NO)
- critical security findings? __ (YES/NO)

RELEASE CHECK (only if no BLOCK triggered):
- qualityGatesPassed == TRUE? __ (YES/NO)
- testPassRate >= 99? __ (YES/NO)
- regressionRisk <= 15? __ (YES/NO)
- flakyRate <= 2? __ (YES/NO)
- criticalFlaky == 0? __ (YES/NO)
- failedTests == 0? __ (YES/NO)
- securityFindings == 0? __ (YES/NO)

FINAL RECOMMENDATION: [RELEASE / REMEDIATE / BLOCK]
REASON: ___

undefined

Write the executive summary report to:
`${OUTPUT_FOLDER}/01-executive-summary.md`

+-- Executive Summary table is complete with all 5 metrics
+-- Recommendation matches decision logic output
+-- Quality Gate section includes all 8 gate statuses
+-- Regression section includes blast radius and risk score
+-- Flaky Test section includes stability score
+-- Conditional sections included for all spawned agents
+-- Recommended actions are specific (not generic)
+-- Report saved to output folder

+-------------------------------------------------------------+
|  LEARNING PERSISTENCE MUST ALWAYS EXECUTE                    |
|                                                              |
|  This is NOT optional. It runs on EVERY verification scan.   |
|  It stores findings for cross-phase feedback loops,          |
|  historical pipeline quality tracking, and pattern learning. |
|                                                              |
|  DO NOT skip this phase for any reason.                      |
|  DO NOT treat this as "nice to have".                        |
|  Enforcement Rule E9 applies.                                |
+-------------------------------------------------------------+

mcp__agentic-qe__memory_store({
  key: `qcsd-cicd-${releaseId}-${Date.now()}`,
  namespace: "qcsd-cicd",
  value: {
    releaseId: releaseId,
    releaseName: releaseName,
    recommendation: recommendation,  // RELEASE, REMEDIATE, BLOCK
    metrics: {
      qualityGatesPassed: qualityGatesPassed,
      testPassRate: testPassRate,
      regressionRisk: regressionRisk,
      flakyRate: flakyRate,
      criticalFlaky: criticalFlaky,
      failedTests: failedTests,
      pipelineStability: stabilityScore,
      securityFindings: securityFindings,  // if applicable
      performanceRegressions: performanceRegressions  // if applicable
    },
    flags: {
      HAS_SECURITY_PIPELINE: HAS_SECURITY_PIPELINE,
      HAS_PERFORMANCE_PIPELINE: HAS_PERFORMANCE_PIPELINE,
      HAS_INFRA_CHANGE: HAS_INFRA_CHANGE,
      HAS_MIDDLEWARE: HAS_MIDDLEWARE,
      HAS_SAP_INTEGRATION: HAS_SAP_INTEGRATION,
      HAS_AUTHORIZATION: HAS_AUTHORIZATION
    },
    agentsInvoked: agentList,
    timestamp: new Date().toISOString()
  }
})

mcp__agentic-qe__memory_share({
  sourceAgentId: "qcsd-cicd-swarm",
  targetAgentIds: ["qe-learning-coordinator", "qe-pattern-learner"],
  knowledgeDomain: "cicd-verification-patterns"
})

Save to: ${OUTPUT_FOLDER}/09-learning-persistence.json

Contents:
{
  "phase": "QCSD-Verification",
  "releaseId": "[release ID]",
  "releaseName": "[release name]",
  "recommendation": "[RELEASE/REMEDIATE/BLOCK]",
  "memoryKey": "qcsd-cicd-[releaseId]-[timestamp]",
  "namespace": "qcsd-cicd",
  "metrics": {
    "qualityGatesPassed": true/false,
    "testPassRate": [0-100],
    "regressionRisk": [0-50],
    "flakyRate": [0-100],
    "criticalFlaky": [N],
    "failedTests": [N],
    "pipelineStability": [0-100],
    "securityFindings": [N or null],
    "performanceRegressions": [N or null]
  },
  "flags": {
    "HAS_SECURITY_PIPELINE": true/false,
    "HAS_PERFORMANCE_PIPELINE": true/false,
    "HAS_INFRA_CHANGE": true/false,
    "HAS_MIDDLEWARE": true/false,
    "HAS_SAP_INTEGRATION": true/false,
    "HAS_AUTHORIZATION": true/false
  },
  "agentsInvoked": ["list", "of", "agents"],
  "crossPhaseSignals": {
    "toProduction": "Release readiness metrics as production monitoring baseline",
    "toIdeation": "Pipeline patterns for future risk assessment"
  },
  "persistedAt": "[ISO timestamp]"
}

npx @claude-flow/cli@latest memory store \
  --key "qcsd-cicd-${RELEASE_ID}-$(date +%s)" \
  --value '{"recommendation":"[VALUE]","testPassRate":[N],"regressionRisk":[N],"flakyRate":[N]}' \
  --namespace qcsd-cicd

npx @claude-flow/cli@latest hooks post-task \
  --task-id "qcsd-cicd-${RELEASE_ID}" \
  --success true

+-- Did I execute mcp__agentic-qe__memory_store with actual values? (not placeholders)
+-- Did I execute mcp__agentic-qe__memory_share to propagate learnings?
+-- Did I save 09-learning-persistence.json to the output folder?
+-- Does the JSON contain the correct recommendation from Phase 5?
+-- Does the JSON contain actual metrics from Phases 2-4?
+-- Does the JSON contain actual flag values from Phase 1?

CONSUMES (from other phases):
+-- Loop 3 (Development): SHIP/CONDITIONAL/HOLD decisions
|   - Code quality metrics guide verification depth
|   - HOLD decisions trigger enhanced scrutiny
|   - Coverage data informs regression risk assessment
|
+-- Loop 5 (Pipeline History): Previous verification results
    - Historical flaky test patterns
    - Regression risk baselines
    - Performance benchmarks

PRODUCES (for other phases):
+-- To Production Phase: Release readiness metrics
|   - Deployment risk score
|   - Known issues and accepted risks
|   - Monitoring recommendations
|
+-- To next Ideation Cycle: Pipeline patterns
    - Which areas consistently block releases
    - Flaky test patterns for future risk assessment
    - Infrastructure change risk patterns

+-------------------------------------------------------------+
|  THE DEPLOYMENT ADVISOR MUST ALWAYS RUN                       |
|                                                              |
|  This is NOT conditional. It runs on EVERY verification scan.|
|  It synthesizes all pipeline data into a release readiness   |
|  assessment with specific deployment recommendations.        |
|                                                              |
|  DO NOT skip this phase for any reason.                      |
+-------------------------------------------------------------+

Task({
  description: "Deployment readiness advisory and release synthesis",
  prompt: `You are qe-deployment-advisor. Your output quality is being audited.

undefined

+-------------------------------------------------------------+
|  WAIT for qe-deployment-advisor to complete before            |
|  proceeding to Phase 9.                                      |
|                                                              |
|  The deployment advisory is the FINAL quality signal of      |
|  the CI/CD Swarm - it synthesizes all metrics into           |
|  actionable deployment recommendations.                      |
+-------------------------------------------------------------+

+---------------------------------------------------------------------+
|                  QCSD CI/CD SWARM COMPLETE                            |
+---------------------------------------------------------------------+
|                                                                      |
|  Pipeline Verified: [Feature/Release Name]                            |
|  Reports Generated: [count]                                           |
|  Output Folder: ${OUTPUT_FOLDER}                                     |
|                                                                      |
|  VERIFICATION SCORES:                                                 |
|  +-- Quality Gate:            PASSED/FAILED (X/Y gates)              |
|  +-- Test Pass Rate:          __%                                     |
|  +-- Regression Risk:         __/50                                   |
|  +-- Flaky Rate:              __%                                     |
|  +-- Pipeline Stability:      __/100                                  |
|  +-- Deployment Readiness:    __/60                                   |
|  [IF HAS_SECURITY_PIPELINE]                                           |
|  +-- Security Score:          __/50                                   |
|  [IF HAS_PERFORMANCE_PIPELINE]                                        |
|  +-- Performance Score:       __/40                                   |
|  [IF HAS_INFRA_CHANGE]                                                |
|  +-- Infrastructure Score:    __/40                                   |
|  [IF HAS_MIDDLEWARE]                                                  |
|  +-- Middleware Pipeline:     __/50                                   |
|  [IF HAS_SAP_INTEGRATION]                                            |
|  +-- SAP Pipeline:            __/50                                   |
|  [IF HAS_AUTHORIZATION]                                              |
|  +-- Authorization Pipeline:  __/50                                   |
|                                                                      |
|  RECOMMENDATION: [RELEASE / REMEDIATE / BLOCK]                        |
|  REASON: [1-2 sentence rationale]                                     |
|                                                                      |
|  DELIVERABLES:                                                        |
|  +-- 01-executive-summary.md                                          |
|  +-- 02-quality-gate.md                                               |
|  +-- 03-regression-analysis.md                                        |
|  +-- 04-flaky-test-analysis.md                                        |
|  [IF HAS_SECURITY_PIPELINE]                                           |
|  +-- 05-security-pipeline.md                                          |
|  [IF HAS_PERFORMANCE_PIPELINE]                                        |
|  +-- 06-performance-pipeline.md                                       |
|  [IF HAS_INFRA_CHANGE]                                                |
|  +-- 07-infrastructure-coverage.md                                    |
|  [IF HAS_MIDDLEWARE]                                                  |
|  +-- 10-middleware-pipeline.md                                        |
|  [IF HAS_SAP_INTEGRATION]                                            |
|  +-- 11-sap-pipeline.md                                              |
|  [IF HAS_AUTHORIZATION]                                              |
|  +-- 12-sod-pipeline.md                                              |
|  +-- 08-deployment-advisory.md                                        |
|  +-- 09-learning-persistence.json                                     |
|                                                                      |
+---------------------------------------------------------------------+

+---------------------------------------------------------------------+
|  ACTION REQUIRED: PIPELINE BLOCKED - DO NOT RELEASE                   |
+---------------------------------------------------------------------+
|                                                                      |
|  The following blockers MUST be resolved before release:              |
|                                                                      |
|  1. [Blocker 1 with specific remediation]                             |
|  2. [Blocker 2 with specific remediation]                             |
|  3. [Blocker 3 with specific remediation]                             |
|                                                                      |
|  NEXT STEPS:                                                          |
|  - Address all P0 blockers listed above                               |
|  - Re-run CI/CD pipeline after fixes                                  |
|  - Re-run /qcsd-cicd-swarm after pipeline passes                     |
|  - Target: 100% test pass, risk <= 15, 0 critical findings           |
|                                                                      |
+---------------------------------------------------------------------+

+---------------------------------------------------------------------+
|  REMEDIATE: PIPELINE NEEDS ATTENTION BEFORE RELEASE                   |
+---------------------------------------------------------------------+
|                                                                      |
|  The pipeline can proceed WITH these remediations:                    |
|                                                                      |
|  1. [Remediation 1 - must be addressed before release]                |
|  2. [Remediation 2 - must be addressed in follow-up]                  |
|                                                                      |
|  DEPLOYMENT STRATEGY:                                                 |
|  - Use canary/blue-green deployment for risk mitigation               |
|  - Monitor [specific metrics] post-deployment                        |
|  - Automated rollback if [conditions]                                 |
|                                                                      |
|  RISK ACCEPTANCE:                                                     |
|  - Release owner acknowledges remaining risks                        |
|  - Follow-up issues created for deferred remediations                 |
|                                                                      |
+---------------------------------------------------------------------+

+-----------------------------------------------------------------------------+
|                   QCSD CI/CD VERIFICATION - DOMAIN MAP                       |
+-----------------------------------------------------------------------------+
|                                                                              |
|  PRIMARY DOMAINS (Always Active)                                             |
|  +-------------------------------+  +-------------------------------+       |
|  |     quality-assessment        |  |       test-execution          |       |
|  |  ---------------------------  |  |  ---------------------------  |       |
|  |  - qe-quality-gate            |  |  - qe-regression-analyzer    |       |
|  |    (threshold enforcement,    |  |    (change impact, blast      |       |
|  |     pass/fail evaluation)     |  |     radius, regression risk)  |       |
|  +-------------------------------+  |                               |       |
|                                     |  - qe-flaky-hunter            |       |
|                                     |    (flaky detection, pipeline  |       |
|                                     |     stability assessment)      |       |
|                                     +-------------------------------+       |
|                                                                              |
|  CONDITIONAL DOMAINS (Based on Pipeline Content)                             |
|  +-----------------------+  +-----------------------+  +------------------+ |
|  | security-compliance   |  |  chaos-resilience     |  | coverage-analysis| |
|  | ───────────────────── |  |  ──────────────────── |  | ──────────────── | |
|  | qe-security-scanner   |  |  qe-chaos-engineer    |  | qe-coverage-     | |
|  | [IF HAS_SEC_PIPELINE] |  |  [IF HAS_PERF_PIPE]   |  | specialist       | |
|  |                       |  |                       |  | [IF HAS_INFRA]   | |
|  +-----------------------+  +-----------------------+  +------------------+ |
|                                                                              |
|  +-----------------------------------------------------------------------+  |
|  |                  enterprise-integration                                |  |
|  |  -----------------------------------------------------------------   |  |
|  |  - qe-middleware-validator [IF HAS_MIDDLEWARE]                        |  |
|  |  - qe-soap-tester [IF HAS_SAP_INTEGRATION]                          |  |
|  |  - qe-sod-analyzer [IF HAS_AUTHORIZATION]                           |  |
|  +-----------------------------------------------------------------------+  |
|                                                                              |
|  ANALYSIS DOMAIN (Always Active)                                             |
|  +-----------------------------------------------------------------------+  |
|  |                    quality-assessment                                   |  |
|  |  -----------------------------------------------------------------   |  |
|  |  - qe-deployment-advisor (readiness matrix, risk register, go/no-go) |  |
|  +-----------------------------------------------------------------------+  |
|                                                                              |
+-----------------------------------------------------------------------------+

Just follow the skill phases above - uses Task() calls with run_in_background: true

// Initialize fleet for Verification domains
mcp__agentic-qe__fleet_init({
  topology: "hierarchical",
  enabledDomains: ["quality-assessment", "test-execution", "security-compliance", "chaos-resilience", "coverage-analysis"],
  maxAgents: 7
})

// Orchestrate verification task
mcp__agentic-qe__task_orchestrate({
  task: "qcsd-cicd-verification",
  strategy: "parallel"
})

undefined

---