Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
Feature flag strategy, lifecycle, and operations. An agent skill from borghei/Claude-Skills.
Install Feature Flags Architect
$ npx skills add borghei/Claude-Skills --skill feature-flags-architect -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills feature-flags-architect --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineering/feature-flags-architect .claude/skills/feature-flags-architect && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "feature-flags-architect" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/feature-flags-architect into .claude/skills/feature-flags-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags-architect", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/engineering/feature-flags-architectType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill feature-flags-architect -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills feature-flags-architect --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/engineering/feature-flags-architect .agents/skills/feature-flags-architect && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "feature-flags-architect" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/feature-flags-architect into .agents/skills/feature-flags-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags-architect", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill feature-flags-architect -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills feature-flags-architect --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/engineering/feature-flags-architect .cursor/skills/feature-flags-architect && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "feature-flags-architect" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/feature-flags-architect into .cursor/skills/feature-flags-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags-architect", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path engineering/feature-flags-architect--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill feature-flags-architect -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills feature-flags-architect --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/engineering/feature-flags-architect .gemini/skills/feature-flags-architect && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "feature-flags-architect" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/feature-flags-architect into .gemini/skills/feature-flags-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags-architect", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills feature-flags-architectInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill feature-flags-architect -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/engineering/feature-flags-architect .github/skills/feature-flags-architect && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "feature-flags-architect" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/feature-flags-architect into .github/skills/feature-flags-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags-architect", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill feature-flags-architect -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills feature-flags-architect --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/engineering/feature-flags-architect .opencode/skills/feature-flags-architect && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "feature-flags-architect" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/feature-flags-architect into .opencode/skills/feature-flags-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags-architect", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
feature-flags-architect- GitHub stars
- 881
- Token cost
- ~2k tokens
- SKILL.md length
- 863 words
- Files
- 8 (incl. scripts, references)
- Skills in repo
- 349
- Repo updated
- First seen
- Licence
- MIT
At a glance
Feature flag strategy, lifecycle, and operations. An agent skill from borghei/Claude-Skills.
- Designing a flag taxonomy
- SKILL.md covers Core Capabilities, Flag taxonomy — the four types, When to Use and Clarify First, plus 4 more sections
- Runs Python scripts from its folder; calls python
- Planning a gradual rollout
What it does
Feature Flags Architect is an agent skill from borghei/Claude-Skills. Feature flag strategy, lifecycle, and operations. Use when designing a flag taxonomy, planning a gradual rollout, building kill switches, auditing flag debt, defining governance, running progressive delivery, or rolling back via flags.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files (for example `references/flag-debt-and-cleanup.md`, `references/flag-types-and-patterns.md` and `references/operations-governance-and-workflows.md`).
It sits in DevOps & Cloud. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Designing a flag taxonomy
- Planning a gradual rollout
- Building kill switches
- Auditing flag debt
Example prompts
- “/feature-flags-architect”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Feature Flags Architect loads about 2k tokens when it runs, and up to ~18k if it reads all its reference files. Until then it costs about 65 tokens; SKILL.md has 863 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 863 words, ~1,956 tokens.
Download SKILL.mdSave it as
.claude/skills/feature-flags-architect/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- feature-flags-architect
- description
- Feature flag strategy, lifecycle, and operations. Use when designing a flag taxonomy, planning a gradual rollout, building kill switches, auditing flag debt, defining governance, running progressive delivery, or rolling back via flags.
- license
- MIT + Commons Clause
- metadata.version
- 1.1.0
- metadata.author
- borghei
- metadata.category
- engineering
- metadata.domain
- engineering
- metadata.updated
- 2026-06-17
- metadata.tags
- feature-flags, progressive-delivery, rollouts, kill-switches, release-engineering, experimentation, flag-governance
Feature Flags Architect
End-to-end feature flag design, rollout, and lifecycle management. Covers flag taxonomy (release vs ops vs experiment vs permission), gradual rollout patterns with blast-radius math, kill-switch runbooks, governance (who can flip what), and the flag-debt cleanup loop that keeps a codebase from drowning in stale flags.
This skill is provider-agnostic: the patterns work whether you run LaunchDarkly, Statsig, Unleash, Flagsmith, ConfigCat, GrowthBook, OpenFeature, or a homegrown system backed by Redis/DynamoDB/Postgres.
Core Capabilities
- Flag taxonomy — classify every flag as one of four types (release, ops, experiment, permission); the type sets lifetime, who flips it, and auto-expiry.
- Rollout ramps — dogfood → canary → 100% schedules with per-step blast-radius math and ramp templates by change type.
- Kill switches — ops-flag pattern with fail-open/closed decisions, runbooks, and alerting for risky dependencies or code paths.
- Governance — role-based who-can-flip-what matrix plus audit-log/retention requirements, mappable onto any flag system.
- Flag debt cleanup — quarterly inventory → classify → decide → execute → measure loop to keep flag count flat or shrinking.
- End-to-end workflows — add a release flag, build a kill switch, audit flag debt, flag-based rollback after a bad release.
Flag taxonomy — the four types
Every flag belongs to exactly one of these four types. The type determines the lifecycle, who can flip it, and whether it should auto-expire. Mixing types in one flag is a root cause of flag debt.
| Type | Purpose | Lifetime | Who flips | Auto-expire? |
|---|---|---|---|---|
| Release | Decouple deploy from release. Ship code dark, ramp to users. | Days to weeks | Engineer who owns the feature | Yes — remove after 100% rollout + 1 release |
| Ops | Kill switches, circuit breakers, throttles. Turn off risky behavior fast. | Permanent or long-lived | Oncall / SRE / platform team | No — but review quarterly |
| Experiment | A/B test, multi-arm bandit, hold-out group. Measure causal impact. | Weeks to months (test duration) | Product / data / growth | Yes — remove after winner is shipped |
| Permission | Entitle users to features based on plan, role, beta-list. | Permanent | Product / billing | No — but consolidate into entitlement system |
Decision rule when adding a flag: name the type. If you can't, the flag shouldn't exist yet — clarify intent first.
When to Use
- Designing a flag system from scratch — start with the flag taxonomy.
- Planning a risky release (DB migration, payment-provider swap, framework upgrade) — use the rollout ramp + kill switch.
- Auditing a codebase with hundreds of growing flags — use flag debt cleanup +
scripts/flag_audit.py. - Setting up an A/B test or hold-out — covers the flag side; pair with
engineering/experiment-designfor statistics. - Building a kill switch for a third-party dependency outage — use the kill switch runbook generator.
- Defining who in the org can flip production flags — use the governance matrix.
- Building entitlements / paid-tier gating — use this for flag mechanics;
business-growth/paywall-upgrade-crofor the UX.
Clarify First
Before designing or operating flags, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- Flag type — release, ops, experiment, or permission (sets the lifecycle, who can flip it, and auto-expiry — the root decision)
- Task — design a taxonomy, simulate a rollout ramp, generate a kill-switch runbook, or audit flag debt (selects
flag_audit.pyvsrollout_simulator.pyvskill_switch_runbook.py) - Blast radius / population — user count and ramp profile, or the dependency a kill switch guards (drives
--users/--profileand the runbook content)
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Show full SKILL.md (317 more words)Show less
Tools
| Tool | Purpose | Command |
|---|---|---|
flag_audit.py | Scan a codebase for flag references, age, classification, and recommended action (optionally cross-reference a control-plane export) | python scripts/flag_audit.py --path . --format markdown |
rollout_simulator.py | Model a rollout: per-step blast radius, time-to-detect, recommended schedule | python scripts/rollout_simulator.py --users 500000 --profile standard |
kill_switch_runbook.py | Generate a kill-switch runbook (default state, flip procedure, validation, escalation) | python scripts/kill_switch_runbook.py --flag ops.recs.kill_switch --feature Recommendations --dependency recs-svc |
All scripts: standard library only, argparse CLI, JSON + human-readable output. Run --help for full usage.
References
Load the reference that matches the task — keep this file lean and pull detail on demand:
- references/flag-types-and-patterns.md — the four flag types in depth, code patterns per type, evaluation-context schema, naming conventions, server-vs-client trade-offs, and storage models. Read when designing a flag system or writing the gating code.
- references/operations-governance-and-workflows.md — the standard ramp table, blast-radius math, kill-switch design, the governance matrix + audit-log requirements, the flag-debt cleanup loop, all four end-to-end workflows, the anti-patterns list, and the tooling input/output reference. Read when running a rollout, defining governance, or executing a workflow.
- references/rollout-and-kill-switch-playbook.md — rollout decision tree, ramp templates by change type, cohort/segment selection, kill-switch design, and monitoring/alerting hookup. Read when planning a specific ramp or wiring kill-switch alerting.
- references/flag-debt-and-cleanup.md — what flag debt costs, the cleanup cadence, dead-code detection, safe removal procedures, PR templates, and governance for flag count. Read when paying down stale flags.
Scope & Limitations
This skill covers: flag taxonomy and lifecycle, rollout ramps with blast-radius math, kill-switch design and runbooks, governance/audit requirements, and flag-debt cleanup — provider-agnostic across LaunchDarkly, Statsig, Unleash, Flagsmith, ConfigCat, GrowthBook, OpenFeature, and homegrown systems.
This skill does NOT cover: the statistical design of A/B tests (pair with product-team/experiment-design), the paywall/upgrade UX for entitlements (business-growth/paywall-upgrade-cro), or the metric instrumentation needed to make ramp decisions (engineering/observability-designer).
Related skills
engineering/observability-designer— wire the metrics needed to make ramp decisionsengineering/incident-commander— flag-based rollback during incidentsengineering/chaos-engineering— verify kill switches actually work under fault injectionproduct-team/experiment-design(if available) — statistical design of A/B tests behind flags
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 7 other files (scripts, references) in engineering/feature-flags-architect of borghei/Claude-Skills.
- SKILL.md
- references/flag-debt-and-cleanup.md
- references/flag-types-and-patterns.md
- references/operations-governance-and-workflows.md
- references/rollout-and-kill-switch-playbook.md
- scripts/flag_audit.py
- scripts/kill_switch_runbook.py
- scripts/rollout_simulator.py
Open the folder on GitHubat commit 4a698e8
Compare with similar skills
Feature Flags Architect next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Feature Flags Architect this skillborghei/Claude-Skills | 881 | — | ~2k | Automated safety check: Pass | MIT | |
| Monitor CInrwl/nx | 29k | 6 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Terraform and OpenTofu Guideagentscope-ai/QwenPaw | 35k | 6 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 9 repos | ~4.3k | Automated safety check: Pass | None | |
| Openclaw Live Updateropenclaw/openclaw | 392k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Analyze GitHub Action Logswithastro/astro | 63k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence |
Similar skills
Terraform and OpenTofu Guide
agentscope-ai/QwenPaw
Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.
- Official
Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
Openclaw Live Updater
openclaw/openclaw
Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.
- Official
Analyze GitHub Action Logs
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
KubeSphere Multi-Tenant Management
kubesphere/kubesphere
Creates and queries KubeSphere users, workspaces and projects and assigns built-in roles, defaulting to least privilege and never deleting anything.
More from borghei/Claude-Skills
All 349 skills in this repoAgents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Brainstorm Okrs
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Related
Categories
Questions about Feature Flags Architect
What does Feature Flags Architect do?
Feature flag strategy, lifecycle, and operations. An agent skill from borghei/Claude-Skills. Feature Flags Architect is an agent skill from borghei/Claude-Skills. Feature flag strategy, lifecycle, and operations.
When should I use Feature Flags Architect?
Feature Flags Architect fits situations like: designing a flag taxonomy; planning a gradual rollout; building kill switches; auditing flag debt.
How do I install Feature Flags Architect in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill feature-flags-architect -a claude-code`. Or copy the skill folder (engineering/feature-flags-architect in borghei/Claude-Skills) into .claude/skills/feature-flags-architect in your project. Claude Code loads it when a task matches its description.
How do I install Feature Flags Architect in Codex?
Run `npx skills add borghei/Claude-Skills --skill feature-flags-architect -a codex`. Or copy the skill folder (engineering/feature-flags-architect in borghei/Claude-Skills) into .agents/skills/feature-flags-architect in your project. Codex loads it when a task matches its description.
Can I use Feature Flags Architect in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill feature-flags-architect -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/feature-flags-architect, .gemini/skills/feature-flags-architect, .github/skills/feature-flags-architect and .opencode/skills/feature-flags-architect in your project.
What does Feature Flags Architect need to run?
Going by SKILL.md and its folder, Feature Flags Architect needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Feature Flags Architect access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Feature Flags Architect safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Feature Flags Architect use?
Feature Flags Architect is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Feature Flags Architect use?
About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16k tokens, read only when the agent opens those files.
What are the alternatives to Feature Flags Architect?
Skills that share tags, products or a category with Feature Flags Architect: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 35k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Openclaw Live Updater (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Feature Flags Architect?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.