53건 · 관련도순
Feature flag strategy, lifecycle, and operations. Use when designing a flag taxonomy, planning a gradual rollout, building kill switches, auditing flag debt, defining governance, running progressive delivery, or rolling back via flags.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan and execute a new brand launch — from internal rollout to public debut. Use when the user says "launch the brand", "brand launch plan", "how do we introduce the brand", "brand reveal", "brand debut", "going public with the brand", "announcing the new brand", "brand launch strategy", "pre-launch brand", "brand rollout", "introducing our brand to the market", or is ready to take a new or refreshed brand from internal to external. Also use for soft launches, hard launches, and phased rollouts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prepares delivery pipelines and remote infrastructure, then executes authorized rollouts; not standalone quality-gate setup or local container packaging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement GitOps continuous delivery for Kubernetes using ArgoCD or Flux. Use for automated deployments with Git as single source of truth, pull-based delivery, drift detection, multi-cluster management, and progressive rollouts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prevent Kubernetes hallucinations by diagnosing and fixing failure modes: insecure workload defaults, resource starvation, network exposure, privilege sprawl, fragile rollouts, and API drift. Use when generating, reviewing, refactoring, or migrating manifests, Helm charts, Kustomize overlays, cluster policies, and platform-specific Kubernetes work for EKS, GKE, AKS, OpenShift, GitOps controllers, or observability stacks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing, implementing, reviewing, testing, or cleaning up feature toggles, feature flags, kill switches, runtime configuration gates, canary controls, staged rollouts, experiments, or temporary compatibility switches in Java enterprise systems. This should trigger for requests such as Design a feature toggle strategy; Review this feature flag; Add a kill switch safely; Test toggle on and off paths; Clean up an expired feature toggle; Plan controlled rollout and rollback behavior. Part of Plinth Toolkit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Safe-release techniques DURING rollout: feature flags, progressive rollouts, canary analysis, guardrail metrics, production smoke tests, and synthetic users. Bridges QA and SRE practices. Use when: "feature flag testing," "canary deploy," "progressive rollout," "guardrail metrics," "dark launch," "safe rollout." Not for: scheduled probes that run continuously after release — use `synthetic-monitoring`. Not for: designing tests from prod telemetry — use `observability-driven-testing`. Related: release-readiness, synthetic-monitoring, observability-driven-testing, qa-metrics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manages ArgoCD application syncs using the argocd CLI and the Argo CD REST API (v1alpha1). Supports progressive delivery with Argo Rollouts integration and automated health checks via Kubernetes readiness probes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrates deployment pipelines using the Argo Workflows Engine API and Argo CD ApplicationSet controller. Implements progressive delivery with Argo Rollouts canary and blue-green strategies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan safe Convex schema and data migrations. Use for widen-migrate-narrow rollouts, backfills, breaking field changes, table splits, or failed schema deploys.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a Go-to-Market (GTM) plan for new product launches, market entries, or feature rollouts. Covers market sizing (TAM/SAM/SOM), positioning, messaging, channel strategy, pricing approach, and launch timeline. Use when preparing to bring something new to market. Do not use for ongoing marketing operations or campaign execution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan launch readiness, staged rollouts, production monitoring, rollback, communications, and post-launch validation. Use when the user asks for `/ship`, pre-launch checklists, release readiness, staged rollout plans, feature flags, deployment monitoring, or rollback planning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan, communicate, and execute organizational change with structured frameworks. Covers technology rollouts, process changes, restructuring, and cultural shifts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Blue-green and canary deployment orchestrator with traffic shifting and automated rollback. Activate on: blue-green deployment, canary release, rolling deployment, traffic shifting, rollback automation, progressive delivery, Argo Rollouts, Flagger. NOT for: K8s manifest generation (use kubernetes-manifest-generator), CI/CD pipeline setup (use github-actions-pipeline-builder), monitoring (use monitoring-stack-deployer).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with feature flags — Laravel Pennant, gradual rollouts, A/B testing, scope-based flags — even when the user just says 'hide this behind a flag' without naming Pennant.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plans Convex schema and data migrations with widen-migrate-narrow and @convex-dev/migrations. Use for breaking schema changes, backfills, table reshaping, or zero-downtime rollouts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plans Convex schema and data migrations with widen-migrate-narrow and @convex-dev/migrations. Use for breaking schema changes, backfills, table reshaping, or zero-downtime rollouts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Config Cat — configCat feature flag management, remote configuration, A/B testing, targeting rules, and percentage-based rollouts. Covers flag listing, targeting rule management, environment overrides, audit log review, and SDK integration status. Use when managing feature flags, reviewing targeting rules, analyzing flag usage, or auditing configuration changes in ConfigCat.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
BDB Shipping Godmode, the final gatekeeper for production releases. Use when running pre-launch checks, feature-flag rollouts, or rollback planning under Spec-Driven Development before a release ships.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plans Convex schema and data migrations with widen-migrate-narrow and @convex-dev/migrations. Use for breaking schema changes, backfills, table reshaping, or zero-downtime rollouts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for using completers — TokenCompleter and MessageCompleter for text generation during RL rollouts and evaluation. Use when the user asks about generating text, completing messages, or using completers in RL environments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Busabase-backed App-in-Skill dashboard for a shared LLM gateway's cost and model governance — daily spend trend, cost breakdown by service/model, a canary-rollout status board, and a deterministic cost/error anomaly list. Use when the user invokes $kelly-llm-gateway or /kelly-llm-gateway, or wants to review LLM gateway spend, model routing, canary rollouts, rollback readiness, or cost/error anomalies for services routed through one shared gateway to multiple LLM providers/models. Human actions (promote/rollback/hold a rollout, acknowledge an anomaly) write directly onto the route's own Busabase record — this skill never changes a real routing config.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add PostHog feature flags to gate new functionality. Use after implementing features or reviewing PRs to ensure safe rollouts with feature flag controls. Also handles initial PostHog SDK setup if not yet installed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add feature flags to an application for gradual rollouts, A/B testing, and kill switches using PostHog, LaunchDarkly, or a simple local implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.