feature-flags-architect

Manage feature flag workflows from planning through deployment and cleanup.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ThalesAndrades/forumfoup2026 --skill feature-flags-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-flags-architect
Source: https://github.com/ThalesAndrades/forumfoup2026/tree/main/.claude/skills/feature-flags-architect
Command: npx skills add https://github.com/ThalesAndrades/forumfoup2026 --skill feature-flags-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It enables teams to classify, ship, and retire feature flags systematically, preventing debt caused by unmanaged flags.

Core Features & Use Cases

  • Flag Lifecycle Management: Guides through requesting, designing, deploying, ramping up, cleaning, and archiving flags.
  • Risk Mitigation: Implements phased rollouts, kill switches, and cleanup automation to reduce incidents.
  • Use Case: A product team launches a new feature toggle with a phased rollout plan, ensuring safety and traceability from request to removal.

Quick Start

Use the feature flags skill to plan a gradual rollout by defining phases and monitoring metrics at each stage.

Frequently Asked Questions about feature-flags-architect

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

FAQPage Schema
What is feature flag lifecycle management and why is it important for release management?

Feature flag lifecycle management systematically governs toggles from request to removal. It prevents technical debt and unmanaged flags by ensuring releases are controlled, documented, and reversible.

How do I plan a progressive delivery rollout for a new feature toggle?

Plan a progressive delivery rollout by defining phased rollout stages, implementing kill switches, and monitoring metrics at each ramp-up phase to ensure safe, controlled feature releases.

How do you clean up and retire feature flags to prevent technical debt?

Clean up and retire feature flags using cleanup automation during the archiving phase. This removes unused toggles systematically, preventing debt caused by unmanaged flags after deployment.

What is the best way to implement kill switches and risk mitigation for feature releases?

The best way to implement risk mitigation is combining phased rollouts with kill switches. This approach reduces incidents by allowing immediate feature reversal during progressive delivery.

Can I use feature flag workflows for software engineering teams without external dependencies?

Yes, you can implement feature flag workflows without external dependencies. The process provides reference assets to guide planning, deployment, and cleanup for engineering teams implementing progressive delivery.

When should I archive feature flags instead of keeping them active in the codebase?

Archive feature flags after the rollout completes and the feature is stable. Archiving removes toggle debt, keeping the codebase clean and preventing unmanaged flags from accumulating.