CP
CI/CD Playbook
🔵 Stable🕐 updated 2026-06-08
🔷 SkillSpec L3
pm-engineering
Write a CI/CD pipeline playbook for a service or team. Use when asked to document a CI/CD pipeline, write a deployment process, define release gates, document build and test stages, or create a deployment guide. Produces a structured playbook covering pipeline stages, environment definitions, deployment gates, rollback procedures, and on-call responsibilities.
What to give it
▸Service name — and brief description
▸Tech stack — language, framework, containerisation (Docker, etc.)
▸Source control — GitHub / GitLab / Bitbucket, branching strategy
▸CI platform — GitHub Actions / CircleCI / Jenkins / BuildKite / other
▸CD platform / deployment target — Kubernetes, ECS, Lambda, Heroku, VMs, etc.
▸Environments — e.g. dev, staging, production (and any canary / feature environments)
▸Deployment frequency — how often does the team ship?
▸Any existing gates — manual approvals, smoke tests, feature flags
▸On-call setup — who's responsible during deploys?
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓Every stage has a clear owner when it fails
✓Rollback procedure is tested — not theoretical
✓Secrets management section names the actual tool used (not "use secrets management")
✓Deployment window is specific — not "during business hours"
✓Post-deploy check thresholds are calibrated to actual baseline metrics
⚠️ What it refuses to do
Do not describe a rollback procedure that has never been tested — a theoretical rollback is not a rollback plan; test it in staging before production
Do not allow deploys on Fridays or before holidays without an explicit on-call engineer who will monitor through the weekend
Do not commit secrets to source control even in non-production branches — secret scanning in the pipeline catches this, but prevention is the standard
Do not skip post-deploy monitoring after a production deploy — the deploying engineer must watch error rates and latency for the specified observation window
Do not suppress a security scan finding without a linked ticket and a named owner — suppressions without accountability accumulate into unmanaged risk
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcpStart with
Related skills
🔌 Embed this skill
Drop this on your blog, docs, or site — it renders a "Run this skill" card:
<div data-pm-skill="cicd-playbook"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>💬 Discussion
CI/CD Playbook is one of 1078 open-source professional AI agent skills — all SkillSpec L3.
Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog