Skip to main content
skill CX Codex

057-design-feature-toggles — Claude Code skill: feature flags

057-design-feature-toggles — an interactive skill for designing and reviewing feature toggles in Java services, including kill switches, staged rollouts, experiments, and cleanup.

Apache-2.0 171 installs ★ 465 updated 2026-10-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jabrena/plinth --skill 057-design-feature-toggles -a claude-code
Open on GitHub

What 057-design-feature-toggles does

This skill guides decisions about runtime controls in Java Enterprise systems. It helps distinguish a feature toggle from a branch, configuration edit, deployment change, or parallel implementation, then defines the toggle category, owner, lifetime, default state, rollout audience, and removal trigger.

The workflow builds a typed toggle contract around a centralized decision point. It covers fallback behavior, evaluation context, audit needs, metrics, logs, rollback controls, and consistent decisions across a request, transaction, message, or batch item. It also checks enabled and disabled paths, configuration failures, targeting rules, observability, and cleanup readiness.

Read references/057-design-feature-toggles.md before applying the guidance; the skill requires that reference as its first step. It is aimed at Java Enterprise code and rejects hidden conditional complexity, weakened security controls, and permanent branches without explicit ownership.

What it helps with

  • choose the right feature toggle category
  • define defaults, fallback, rollout, and rollback rules
  • centralize flag evaluation in a Java service
  • test enabled, disabled, and configuration-failure paths
  • plan removal of an expired toggle

Example prompts for the agent

  • Design a feature toggle strategy for this Java service, including ownership, lifetime, rollout audience, and removal trigger.
  • Review this kill switch implementation for fallback behavior, rollback safety, and configuration failure handling.
  • Create a test matrix for both toggle paths and outline the cleanup plan for this temporary flag.

How to install 057-design-feature-toggles

1Skills CLI (Vercel)

npx skills add jabrena/plinth --skill 057-design-feature-toggles -a claude-code

2Manually: put the files in place

~/.claude/skills/057-design-feature-toggles/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/057-design-feature-toggles/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about 057-design-feature-toggles

How do I install 057-design-feature-toggles in Claude Code?

Run npx skills add jabrena/plinth --skill 057-design-feature-toggles -a claude-code, then verify ~/.claude/skills/057-design-feature-toggles/SKILL.md.

What does 057-design-feature-toggles do?

It guides the design, implementation review, testing, rollout, rollback, and removal of feature toggles in Java Enterprise systems. Its workflow covers typed decisions, fallback behavior, observability, and cleanup.

What must be done before using the skill?

Read references/057-design-feature-toggles.md first. The toggle plan should also define its type, owner, expected lifetime, default state, and removal trigger.

Source text

SKILL.md · Apache-2.0
---
name: 057-design-feature-toggles
description: 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
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral, Sangwon Park
  version: 0.19.0
---
# Feature Toggles Design

Guide Java Enterprise developers through safe feature toggle design and lifecycle management. **This is an interactive SKILL**.

**What is covered in this Skill?**

- Deciding when a feature toggle is appropriate versus a branch, configuration change, deployment change, or parallel change
- Classifying release toggles, operational kill switches, experiment toggles, permission toggles, and migration toggles
- Designing typed toggle ownership, defaults, evaluation scope, fallback behavior, observability, and rollback controls
- Implementing toggles in Java services without scattering flag checks or creating hidden long-term complexity
- Reviewing toggles for release, rollback, security, privacy, concurrency, and maintenance risk
- Testing both enabled and disabled paths, configuration failure behavior, rollout rules, and cleanup readiness

## Constraints

Use feature toggles as explicit, owned runtime control points rather than hidden conditional complexity.

- **MUST** read `references/057-design-feature-toggles.md` before applying feature toggle guidance
- **MUST** classify the toggle type, owner, expected lifetime, default state, rollout audience, and removal trigger before recommending implementation
- **MUST** design safe defaults, fallback behavior, observability, and rollback behavior for runtime evaluation failures
- **MUST** keep toggle evaluation centralized, typed, and testable instead of scattering raw configuration lookups through business logic
- **MUST** include cleanup expectations for temporary toggles before implementation is considered complete
- **MUST NOT** use feature toggles to hide incomplete design decisions, weaken security controls, or leave permanent branches without explicit ownership

## When to use this skill

- Design a feature toggle strategy
- Review this feature flag implementation
- Add a kill switch safely
- Plan a canary or staged rollout in a Java service
- Test toggle on and off paths
- Clean up an expired feature toggle
- Decide whether this runtime behavior change needs a toggle

## Workflow

1. **Classify the Toggle Need**

Read `references/057-design-feature-toggles.md`, then identify the runtime behavior change, rollout risk, rollback expectation, affected users, operational owner, and whether a feature toggle is the smallest safe control mechanism.

2. **Design the Toggle Contract**

Define the toggle type, stable name, typed decision API, default state, evaluation context, fallback behavior, audit needs, metrics, logs, and cleanup trigger. Prefer one decision point per behavior over repeated raw flag checks.

3. **Plan Implementation Boundaries**

Place toggle evaluation near an application service, adapter, strategy selector, or request boundary. Keep domain code explicit, avoid secret or personal data in rules, and preserve consistent decisions across a request, transaction, message, or batch item.

4. **Review Release and Rollback Safety**

Check whether disabled behavior preserves the current production contract, enabled behavior has rollout guardrails, operational teams can disable the behavior quickly, and cleanup will not break old deployments, data, or integrations.

5. **Test and Observe Both Paths**

Test disabled, enabled, fallback, configuration failure, rollout targeting, and cleanup scenarios. Add metrics, logs, alerts, or dashboards that show toggle state, decision volume, error rate, latency impact, and kill-switch activation.

6. **Report the Toggle Plan**

Report the decision, toggle contract, implementation boundary, test matrix, observability plan, rollout and rollback steps, cleanup owner, removal trigger, skipped checks, and remaining risks.

## Reference

For detailed guidance, examples, and constraints, see [references/057-design-feature-toggles.md](references/057-design-feature-toggles.md).

© Juan Antonio Breña Moral, Sangwon Park · Apache-2.0 · jabrena/plinth

Similar skills

All skills for Backend and APIs →

From the same set123

The whole set →
056-design-avoid-breaking-changes 056-design-avoid-breaking-changes reviews plans, OpenSpec changes, and APIs for breaking changes and migration risks before release. CX Codex +1 172installs 055-design-parallel-change The 055-design-parallel-change skill guides you through designing safe database schema changes when old and new application versions must run simultaneously. It breaks complex migrations into three separately deployable phases. CX Codex +1 172installs 052-design-hamburger-method 052-design-hamburger-method splits oversized user stories and specs into thin vertical slices using the Hamburger Method. Delivers end-to-end observable value instead of isolated technical tasks. CX Codex +1 172installs 053-design-simple-rules 053-design-simple-rules is a Claude skill that checks Java design and refactoring decisions against Kent Beck's four rules, in order. CX Codex +1 172installs 051-design-two-steps-methods The 051-design-two-steps-methods skill splits complex or risky code changes into two steps: first refactor to improve design while preserving behavior, then apply the intended behavior change. CX Codex +1 170installs 045-planning-azure-devops 045-planning-azure-devops manages Azure Boards work items via the Azure DevOps CLI. It verifies tool availability first and restricts query outputs strictly to IDs and counts. CX Codex +1 168installs 811-regulations-eu-market-abuse-regulation The 811-regulations-eu-market-abuse-regulation skill reviews Java systems for EU Market Abuse Regulation controls, reviewable evidence, alert decisions, and escalation paths. CX Codex +1 166installs 813-regulations-iso-42001 813-regulations-iso-42001 reviews Java systems that use GenAI against ISO/IEC 42001 concerns and turns findings into engineering controls, evidence, and owner handoffs. CX Codex +1 165installs

Project sponsors

Companies that keep this analytics open