skills.rest
f4rkh4d
f4rkh4dCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

forge-feature-flags

Enforce lifecycle, naming, rollout, and removal rules for feature flags.

Updated Aug 23, 2026
Search Tags:#release management#technical debt#testing strategy#feature flags#server-side evaluation#rollout targeting
One-click install
npx skills add https://github.com/f4rkh4d/forge-skill --skill forge-feature-flags
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: forge-feature-flags
Source: https://github.com/f4rkh4d/forge-skill/tree/main/skills/backend/forge-feature-flags
Command: npx skills add https://github.com/f4rkh4d/forge-skill --skill forge-feature-flags

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about forge-feature-flags

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent feature flags from becoming permanent technical debt?▼

Preventing feature flags from becoming technical debt requires enforcing a disciplined lifecycle with safe defaults, assigning an owner, and scheduling a removal date for every flag before it ships to production.

What is the best way to implement feature flag rollout targeting safely?▼

The best way to implement safe feature flag rollout targeting is to enforce default-off behavior in production and use gradual percentage-based targeting across users, tenants, or cohorts to control exposure and ensure reliable rollback.

Should I use environment variables or a flag service for server-side feature flag evaluation?▼

Use a dedicated flag service instead of environment variables for server-side evaluation. A flag service enables request-scoped snapshotting for performance consistency and supports dynamic rollout targeting across users and tenants.

How do I test feature flags to ensure both on and off branches work correctly?▼

Testing feature flags requires mandating tests that cover both the on and off branches. This ensures the default-off path stays healthy and the active rollout path is verified, maintaining reliability during server-side evaluation.

When should I use kill-switch ops flags versus authorization permissions for incident response?▼

You should use kill-switch ops flags for incident response to quickly disable functionality, while distinguishing them from authorization permissions. Ops flags are temporary release toggles, whereas permissions govern permanent access control rules.

Related Skills

Explore More Software Engineering Skills→
jnlanahanjnlanahan

feature-flag

Create default-OFF feature flags with guard checks and rollout plans.

Community
Intermediate
anyprotoanyproto
509

Feature Toggle Developer

Automate feature toggle removal and cleanup detection in Swift codebases.

Official
Intermediate
luokai25luokai25

test-automator

Develop test automation frameworks, scripts, and CI/CD pipeline integrations.

Community
Advanced
hopeoverturehopeoverture
6

feature-flag-manager

Manage feature flags for progressive rollouts and A/B testing in web applications.

Community
Advanced