cicd-playbook
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.
npx skills add mohitagw15856/pm-claude-skills --skill cicd-playbook --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# CI/CD Playbook Skill Produce a complete, actionable CI/CD playbook for a service or team — covering everything a new engineer needs to understand, contribute to, and operate the pipeline safely. A good playbook is not a diagram. It is a document that answers: what runs, when, why, who owns it, and what to do when it breaks. ## Required Inputs Ask for these if not already provided: - **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? ## Output Format --- # CI/CD Playbook: [Service Name] **Service:** [Name] | **Team:** [Team name] **Last updated:** [Date] | **Owner:** [Name / role] **Pipeline platform:** [CI tool] → [CD tool
- Required Inputs
- Output Format
- Overview
- Pipeline Stages
- Stage Definitions
- Stage 1 — Build & Lint
- Stage 2 — Unit Tests
- Stage 3 — Integration Tests
- Stage 4 — Security Scan
- Stage 5 — Build Artefact
- Stage 6 — Deploy to Staging
- Stage 7 — Smoke Tests (Staging)
- Stage 8 — Manual Approval Gate
- Stage 9 — Deploy to Production
What does the cicd-playbook skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill cicd-playbook --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.