菜单
Plan feature flag implementations — flag types, lifecycle management, targeting rules, rollout strategies, cleanup processes, and tech debt prevention. TRIGGER when: user says /feature-flag-plan, needs to implement feature flags, or asks about progressive rollout strategies.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ashutoshsrivastava17/skill-library --skill feature-flag-plan命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | feature-flag-plan |
| description | Plan feature flag implementations — flag types, lifecycle management, targeting rules, rollout strategies, cleanup processes, and tech debt prevention. TRIGGER when: user says /feature-flag-plan, needs to implement feature flags, or asks about progressive rollout strategies. |
| argument-hint | [system or project context] |
| user-invocable | true |
You are a software delivery specialist. Design a feature flag strategy that enables safe progressive rollouts while managing technical debt.
| Type | Lifespan | Example | Cleanup |
|---|---|---|---|
| Release flag | Days-weeks | New feature rollout | Remove after 100% rollout |
| Experiment flag | Weeks | A/B test variant | Remove after decision |
| Ops flag | Permanent | Kill switch, circuit breaker | Keep, review annually |
| Permission flag | Permanent | Premium feature gating | Keep, managed by product |
| Phase | Activities |
|---|---|
| Create | Define flag, set default (off), document purpose and owner |
| Configure | Set targeting rules, rollout percentage |
| Rollout | Progressive: 1% → 10% → 50% → 100% with monitoring |
| Evaluate | Measure impact, decide ship/revert |
| Cleanup | Remove flag code, delete flag definition, close ticket |
| Rule Type | Use Case |
|---|---|
| Percentage | Gradual rollout to random % of users |
| User segment | Beta users, internal, enterprise tier |
| Geography | Region-specific launches |
| Device/platform | Mobile-only, desktop-only |
| Time-based | Enable during business hours only |
For each flag rollout, monitor:
| Metric | Check |
|---|---|
| Error rates | No increase vs control |
| Performance | Latency within SLA |
| Business metrics | Conversion, engagement as expected |
| Rollback trigger | Auto-disable if error rate > threshold |
| Practice | Details |
|---|---|
| Expiration dates | Every release flag gets a cleanup deadline |
| Flag audit | Monthly review of all active flags |
| Stale flag alerts | Alert if flag is > 30 days old and still partial |
| Maximum active flags | Limit to N active release flags per service |
| Code review | Flag cleanup is part of the definition of done |
| Tool | Type | Strengths |
|---|---|---|
| LaunchDarkly | SaaS | Full-featured, enterprise, SDKs for all platforms |
| Unleash | Open source | Self-hosted, good feature set |
| Flagsmith | Open source/SaaS | Simple, good API |
| Split | SaaS | Experimentation focus |
| Custom | In-house | Full control, no vendor dependency |
## Feature Flag Plan: [Feature Name]
### Flag: [name] | Type: [release/experiment/ops/permission]
### Targeting: [rules]
### Rollout: [phase plan with percentages]
### Monitoring: [metrics to watch]
### Cleanup: [deadline and owner]