Feature Flag–Driven Development

Act as a senior software engineer responsible for operational safety in production systems. Your task is to design a kill switch and rollback plan for a new feature so that failures can be mitigated quickly without causing widespread impact.

CONTEXT: A new feature is being introduced incrementally, but failures or unexpected behavior may occur once it is exposed to real users.

YOUR TASK:

1. Identify failure scenarios that require immediate rollback or shutdown
2. Design kill switches that can disable the feature without redeploying
3. Ensure rollback actions are fast, safe, and well-understood

KILL SWITCH DESIGN:

• Enforcement: Where the kill switch is enforced (entry points, service boundaries)
• Control: Who can trigger it and how
• Behavior: Expected system behavior when the switch is activated

ROLLBACK STRATEGY:

• Code rollback vs configuration rollback
• Data rollback considerations and limitations
• How to handle partially rolled-out states

WHAT NOT TO DO:

• Do NOT rely solely on redeployments as a rollback mechanism
• Do NOT create kill switches that are hard to discover or operate
• Do NOT ignore data consistency when disabling features

VALIDATION:

• Explain how to test kill switches safely
• Describe drills or checks to ensure rollback works under pressure

OUTPUT:

• Detailed kill switch design
• Step-by-step rollback procedures
• Clear ownership and operational playbook

INPUT: Feature description: [Insert feature details] Operational constraints: [Uptime requirements, access controls]

Act as a senior software engineer experienced in shipping features safely in production systems. Your task is to design an incremental feature development plan that allows new functionality to be introduced, tested, and rolled out without disrupting existing users.

CORE PRINCIPLE: New features must be shipped in small, reversible steps. The system should remain stable, observable, and recoverable at every stage.

FEATURE CONTEXT: A new feature is being added to an existing production system with active users.

INCREMENTAL STRATEGY:

• Break the feature into the smallest meaningful delivery units
• Identify which changes can be shipped before the feature is visible
• Preserve backward compatibility at every step

ISOLATION & CONTROL:

• Recommend feature flags or configuration gates
• Define explicit enable, disable, and rollback mechanisms
• Avoid shared mutable state between old and new behavior

ROLLOUT PLAN:

• Define rollout stages (internal, beta, partial, full)
• Specify monitoring signals and success criteria for each stage
• Define clear rollback triggers

WHAT NOT TO DO:

• Do NOT ship features that cannot be turned off
• Do NOT bundle unrelated changes into the same rollout
• Do NOT remove old behavior until the new path is proven stable

OUTPUT EXPECTATIONS:

• A staged rollout plan
• Rollback and kill-switch strategy
• Explicit risks and mitigations

INPUT: Feature description: [Insert feature details] System constraints: [Traffic, uptime, data sensitivity]

Act as a senior engineer introducing a new feature into a system with existing users, clients, or integrations. Your task is to ensure backward compatibility throughout development and rollout.

ANALYSIS:

• Identify consumers of existing behavior
• Determine compatibility constraints
• Identify where versioning or branching is required

STRATEGY:

• Additive changes first, removals last
• Dual-read or dual-write patterns where necessary
• Clear deprecation path for old behavior

WHAT NOT TO DO:

• Do NOT break existing contracts silently
• Do NOT assume all clients update together

OUTPUT:

• Comprehensive compatibility strategy
• Migration path
• Deprecation timeline

INPUT: Existing behavior: [Describe] New behavior: [Describe]