writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
Use when you have a spec or requirements for a multi-step task, before touching code
Expert DevOps automation consultant for building production-grade CI/CD deployment pipelines using Vercel, GitHub Actions, and Railway. Implements build/test/preview/production workflows, automated rollbacks, canary deployments, blue-green strategies, environment promotion, secrets management, health checks, smoke testing, and live monitoring. Use when deploying web applications, setting up CI/CD pipelines, configuring automated deployments, implementing deployment strategies, managing production releases, or troubleshooting deployment issues.
Checklist gate สำหรับ production release ครอบคลุม testing, documentation, rollback plan, และ stakeholder sign-off
Enforce CA Lobby phase planning protocol following master project plan. Use when starting new CA Lobby phases, planning implementations, or user says "start phase" or "plan phase". Ensures master plan consultation and proper CA Lobby documentation structure.
Creates CI/CD pipeline configurations for automated testing and deployment
Prep workflow before autonomous ralph-wiggum loops. Use when: (1) starting overnight/long autonomous runs, (2) user says "long session", "overnight", "autonomous", (3) work will span multiple sessions without user interaction.
Reference for NixOS build, test, and flake commands. Use when asked about rebuilding, checking config, formatting, or flake operations.
Builds complete features full-stack (backend + frontend + tests). Triggers when user wants to implement a feature, add functionality, or build a specific capability.
Master orchestrator control for PR lifecycle management with multi-agent coordination
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes
Generate Helm chart files for Kubernetes application deployment. Triggers on "create helm chart", "generate helm template", "kubernetes helm", "helm package".
Use when user requests "parallel" commands, running multiple builds/tests simultaneously, or long-running tasks. Use `gob add` instead of parallel Bash tool calls - gob provides job management, output capture, and proper process control.
This skill should be used when the user asks to 'verify completion', 'check that tests pass', 'confirm feature works', or REQUIRED Phase 7 of /dev workflow (final). Enforces fresh runtime evidence before claiming completion.
Gate 2 of the development cycle. VALIDATES that observability was correctly implemented by developers. Does NOT implement observability code - only validates it.
Vercel deployment workflow for TSH Clients Console. Use when: (1) Deploying changes to production or staging (2) Checking deployment status (3) Troubleshooting deployment issues (4) Setting up environment variables (5) Managing domains and DNS (6) Running cache revalidation after deployment
Plans and executes release and operational readiness tasks, including versioning, changelogs, deployment and rollback.
Use when you have a spec or requirements for a multi-step task, before touching code
Complete ArgoCD API and CLI skill for GitOps automation. Use when working with ArgoCD for: (1) Managing Applications - create, sync, delete, rollback, get status, (2) ApplicationSets - templated multi-cluster deployments, (3) Projects - RBAC, source/destination restrictions, sync windows, (4) Repositories - add/remove Git repos, Helm charts, OCI registries, (5) Clusters - register, rotate credentials, manage multi-cluster, (6) Accounts - generate tokens, manage users, check permissions, (7) Any ArgoCD REST API calls or argocd CLI commands. Supports both REST API (curl/HTTP) and CLI wrapper approaches with bearer token authentication.
Provides the "how-to" for workflow execution orchestration. Defines methods for planning multi-phase workflows, implementing them through agent delegation, managing artifacts, and tracking progress. Pure concepts - no command triggers.
Utilities and patterns for detecting execution environment (CI/CD vs local, network access, available ports, timeouts). Use when you need to adapt scripts or workflows based on where the agent is running, or when creating helper scripts that need environment-aware behavior.