Feature Flags Architect
Design and review feature-flag architecture: flag types, rollout strategy, kill switches, and cleanup discipline.
Before & after
Same prompt, same agent — the only difference is the skill.
Feature flags are useful for controlling the rollout of new features. You can gradually release a feature to a percentage of users and monitor for issues before going fully live. Some teams use feature flag services that let you toggle features on and off remotely without redeploying code. You'd want to think about who your target users are and how to measure whether the feature is working as intended. It's also important to clean up old flags after a feature is fully rolled out. Different flag services have different capabilities and pricing models.
FEATURE FLAG ROLLOUT ARCHITECTURE FOR BILLING V2: FLAG NAMING STRATEGY • billing_v2_overhaul (main kill switch) • billing_v2_ui_redesign (UX changes only) • billing_v2_invoice_calc (calculation logic) • billing_v2_reporting (new reports) ROLLOUT SCHEDULE (10percent weekly) Week 1: Canary segment (internal QA + 10 friendly accounts) Week 2: 10percent random sample (monitor error rates, latency) Week 3: 20percent (expand if no issues) Week 4: 50percent Week 5+: 100percent (deprecate flag, remove from codebase) TARGET AUDIENCE DEFINITION • Include only accounts with Billing Admin role • Exclude accounts with open billing disputes • Exclude accounts in onboarding (first 7 days) • Include accounts in trial and paid tiers equally MONITORING & ROLLBACK CRITERIA RED FLAGS (automatic rollback): • Error rate spikes above 5percent on invoice creation • P99 latency exceeds 2 seconds • Payment processing fails more than 1percent GREEN LIGHTS (proceed to next segment): • Error rate stable at <1percent • User feedback score >4.0 in new UI • Zero billing dispute increases CLEANUP PLAN After 30 days at 100percent, flag removal: 1. Delete feature flag config from system 2. Remove if/else branches from codebase 3. Archive flag history and ruleset
About this skill
name: skills-feature-flags-architect description: Use when Structured Claude skill that gives Claude a repeatable workflow for skills feature flags architect.
Skills Feature Flags Architect
One of 337+ skills in the original author's multi-agent claude-skills mega-collection (~19k GitHub stars). Packages the Skills Feature Flags Architect workflow with its own instructions and validation so outputs stay consistent.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the skills-feature-flags-architect skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Skills Feature Flags Architect; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: skills-feature-flags-architect
description: Design and review feature-flag architecture — flag types, rollout strategy, kill switches, and cleanup discipline — for a codebase adopting or scaling feature flags.
version: 1.0.0
category: AI Agents / Development
author: AgentVolt
license: proprietary
tags:
- ai-agents
- development
---
# Skills Feature Flags Architect
Design and review feature-flag architecture — flag types, rollout strategy, kill switches, and cleanup discipline — for a codebase adopting or scaling feature flags.
## When to use
… (sign up to view the full skill)More ai & agents skills
View all AI & Agents skills →Skill Status Report
Scan every skill in a project and report which pass validation, which are stale, and which lack required metadata.
Skills Scaffolder
Scaffold a new skills directory — folder structure, metadata, a baseline validation pass — with the right conventions from day one.
Research Bundle
Run a multi-step research task as one pipeline: gather sources, extract findings, validate consistency, emit one structured bundle.
Workspace Admin
Administer a Cowork or Claude workspace — settings, access, configuration — with every change scoped and verified.