| name | playbook-template-authoring |
| description | Use only when explicitly authoring or revising reusable, repo-neutral playbook/template skills for deployment, infrastructure operations, data fetching/analysis, or library/API reference guidance. Do not use for normal E2E implementation, executing deployments, running infrastructure changes, one-off data analysis, or applying a library directly. |
| metadata | {"short-description":"Reusable playbook/template authoring","resources":["references/data-fetching-analysis-checklist.md","references/deployment-checklist.md","references/infrastructure-operations-checklist.md","references/library-api-cli-summary.md"],"templates":["templates/data-analysis-report-template.md","templates/deployment-report-template.md","templates/infrastructure-operations-report-template.md"]} |
Purpose
Use this skill to create reusable playbook/template packages that other repositories can copy and specialize without embedding real secrets, production data, or org-specific endpoints.
This skill is for explicit template authoring, not for running the workflow described by a template and not for ordinary E2E software implementation.
When to use
Use this skill only when the requested output is a reusable skill, runbook template, checklist, report template, reference template, or canonical example for one of these modes:
- Deployment: CI/CD release playbooks with preflight, artifact integrity, smoke tests, staged rollout, verification, rollback triggers, and deployment reports.
- Infrastructure operations: day-2 ops runbooks with pre-check, dry-run, blast-radius controls, approval gates, phased apply, soak/cleanup, audit logs, and execution reports.
- Data fetching/analysis: repeatable analysis playbooks with scoped questions, source inventory, canonical keys, safe query patterns, limitations, and reproducibility notes.
