add-feature-flag

Scaffold feature flags across MCP and AI Command Center repositories.

Updated May 18, 2021
One-click install
npx skills add https://github.com/jwbaldwin/dotfiles --skill add-feature-flag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-feature-flag
Source: https://github.com/jwbaldwin/dotfiles/tree/main/.config/opencode/skills/add-feature-flag
Command: npx skills add https://github.com/jwbaldwin/dotfiles --skill add-feature-flag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill scaffolds the foundational plumbing for a new feature flag across MCP and AI Command Center, updating schemas, build configs, getters, and dashboards to enable controlled, staged feature delivery.

Core Features & Use Cases

  • Repository detection: Identify whether we are in MCP or AI Command Center to apply the correct scaffolding.
  • Flag naming: Derive or solicit a feature flag name and align with repository conventions.
  • File updates: Add and wire required files across the two repositories (env schema, turbo globalEnv, getter/export, and local dev docs).
  • Next steps: Provide precise follow-ups to create the flag in dashboards and to wire usage points.
  • Use Case: Quickly bootstrap a new feature flag to enable controlled experimentation without manual, multi-repo edits.

Quick Start

Say "feature flag it" or "add the feature flag" and specify a name if prompted. The skill will scaffold the necessary files across MCP and AI Command Center, then guide you through dashboard creation and implementation in code.

Frequently Asked Questions about add-feature-flag

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a feature flag across multiple repositories?

Feature flag scaffolding automates setup across MCP and AI Command Center by detecting your active repo, deriving the flag name, and wiring backend integration—Split.io for MCP with env var overrides, Harness with Edge Config for AI Command Center—plus generating env schemas, turbo configs, and getter functions.

What files does feature flag scaffolding generate?

Scaffolding creates an env-config schema entry, turbo.json globalEnv entry, a getter function, an export, and an environment example file, with usage steps for server-side and client-side integration across both repositories.

Can I use feature flags with Split.io and Harness together?

Yes. This Skill scaffolds feature flag plumbing to work with Split.io in MCP using environment variable overrides and Harness with Edge Config in AI Command Center, enabling centralized flag management across both platforms.

Do I need to manually edit multiple files to set up a feature flag?

No. The Skill automates multi-repo edits by detecting your repository, deriving the flag name from Jira or user input, and wiring all required configuration files—eliminating manual schema, build config, and getter updates.

What's the fastest way to bootstrap a new feature flag?

Say 'feature flag it' and provide a name. The Skill scaffolds all foundational plumbing, generates artifacts for both repositories, and provides precise follow-ups to create the flag in dashboards and wire usage points in code.

How do feature flags enable controlled feature delivery?

Feature flags replace ad hoc toggles with centralized, overridable flags via Split.io or Harness, allowing staged rollout, A/B testing, and rapid rollback without redeployment.