FF
Feature Flag Guide
🔵 Stable🕐 updated 2026-06-08
🔷 SkillSpec L3
pm-engineering
Write a feature flag management guide and lifecycle playbook for a service or team — covering flag taxonomy, creation checklist, rollout strategy, monitoring requirements, cleanup policy, and governance. Use when asked to document feature flag practices, create a flag rollout plan, write a feature flag policy, or guide a team on flag lifecycle management. Produces a flag lifecycle playbook, taxonomy reference, per-flag creation template, rollout decision tree, and cleanup checklist.
What to give it
▸Service or team name — scope of the guide
▸Feature flag platform — LaunchDarkly, Split, Unleash, Flagsmith, Flipt, or a custom/in-house solution
▸Flag being documented — if writing a per-flag guide) or "general guide" (if writing team-wide policy
▸Rollout constraints — any compliance, data privacy, or contractual constraints on who can see a feature (e.g. HIPAA, EU-only, enterprise customers only)
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓Every flag has an owner named in its description — no orphan flags
✓Release and Experiment flags have a cleanup date set — not open-ended
✓Monitoring is configured for every flag currently between 1–99% rollout
✓The emergency kill-switch procedure has been tested — on-call engineers have bookmarked the platform URL and know the steps
✓Stale flag detection runs automatically and results are reviewed weekly
✓Code review checklist includes: "Does this PR introduce a flag? If yes, is the creation checklist complete?"
✓At least one person other than the flag owner knows how to disable any given flag in an emergency
⚠️ What it refuses to do
Do not create release flags without a cleanup date — flags without expiry dates become permanent technical debt that accumulates silently until the codebase is unmaintainable
Do not skip monitoring setup for flags between 1–99% rollout — a partially-rolled-out flag without metric comparison is a risk without a sensor
Do not nest flags inside other flags — compound flag logic makes cleanup nearly impossible and creates untestable code paths
Do not allow flag owners to leave the team without reassigning ownership — orphan flags with no owner never get cleaned up
Do not use feature flags as a permanent configuration system — flags that have been at 100% or 0% for more than 30 days must be cleaned up; using flags as permanent config couples business logic to a feature flag platform
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcpStart with
Related skills
🔌 Embed this skill
Drop this on your blog, docs, or site — it renders a "Run this skill" card:
<div data-pm-skill="feature-flag-guide"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>💬 Discussion
Feature Flag Guide is one of 1078 open-source professional AI agent skills — all SkillSpec L3.
Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog