'rollout' 검색 결과

IoT 기기 그룹에 펌웨어를 단계적으로 배포합니다. 소수 기기의 이상을 확인한 뒤 범위를 넓히며, 배포 상태 조회와 롤백도 관리합니다.

• 기기 그룹에 지정한 펌웨어 버전 배포
• 선행 배포 확인 후 배포 범위 확대
• 펌웨어 배포 롤백

Inventory feature flags, switches that control feature availability, and remove eligible flags with their unused code branches. Leave ongoing rollouts and experiments untouched, run verification checks, and prepare a pull request for human review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Removing flags after a feature has fully rolled out
• Cleaning up unused flags and unreachable code branches
• Listing ongoing rollouts and experiments for human review

Configures the rollout shape of a PostHog experiment — the variant split (50/50, 80/20, A/B/C ratios), the overall rollout percentage that gates how many users enter the experiment, and the disambiguation when a percentage like "roll out to 25%" could mean either. Use when the user mentions a rollout percentage, variant split, or traffic distribution; gives a ratio like 60/40, 70/30, or 80/20; asks "who sees the test variant?"; wants to increase, decrease, or change the rollout or split on a draft or running experiment; weighs equal vs uneven splits; or proposes a mid-experiment split change (often an anti-pattern that needs reset or end-and-restart).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

짙은 보라색 그라데이션으로 기업의 AI 도입 검토용 HTML 슬라이드를 만듭니다. 경영진과 IT·보안 담당자를 위해 위험 관리, 투자 수익과 배포 계획을 정리합니다.

• 경영진에게 AI 도입안 설명
• IT 부서와 위험 관리 검토
• 투자 수익과 배포 계획 정리

Review external integration points for breaking changes that could disrupt existing use. Examine app-server APIs, command-line parameters, configuration loading, and session resumption from saved records, continuing beyond the first issue to cover possible failure paths.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check app-server API compatibility
• Review changes to command-line parameters
• Check compatibility of configuration loading

Plan, review, and retire feature flags, switches that control feature availability. Includes tools to identify aging flags, generate phased release schedules, and check that documentation records ownership and emergency shutdown procedures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan a phased release for a new feature
• Identify old flags for cleanup
• Audit emergency shutdown documentation

Prepare employee communications for organizational changes, tool rollouts, and policy updates. Create announcements, audience-specific FAQs, manager talking points, and a communication calendar, while checking tone, channel choices, and sequencing against the change's impact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing an internal reorganization announcement
• Planning communications for a new tool rollout
• Writing audience-specific FAQs for policy changes

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

An Agentforce agent is moving from build or sandbox to live end-user traffic and the team needs a comprehensive readiness gate: coverage testing, Trust Layer config, guardrails, cost telemetry, observability, rate limits, permissions, rollout strategy, rollback plan, performance benchmarks. Triggers: 'we want to ship our Agentforce agent next week', 'pre-prod readiness review for our Service Agent', 'what do we need before turning the agent on for real customers', 'agent went live and is hallucinating, what should we have caught', 'cost monitoring for our internal sales agent', 'rollout strategy from internal pilot to GA'. NOT for the lighter five-block activation sign-off artifact — use agentforce/agent-deployment-checklist. NOT for authoring the guardrails themselves — use agentforce/agentforce-guardrails. NOT for building the test harness — use agentforce/agentforce-eval-harness. NOT for Trust Layer feature setup in isolation — use agentforce/einstein-trust-layer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

운영 환경에 공개하기 전 품질, 보안, 성능, 사용성을 점검하고 모니터링과 롤백을 준비합니다. 공개 후 확인과 지표에 따른 단계적 배포도 다룹니다.

• 첫 운영 환경 공개 전 준비 확인
• 주요 기능의 단계적 공개 계획
• 모니터링과 공개 후 확인 절차 정리

Clarify how a product differs from competitors and test whether buyers value that difference. The skill guides competitor messaging reviews, assessments of hard-to-copy strengths, wording comparisons, and a phased rollout of validated positioning.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying differences from competitors
• Testing website headlines and sales wording
• Planning a phased positioning rollout

Create rollout plans for application and infrastructure changes. Organize readiness checks, deployment steps, health indicators, rollback procedures, and stakeholder communications, adapting the detail to the target environment, change type, and level of risk.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare a production deployment plan
• Define rollback steps and decision criteria
• Set post-deployment health checks

Manage OpenWork feature releases with feature flags, switches that control access to new behavior. Register features before coding, release them by organization and deployment, prepare a global shutdown option, and remove temporary flags after rollout.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Registering a feature before implementation
• Releasing a feature to selected organizations
• Separating cloud and self-hosted availability

Add, read, or remove feature flags, switches that control feature availability, in a web app and Rust backend. The skill covers PostHog rollout controls, environment settings, loading behavior, and cleanup after a feature is fully released.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add a flag for a staged feature rollout
• Configure an environment-specific feature switch
• Check all entry points and flag loading behavior

The operational playbook for launching a feature well. Positioning, internal alignment, customer comms, sales enablement, support readiness, rollout strategy, monitoring with pre-defined rollback triggers, post-launch measurement against spec hypotheses, and the discipline that distinguishes shipping from releasing from actually launching. Triggers on launch plan, feature launch, launch checklist, ship vs release, rollout strategy, gradual rollout, sales enablement, support readiness, launch announcement, post-launch measurement, launch failure, declared victory too early. Also triggers when planning a launch (any size, any segment), auditing an existing launch process, fixing the we shipped it but the metric did not move problem, or building a launch checklist for the team.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validate release readiness with evidence-based go/no-go decisions. Covers go/no-go checklists, smoke test suite design, staged rollout validation, rollback criteria and procedures, and post-deployment verification. Ensures release confidence comes from data, not feelings. Use when: "release ready," "go/no-go," "smoke test," "release checklist," "rollback plan," "staged rollout," "canary deploy." Not for: safe-release techniques (flags, canary, dark launch) applied during the rollout itself — use testing-in-production; scheduled probes that run continuously after release — use synthetic-monitoring; designing new tests from prod telemetry — use observability-driven-testing. Related: testing-in-production, qa-metrics, ci-cd-integration, ai-system-testing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design and execute A/B tests for ML models in production using traffic splitting, statistical significance testing, and canary/shadow deployment strategies. Measure performance differences and make data-driven decisions about model rollout. Use when validating a new model version before full rollout, comparing candidate models trained with different algorithms, measuring business metric impact of model changes, or when regulatory requirements mandate gradual rollout.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when introducing a feature flag system, choosing between release flags / experiment flags / operational flags / kill switches / permission flags, designing percentage rollouts, building kill-switch + circuit-breaker patterns, structuring evaluation contexts (user IDs, plan tier, region), or building flag-cleanup discipline. Triggers: LaunchDarkly / GrowthBook / Unleash / Flagsmith / OpenFeature, percentage ramp, sticky bucketing, kill switch wired to alerting, "we still have flags from 2 years ago", flag debt, OpenFeature provider, evaluation context, default value on provider failure. NOT for A/B test statistical analysis (separate skill), traffic-split routing at the edge, build-time bundler defines, or environment-based config.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Ensure design/ADR changes include a concrete migration plan, rollout strategy, rollback conditions, and compatibility considerations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides agents through the 3-step experiment creation flow: defining the hypothesis, configuring rollout, and setting up analytics. Delegates rollout decisions to configuring-experiment-rollout and metric setup to configuring-experiment-analytics. TRIGGER when: user asks to create a new experiment or A/B test, OR when you are about to call experiment-create. DO NOT TRIGGER when: user is updating an existing experiment, managing lifecycle, or only browsing experiments.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when introducing a feature flag system, choosing between release flags / experiment flags / operational flags / kill switches / permission flags, designing percentage rollouts, building kill-switch + circuit-breaker patterns, structuring evaluation contexts (user IDs, plan tier, region), or building flag-cleanup discipline. Triggers: LaunchDarkly / GrowthBook / Unleash / Flagsmith / OpenFeature, percentage ramp, sticky bucketing, kill switch wired to alerting, "we still have flags from 2 years ago", flag debt, OpenFeature provider, evaluation context, default value on provider failure. NOT for A/B test statistical analysis (separate skill), traffic-split routing at the edge, build-time bundler defines, or environment-based config.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

후보 탐색과 비교를 반복하며 근거와 판단을 추가 기록 방식의 장부에 남깁니다. 이전 결과와의 일관성과 재검증 결과를 확인하고 실거래나 운영 작업의 실행 조건을 명확히 합니다.

• 여러 차례 시도하며 후보를 비교할 때
• 판단의 근거를 기록할 때
• 새 정보로 이전 채택 후보를 재평가할 때