forge-feature-flags

Community

Ship flags that die on schedule.

Authorf4rkh4d
Version1.0.0
Installs0

System Documentation

What problem does it solve?

This Skill prevents feature flags from turning into permanent technical debt by enforcing a disciplined, time-bounded lifecycle with safe defaults and reliable rollback behavior.

Core Features & Use Cases

  • Feature-flag lifecycle rules: Require an owner and a scheduled removal date so flags don’t linger.
  • Safe rollout behavior: Enforce default-off in production, positive naming, and gradual percentage-based targeting.
  • Correct implementation patterns: Promote flag services over env vars and require request-scoped snapshotting for performance and consistency.
  • Reliability via testing: Mandate tests for both branches so the “off” path stays healthy and the “on” path is verified.
  • Operational correctness: Encourage kill-switch ops flags for incident response while distinguishing flags from authorization/permissions.

Quick Start

Use the forge-feature-flags skill when you need to introduce a new rollout-controlled feature, so you can add the flag, implement both branches, and plan its deletion date up front.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: forge-feature-flags
Download link: https://github.com/f4rkh4d/forge-skill/archive/main.zip#forge-feature-flags

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.