SkillVaultskills Browse all 500 skills

Architecture · Version 1.1.0 · Reviewed 2026-08-02

Feature Flag Lifecycle Manager

Make a defensible decision about flag taxonomy design and safe default selection with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Designs flag taxonomy, evaluation safety, default behavior, and removal discipline so flags do not become permanent hidden branches.

₹149 one-time

Get this skill archive

What this skill helps you do

  • Flag taxonomy design
  • Safe default selection
  • Flag debt removal

How Feature Flag Lifecycle Manager works

You provide

Flag inventory, evaluation data, and owners

It inspects

Flag type, staleness, and default-path safety

It decides

Classification with a removal order and owners

You verify

Stale release flags removed and evaluation drops to zero

What it checks first

Feature Flag Lifecycle Manager designs flag taxonomy, evaluation safety, default behavior, and removal discipline so flags do not become permanent hidden branches. Use it when the work involves Flag taxonomy design, Safe default selection, Flag debt removal.

  1. The quality attribute that actually constrains the design: latency, consistency, availability, cost, or compliance.
  2. The critical path and the number of network hops on it.
  3. Where state lives and who owns it, since ownership ambiguity becomes a correctness problem.
  4. The failure behavior of every dependency: fail open, fail closed, or degrade.

Failure modes it recognizes

  • Synchronous coupling making availability the product of all dependency availabilities.
  • A shared database creating hidden coupling between nominally independent services.
  • A component with no clear owner, so its failure has no defined response.
  • Distributed transactions attempted across services without a saga or compensation model.

Answers it will reject

  • Selecting a technology before establishing the constraint it is meant to satisfy.
  • Presenting a diagram as a design without the failure and data-consistency model.
  • Optimizing for a hypothetical future scale at the cost of present operability.

Decision rules it applies

  • Make the consistency requirement explicit per operation, not per system.
  • Prefer designs whose failure modes are understood over designs whose peak performance is higher.
  • Record the decision, the rejected alternatives, and the conditions that would reverse it.

Evidence it asks for

  • Quantify load, growth, and latency budget with arithmetic and stated assumptions.
  • Define the rollout stages and the signal that gates each one.
  • Name the reversal path for the decision.

The method inside

  1. Establish what is actually true about flag taxonomy design from the supplied evidence, and mark what is missing.
  2. Identify the mechanism behind safe default selection rather than restating the symptom.
  3. Choose the smallest defensible change for flag debt removal, weighing impact, confidence, effort, and reversibility.
  4. Record consequences, rollback, and open questions

Deliverables

  • Flag taxonomy design assessment
  • Safe default selection decision and action plan
  • Flag debt removal verification checklist

Evidence requirements

  • Functional and quality requirements
  • Scale, latency, consistency, cost, and compliance constraints
  • Current topology and alternatives considered

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

We have 200 feature flags and nobody knows which are safe to remove.

Expected output

Removal is blocked because the flags have no declared type. A release flag should live days, an operational kill switch lives forever, and a permission flag is not a flag at all. Classify first, since the removal policy differs by type, then attack the release flags with stale evaluation data...

Boundaries and compatibility

Ideal for

  • Flag taxonomy design: produce a decision or artifact grounded in supplied evidence.
  • Safe default selection: produce a decision or artifact grounded in supplied evidence.
  • Flag debt removal: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Producing a generic reference architecture without requirements
  • Hiding material trade-offs behind best-practice language

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.