Deployment

Feature Flags & Safe Rollouts

Designs feature flags and controlled rollouts: percentage exposure, kill switches, safe defaults, expiry.

What it does

Designs feature flags and controlled rollouts: percentage exposure, kill switches, safe defaults, expiry.

When to use it

Use for release toggles, cohort exposure, migrations, or cleaning up flags nobody remembers the purpose of.

Problems it prevents

Stops a rollout with no kill switch, and flags that outlive their purpose and quietly rot in the codebase.

Typical workflow

  1. Define the flag's contract and owner
  2. Engineer safe evaluation and defaults
  3. Roll out with a real recovery path
  4. Set an expiry and remove it on schedule

Example output

A rollout with a working kill switch and an expiry date, not a flag left permanently wrapping the old and new path.

What's included

  1. 01
    The complete prompt

    The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

  2. 02
    Install walkthrough

    Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

  3. 03
    Use notes

    How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Installation

Save the manual as SKILL.md in ~/.claude/skills/feature-flags-safe-rollouts/ to use it on every project, or in .claude/skills/feature-flags-safe-rollouts/ to scope it to one repository. Then invoke it directly:

/feature-flags-safe-rollouts

Read the official Claude Code skills guide

Works well with