Verified:GitHub

Harness Feature Flags

Govern feature flags across codebases with lifecycle policies and automated cleanups.

18|11|Updated Mar 16, 2026

Search Tags:#feature flags #a/b testing #gradual rollout #rollout strategy #kill switch #release governance #flag lifecycle

Ready to run

npx skills add https://github.com/Intense-Visions/harness-engineering --skill harness-feature-flags

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Harness Feature Flags
Source: https://github.com/Intense-Visions/harness-engineering/tree/main/agents/skills/claude-code/harness-feature-flags
Command: npx skills add https://github.com/Intense-Visions/harness-engineering --skill harness-feature-flags

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and governs feature flag usage to reduce risk during releases, enabling safe experiments, controlled rollouts, and clear ownership with automated hygiene rules.

Core Features & Use Cases

Flag lifecycle management: Define, enable/disable, and retire flags with documented ownership and timelines.
A/B testing infrastructure: Design experiments with consistent user assignment and outcome tracking.
Gradual rollout governance: Implement percentage rollouts, segment targeting, and kill switches to minimize blast radius.
Governance and hygiene: Enforce default values, naming conventions, and automatic cleanup processes.
Use Case: Roll out a new search algorithm to 5% of users, measure impact, and incrementally increase exposure with a safety net.

Quick Start

Enable your first feature flag in your project and begin a gradual rollout to a small user segment.

Frequently Asked Questions about Harness Feature Flags

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage feature flag lifecycle and ownership across multiple deployment environments?▼

Feature flag lifecycle management involves defining, enabling, disabling, and retiring flags with documented ownership and timelines. You can catalog and govern feature flags across codebases to maintain clear ownership and automated hygiene rules.

What is the best way to implement a gradual rollout with a kill switch for a new release?▼

Gradual rollout governance is implemented using percentage rollouts, segment targeting, and kill switches to minimize blast radius. This approach allows you to incrementally increase exposure while maintaining a safety net to instantly revert if issues arise.

How do I set up A/B testing infrastructure with consistent user assignment?▼

A/B testing infrastructure is designed to run experiments with consistent user assignment and outcome tracking. This ensures users remain in their assigned test groups across sessions, providing accurate measurement of the experiment's impact.

How do I enforce feature flag hygiene and naming conventions in my codebase?▼

Feature flag hygiene is enforced by applying default values, strict naming conventions, and automatic cleanup processes. This governance prevents flag accumulation and ensures flags are retired with documented timelines once their lifecycle ends.

Can I target a specific user segment for a feature flag rollout?▼

Yes, segment targeting is a core component of gradual rollout governance. You can roll out features to a specific user segment, such as exposing a new search algorithm to 5% of users, measuring the impact, and safely scaling exposure.

Why do I need release governance for feature flags?▼

Release governance for feature flags reduces risk during releases by centralizing control. It enables safe experiments, controlled rollouts, and clear ownership with automated hygiene rules, preventing untracked flags from causing deployment issues.