scriptoriumadmin/claude-skills
1
0
Fork 0
mirror of https://github.com/alirezarezvani/claude-skills.git synced 2026-09-05 08:05:57 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
claude-skills/engineering/feature-flags-architect
History
Exact
Claude 0f88555485
chore(versioning,docs): normalize stale versions to 2.9.0 + refresh counts 
Version normalization (scope: only plugins/skills older than 2.7.0):
- Bumped 52 plugin.json + 21 SKILL.md `version` fields from pre-2.7.0
  values (1.0.0 / 2.0.x / 2.2.x / 2.3.x / 2.4.x / 2.5.x) to 2.9.0.
  Left 2.7.0+ packages untouched. Tool mirrors (.codex/.gemini/.vibe/
  .hermes) excluded. All manifests still pass check_plugin_json --all.

Doc count refresh (recomputed raw figures: 338 skills, 16 domains,
62 plugins, 533 Python tools, 676 references):
- marketplace.json: both descriptions + metadata.version -> 2.9.0.
- Root README: headline, badges (Skills 338, Agents 51+, Commands 87+),
  intro counts, convert section (338 skills / 9 tools), and the full
  domain table rebuilt to 16 domains summing to 338 (adds research-ops,
  business-operations, commercial, compliance-os; corrects product 17,
  marketing 46, c-level 66, ra-qm 18, finance 4, engineering 51/78).
- Fixed stale per-skill README `Version:` lines left inconsistent by the
  bump (andreessen, c-level-agents, product-team, senior-qa).
- Fixed stale domain README footers (product-team 17/17, c-level 66/66,
  project-management 9/9).
- CLAUDE.md scope line, structure tree, highlight, and footer synced to
  the raw figures.

https://claude.ai/code/session_01PUNmQVE4WYvcrzpq2anC3D
2026-05-27 05:22:59 +00:00
..
.claude-plugin chore(versioning,docs): normalize stale versions to 2.9.0 + refresh counts 2026-05-27 05:22:59 +00:00
skills/feature-flags-architect chore(versioning,docs): normalize stale versions to 2.9.0 + refresh counts 2026-05-27 05:22:59 +00:00
README.md feat(skills): ship feature-flags-architect (Phase 1 pilot — dual-publish) 2026-05-09 06:10:43 +00:00

README.md

Feature Flags Architect

End-to-end discipline for feature flags: classify, ship, ramp, retire.

Most teams treat flags as throwaway if-statements. This skill treats them as a controlled lifecycle with measurable debt — and ships the tools to enforce it.

What's inside

  • 3 stdlib Python tools — flag debt scanner, rollout planner, kill-switch auditor
  • 4 reference docs — taxonomy, provider comparison, rollout strategies, lifecycle
  • /flag-cleanup slash command — runs the full quarterly cleanup workflow
  • Asset template — feature flag request form

Install

Claude Code

# Via Claude Code marketplace
/plugin install feature-flags-architect

# Or clone the repo
git clone https://github.com/alirezarezvani/claude-skills.git
cd claude-skills/engineering/feature-flags-architect

Other tools (Codex CLI, Cursor, Antigravity, OpenCode, Gemini CLI)

The skill ships with a context: fork SKILL.md, so it loads via the standard skill mechanism each tool supports. See cross-tool compatibility in the SKILL.md frontmatter.

Quick start

SKILL=engineering/feature-flags-architect/skills/feature-flags-architect

# Audit your repo for stale flags
python "$SKILL/scripts/flag_debt_scanner.py" --repo . --max-age-days 90

# Plan a phased rollout
python "$SKILL/scripts/rollout_planner.py" --population 100000 --target-percent 100 --duration-days 14 --strategy ring

# Verify every flag has a kill switch
python "$SKILL/scripts/kill_switch_audit.py" --repo . --flag-doc docs/feature-flags.md

When to use

  • Adding a new flag and need a rollout plan
  • Auditing a codebase for orphaned or stale flags
  • Choosing a flag provider (LaunchDarkly vs GrowthBook vs Statsig vs Unleash vs Flipt vs DIY)
  • Designing a kill-switch path for a risky launch
  • Cleaning up flag debt before a release freeze

Key principles

  1. Flags are a lifecycle, not an if-statement: request → design → ship → ramp → cleanup → archive
  2. 4 flag types with different lifespans: Release / Experiment / Operational / Permission
  3. Every flag has a documented kill switch — owner, type, trigger, dashboard
  4. Rollout strategy by risk, not preference (ring for risky, linear for medium, log for low)
  5. Quarterly cleanup is non-negotiable — debt compounds

Skill structure

feature-flags-architect/
├── README.md                              # this file
├── .claude-plugin/plugin.json             # 8-field plugin manifest
└── skills/feature-flags-architect/
    ├── SKILL.md                           # main skill spec
    ├── scripts/
    │   ├── flag_debt_scanner.py           # find stale flags
    │   ├── rollout_planner.py             # generate phased schedule
    │   └── kill_switch_audit.py           # verify documentation
    ├── references/
    │   ├── flag_taxonomy.md               # 4 types decision tree
    │   ├── provider_comparison.md         # LD/GB/Statsig/Unleash/Flipt/DIY
    │   ├── rollout_strategies.md          # ring/linear/log/cohort
    │   └── flag_lifecycle.md              # 6-phase lifecycle
    └── assets/
        └── flag_request_template.md       # PR template

Verifiable success

A team using this skill should achieve:

  • 100% of new flags pass kill_switch_audit.py at merge time
  • flag_debt_scanner.py --max-age-days 90 returns ≤5 stale flags repo-wide
  • Every flag has a documented owner, type, kill switch, and dashboard
  • Mean time to retire a Release flag: <60 days from 100% rollout

License

MIT — see repo root LICENSE.