DevOps Workflow Engineer
Generate GitHub Actions workflow YAML, analyze existing pipelines for optimization opportunities, and create deployment plans with strategy selection, health checks, and rollback procedures.
Core Capabilities
- CI pipeline design — fail-fast job ordering (lint → unit → build → integration → security) with matrix testing and CI time/flake/cache targets.
- CD & multi-environment — dev/staging/prod promotion flows, build-once-deploy-everywhere, environment protection rules, and rollback at every stage.
- Pipeline optimization — detect missing caching, missing timeouts, serial chains, deprecated actions, leaked secrets, and oversized runners; apply path filtering and concurrency cancellation.
- Deployment strategies — choose blue-green, canary, or rolling via decision tree; canary traffic-split schedule with promotion gates.
- GitHub Actions patterns — reusable workflows, OIDC auth, secrets hierarchy, and runner cost estimation.
When to Use
- Designing a new CI or CD workflow from scratch.
- Planning a multi-environment (dev/staging/prod) deployment.
- Optimizing an existing pipeline's cost or runtime.
- Implementing a blue-green, canary, or rolling deployment strategy.
Clarify First
Before generating the workflow, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Tools
| Tool |
Purpose |
Command |
workflow_generator.py |
Generate GitHub Actions YAML (ci, cd, release, security-scan, docs-check) |
python scripts/workflow_generator.py --type ci --language python --test-framework pytest |
pipeline_analyzer.py |
Analyze workflows for optimization findings, cost estimates, severity ratings |
python scripts/pipeline_analyzer.py .github/workflows/ --format json |
deployment_planner.py |
Generate a deployment plan with strategy, health checks, rollback |
python scripts/deployment_planner.py --type webapp --environments dev,staging,prod --strategy canary |
All tools support --format json and --output/-o for file writing.
References
Load the reference that matches the task — keep this file lean and pull detail on demand:
- references/workflows-and-optimization.md — the CI / CD / optimization workflows with full YAML, deployment-strategy decision tree and canary schedule, GitHub Actions patterns, runner cost table, anti-patterns, and troubleshooting. Read when building or tuning a pipeline.
- references/github-actions-patterns.md — deep GitHub Actions pattern library. Read when authoring advanced workflow YAML.
- references/deployment-strategies.md — deep deployment strategy guide (blue-green, canary, rolling). Read when planning a release rollout.
- references/agentic-workflows-guide.md — agentic/automated workflow patterns. Read when wiring up AI-driven or autonomous pipeline steps.
Integration Points
| Skill |
Integration |
release-orchestrator |
Release workflows align with versioning and changelog |
senior-devops |
Deployment strategies complement infra automation |
senior-secops |
Security scanning steps feed SecOps dashboards |
senior-qa |
CI quality gates map to QA acceptance criteria |
incident-commander |
Rollback procedures connect to incident playbooks |
1---2name: devops-workflow-engineer3description: Generate and optimize GitHub Actions CI/CD workflows. Use when designing workflows, planning multi-environment deployments, optimizing pipeline cost and runtime, or implementing blue- green, canary, or rolling deployment strategies.4license: MIT + Commons Clause5---6# DevOps Workflow Engineer
7
8Generate GitHub Actions workflow YAML, analyze existing pipelines for optimization opportunities, and create deployment plans with strategy selection, health checks, and rollback procedures.
9
10## Core Capabilities
11
12- **CI pipeline design** — fail-fast job ordering (lint → unit → build → integration → security) with matrix testing and CI time/flake/cache targets.
13- **CD & multi-environment** — dev/staging/prod promotion flows, build-once-deploy-everywhere, environment protection rules, and rollback at every stage.
14- **Pipeline optimization** — detect missing caching, missing timeouts, serial chains, deprecated actions, leaked secrets, and oversized runners; apply path filtering and concurrency cancellation.
15- **Deployment strategies** — choose blue-green, canary, or rolling via decision tree; canary traffic-split schedule with promotion gates.
16- **GitHub Actions patterns** — reusable workflows, OIDC auth, secrets hierarchy, and runner cost estimation.
17
18## When to Use
19
20- Designing a new CI or CD workflow from scratch.
21- Planning a multi-environment (dev/staging/prod) deployment.
22- Optimizing an existing pipeline's cost or runtime.
23- Implementing a blue-green, canary, or rolling deployment strategy.
24
25## Clarify First
26
27Before generating the workflow, confirm these inputs. If any is unknown or vague, ASK — do not assume:
28
29- [ ] **Workflow type** — CI, CD, release, or security-scan (sets `workflow_generator.py --type`)
30- [ ] **Stack** — language and test framework (e.g. python/pytest) (drives the generated YAML steps via `--language`/`--test-framework`)
31- [ ] **Deployment strategy & environments** — blue-green, canary, or rolling, and which of dev/staging/prod (drives the `deployment_planner.py` plan)
32
33Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
34
35## Tools
36
37| Tool | Purpose | Command |
38|------|---------|---------|
39| `workflow_generator.py` | Generate GitHub Actions YAML (ci, cd, release, security-scan, docs-check) | `python scripts/workflow_generator.py --type ci --language python --test-framework pytest` |
40| `pipeline_analyzer.py` | Analyze workflows for optimization findings, cost estimates, severity ratings | `python scripts/pipeline_analyzer.py .github/workflows/ --format json` |
41| `deployment_planner.py` | Generate a deployment plan with strategy, health checks, rollback | `python scripts/deployment_planner.py --type webapp --environments dev,staging,prod --strategy canary` |
42
43All tools support `--format json` and `--output`/`-o` for file writing.
44
45## References
46
47Load the reference that matches the task — keep this file lean and pull detail on demand:
48
49- **[references/workflows-and-optimization.md](references/workflows-and-optimization.md)** — the CI / CD / optimization workflows with full YAML, deployment-strategy decision tree and canary schedule, GitHub Actions patterns, runner cost table, anti-patterns, and troubleshooting. Read when building or tuning a pipeline.
50- **[references/github-actions-patterns.md](references/github-actions-patterns.md)** — deep GitHub Actions pattern library. Read when authoring advanced workflow YAML.
51- **[references/deployment-strategies.md](references/deployment-strategies.md)** — deep deployment strategy guide (blue-green, canary, rolling). Read when planning a release rollout.
52- **[references/agentic-workflows-guide.md](references/agentic-workflows-guide.md)** — agentic/automated workflow patterns. Read when wiring up AI-driven or autonomous pipeline steps.
53
54## Integration Points
55
56| Skill | Integration |
57|-------|-------------|
58| `release-orchestrator` | Release workflows align with versioning and changelog |
59| `senior-devops` | Deployment strategies complement infra automation |
60| `senior-secops` | Security scanning steps feed SecOps dashboards |
61| `senior-qa` | CI quality gates map to QA acceptance criteria |
62| `incident-commander` | Rollback procedures connect to incident playbooks |