Skip to content

alirezarezvani/claude-skills / engineering/skills/feature-flags-architect

feature-flags-architect

Verified

Use before adding, rolling out or retiring a feature flag or kill switch, or when flag debt piles up. Plans the rollout with rollout_planner.py, finds stale flags with flag_debt_scanner.py and audits kill switches with kill_switch_audit.py.

FileKindSize
SKILL.mdskill md9.4 KB
assets/flag_request_template.mdmarkdown1.7 KB
references/flag_lifecycle.mdmarkdown5.7 KB
references/flag_taxonomy.mdmarkdown4.4 KB
references/provider_comparison.mdmarkdown5.0 KB
references/rollout_strategies.mdmarkdown4.9 KB
scripts/flag_debt_scanner.pyexecutablescript4.7 KB
scripts/kill_switch_audit.pyexecutablescript4.9 KB
scripts/rollout_planner.pyexecutablescript4.5 KB

assets/flag_request_template.md

View on GitHub
# Feature flag request

Fill in every section before opening a PR that adds the flag.

## Basics

- **Name:** `<kebab-case-flag-name>` (e.g., `new-checkout-flow`)
- **Owner:** `<your-handle@team>`
- **Type:** [ ] Release  [ ] Experiment  [ ] Operational  [ ] Permission
- **Created:** `<YYYY-MM-DD>`
- **Expected cleanup:** `<YYYY-MM-DD or "permanent">`

## Justification

> Why a flag and not a direct deploy?

(Examples: risky launch, A/B test, kill-switch needed, gradual rollout, compliance requirement)

## Rollout plan

> Generated by `rollout_planner.py`. Paste output below.

```
<paste output here>
```

## Kill switch

- **Trigger:** `<concrete signal that flips the flag back to 0%>`
- **Threshold:** `<numeric threshold>`
- **Method:** [ ] Manual via dashboard URL  [ ] Automated via alert webhook
- **Runbook:** `<link to on-call runbook>`

## Monitoring

- **Dashboard:** `<URL>`
- **Key metrics to watch:**
  - `<metric 1>` baseline: `<value>`, abort threshold: `<value>`
  - `<metric 2>` baseline: `<value>`, abort threshold: `<value>`

## Code locations

- **Decision point:** `<file:line>` (single point of conditional)
- **Provider used:** `<LaunchDarkly | GrowthBook | Statsig | Unleash | Flipt | DIY>`
- **SDK:** `<sdk version / config file path>`

## Tests

- [ ] Test for ON branch
- [ ] Test for OFF branch
- [ ] Kill-switch test in staging (verify flag flip works)

## Cleanup criteria

> When can this flag be removed?

(Example: at 100% rollout for ≥7 days with no incidents)

## Pre-merge checklist

- [ ] `kill_switch_audit.py` passes
- [ ] flag-doc entry added with all required fields
- [ ] PR description links to this template
- [ ] Owner has write access to the provider dashboard
- [ ] Abort criteria are concrete numbers, not vague
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall