featureopslisted
Install: claude install-skill Unleash/unleash-claude-skills
# Unleash FeatureOps
[FeatureOps](https://featureops.io) rests on one default: every change is reversible. If you can't turn it off, don't turn it on. This skill applies that default through the [Unleash MCP server](https://github.com/Unleash/unleash-mcp): it decides when a change needs a flag, how to wrap it, how to roll it out and when to take the flag out again.
## Setup check
The skill needs the Unleash MCP server. A plugin install registers it from the bundled `.mcp.json`; set these in the shell that starts your agent:
```bash
export UNLEASH_BASE_URL=https://your-instance.getunleash.io
export UNLEASH_PAT=your-personal-access-token
```
On any other install, connect the server yourself (see <https://github.com/Unleash/unleash-claude-skills>). If the Unleash tools are missing, tell the user to finish setup and stop rather than guessing flag state. Deciding, wrapping and removing work on the code alone and still apply.
## Active policy
Every tunable value (naming, flag types and lifetimes, when a flag is required, rollout milestones and holds, halt thresholds, staleness windows, high-risk domains) comes from the **active policy**. The reference files say how to apply the values and never restate them.
**Precedence, highest first: project override, user override, shipped defaults.** For each value, use the highest layer that sets it. The project override and the defaults are inlined below. If `~/.unleash/featureops.md` exists, read it and slot it between them.
**Proj