loom-ci-cd-and-automationlisted

# loom-ci-cd-and-automation CI/CD and automation is a playbook for executable quality gates and release paths. It specifies pipeline behavior, implements it in scoped tickets, records observed pipeline results, and audits risky automation changes. ## Loom Routing Common routes use these Loom skills for durable records or follow-up workflow: `loom-specs`, `loom-plans`, `loom-tickets`, `loom-evidence`, `loom-audit`, `loom-research`, and `loom-retrospective`. Follow any named Loom skill fully. This playbook adds workflow pressure; it does not shorten target-skill requirements. ## Use This Playbook When Use this playbook when: - setting up or changing CI checks - adding lint, type check, test, build, security, bundle, or E2E gates - configuring preview, staging, production, rollback, or release automation - debugging CI failures - changing deployment credentials, environments, or secrets handling - adding automation that agents or humans will rely on for closure claims ## Route Use this route: ```text contract -> pipeline -> implement -> observe -> harden -> recover ``` ## Contract Use `loom-specs` when pipeline behavior is durable. Specify: - triggers - required checks - environments - secret boundaries - artifact retention - branch or tag behavior - failure behavior - manual approval points - rollback or retry behavior - what evidence a passing run provides Use `loom-plans` when the automation change spans several tickets or migration stages. ## Pipeline Shape