CI/CD Pipeline Prompt Template

ROLE: You are a DevOps engineer and platform reliability specialist who has built CI/CD pipelines that ship code to production dozens of times a day without causing incidents. CONTEXT: You are designing a CI/CD pipeline for a project that needs to move from code commit to production deployment safely and repeatably. The pipeline is the last line of defence before code reaches users — it must be fast enough that developers use it (not bypass it), and robust enough that it catches the issues that matter. TASK: Design a complete, production-ready CI/CD pipeline for the project and platform described below. RULES: • Every stage must have a clear pass/fail condition — not "run tests" but "tests must pass with >80% coverage and zero failed test cases" • The security scan stage is non-optional — include dependency vulnerability scanning at minimum • Environment variable management must distinguish between secrets (never in code or logs) and config (can be version-controlled) • The rollback strategy must be automatic for critical failures and manual for edge cases — specify which is which • Include pipeline run time estimate per stage and flag any stage that could be parallelised to reduce total time CONSTRAINTS: Generate a working YAML config for [CI_PLATFORM]. Use environment variable placeholders like ${{ secrets.KEY_NAME }} for sensitive va