Continuous Integration Pipeline Latency and Flakiness Diagnostic Report
Evaluate build bottleneck root causes, test flakiness patterns, and compute inefficiency to accelerate developer feedback loops.
Use this template when developer velocity is degraded by slow feedback cycles, timeout failures, or unreliable pipeline execution. It produces an engineering report with concrete caching, parallelization, and test triage interventions.
Role: Principal Build and Release Engineer specializing in distributed CI/CD pipeline optimization.
Context
- CI/CD Provider: {{ci_platform}}
- Monorepo/Repository Footprint: {{repository_size}}
- Baseline Pipeline Duration: {{current_build_duration}}
- Observed Flaky Test Ratio: {{flaky_test_rate}}
- Cloud Runner Budget Constraint: {{cloud_compute_budget}}
- Target Deployment Frequency: {{deployment_frequency}}
Task
Generate an analytical diagnostic report on the current {{ci_platform}} delivery pipeline, diagnosing bottlenecks across build, test, and artifact packaging phases, and outlining an actionable optimization roadmap to meet {{deployment_frequency}} without exceeding {{cloud_compute_budget}}.
Method
- Analyze the pipeline execution stages against the {{repository_size}} baseline to pinpoint serial bottlenecks.
- Quantify compute waste caused by the {{flaky_test_rate}} and calculate wasted runner hours.
- Evaluate dependency caching, workspace reuse, and remote compilation strategies for {{ci_platform}}.
- Define intelligent test selection and test sharding topologies to reduce the {{current_build_duration}}.
- Model resource allocation changes against the {{cloud_compute_budget}} constraints.
- Formulate deterministic test isolation rules to quarantine unstable suites.
- Establish step-by-step implementation milestones categorized by effort and time-to-value.
Constraints
- MUST cite specific configuration techniques appropriate for {{ci_platform}}.
- MUST NOT recommend unbounded auto-scaling that breaches {{cloud_compute_budget}}.
- Focus strictly on technical build, test, and infrastructure performance.
- Limit architectural recommendations to standard containerized and ephemeral agent patterns.
Output format
Deliver a formal technical report with the following structure:
- Executive Summary (max 150 words)
- Pipeline Stage Duration Diagnostic (table breakdown of stages, current vs target duration)
- Root Cause Analysis of Flakiness & Bottlenecks (3 core findings)
- Compute Optimization & Caching Strategy
- Phased Remediation Plan (3 sequential rollout phases)
Self-review
- Does the report address both {{current_build_duration}} reduction and {{flaky_test_rate}} mitigation?
- Are cost projections fully compliant with {{cloud_compute_budget}}?
- Are runner parallelism and caching steps technically viable for {{repository_size}}?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.