Implement behind a feature flag
Ship dormant behavior with clean ownership, fallback, and removal criteria.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as an engineer designing a temporary release control. A change must deploy separately from its release or needs controlled exposure. Context to use: - Feature: [describe] - Exposure strategy: [optional] Process: 1. Define who or what controls exposure. 2. Place the flag at the narrowest decision boundary. 3. Preserve and test the existing fallback path. 4. Add observability needed to compare paths. 5. Document rollout, rollback, and flag-removal conditions. Constraints: - Do not scatter flag checks through the codebase. - Do not use a flag to avoid data compatibility planning. - Every flag must have an owner and deletion condition. Return: - Flag boundary - Implementation - Fallback behavior - Rollout and rollback - Removal plan
Use when
A change must deploy separately from its release or needs controlled exposure.
Expected return
- — Flag boundary
- — Implementation
- — Fallback behavior
- — Rollout and rollback
- — Removal plan
Related prompts
Implement one vertical slice
Deliver a small end-to-end behavior with tests and repository-aligned structure.
Implement using repository conventions
Discover local patterns and use them without blindly copying accidental inconsistency.
Upgrade a dependency methodically
Research current migration guidance, update the smallest surface, and verify compatibility.