feature-flags-are-infrastructure

SKILLWorkflowcommunity
v0.0.0tedgoldsteinMITUpdated 3mo agoSource →

Treat feature flags as first-class deployment infrastructure, not an ad-hoc `if` here and there — they decouple "what's deployed" from "what's enabled", let big features land in main as inert code, support per-user/cohort/percent rollout, and give one-config rollback. Load when a feature would other

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
1Clients
1Formats
3mo agoLast update
Skill
Authortedgoldstein
Version0.0.0
LicenseMIT
CategoryWorkflow
Formatsskill.md
PromptNot published
Compatibility
Claude✓ Supported
Cursor—
Copilot—
ChatGPT—
Gemini—
About

Treat feature flags as first-class deployment infrastructure, not an ad-hoc `if` here and there — they decouple "what's deployed" from "what's enabled", let big features land in main as inert code, support per-user/cohort/percent rollout, and give one-config rollback. Load when a feature would otherwise live in a long-running branch, when a risky change needs to ship 1% → 10% → 100%, when a change

Keywords
skillclaude

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.