AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

feature-flags-architect

Use before adding, rolling out or retiring a feature flag or kill switch, or when flag debt piles up. Plans the rollout with rollout_planner.py, finds stale flags with flag_debt_scanner.py and audits kill switches with kill_switch_audit.py.

Original source
alirezarezvani
License
MIT
Pinned revision
e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read alirezarezvani--feature-flags-architect at revision e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 6

assets/flag_request_template.md

Feature flag request

Fill in every section before opening a PR that adds the flag.

Basics

  • Name: <kebab-case-flag-name> (e.g., new-checkout-flow)
  • Owner: <your-handle@team>
  • Type: [ ] Release [ ] Experiment [ ] Operational [ ] Permission
  • Created: <YYYY-MM-DD>
  • Expected cleanup: <YYYY-MM-DD or "permanent">

Justification

Why a flag and not a direct deploy?

(Examples: risky launch, A/B test, kill-switch needed, gradual rollout, compliance requirement)

Rollout plan

Generated by rollout_planner.py. Paste output below.

<paste output here>

Kill switch

  • Trigger: <concrete signal that flips the flag back to 0%>
  • Threshold: <numeric threshold>
  • Method: [ ] Manual via dashboard URL [ ] Automated via alert webhook
  • Runbook: <link to on-call runbook>

Monitoring

  • Dashboard: <URL>
  • Key metrics to watch:
    • <metric 1> baseline: <value>, abort threshold: <value>
    • <metric 2> baseline: <value>, abort threshold: <value>

Code locations

  • Decision point: <file:line> (single point of conditional)
  • Provider used: <LaunchDarkly | GrowthBook | Statsig | Unleash | Flipt | DIY>
  • SDK: <sdk version / config file path>

Tests

  • [ ] Test for ON branch
  • [ ] Test for OFF branch
  • [ ] Kill-switch test in staging (verify flag flip works)

Cleanup criteria

When can this flag be removed?

(Example: at 100% rollout for ≥7 days with no incidents)

Pre-merge checklist

  • [ ] kill_switch_audit.py passes
  • [ ] flag-doc entry added with all required fields
  • [ ] PR description links to this template
  • [ ] Owner has write access to the provider dashboard
  • [ ] Abort criteria are concrete numbers, not vague