create-feature-flag
Installation
SKILL.md
Create Feature Flag
Create a new Harness FME feature flag and optionally its per-environment definitions with safe defaults, following the project's existing conventions. Related: update-flag-targeting (ramp), manage-experiments (A/B test).
Tools
Works through the Harness MCP server or the Harness CLI; names are from tool-map.md.
| Operation | MCP | CLI |
|---|---|---|
| List flags | harness_list · fme_feature_flag · size: 50 · compact: false |
harness list feature_flag --json --limit 50 |
| Get flag | harness_get · fme_feature_flag · params.feature_flag_name |
harness get feature_flag <name> --json |
| List environments | harness_list · fme_environment · compact: false |
harness list fme_environment --json |
| List traffic types | harness_list · fme_traffic_type · compact: false |
harness list traffic_type --json |
| Get definition | harness_get · fme_feature_flag_definition · params: { feature_flag_name, environment_id } |
harness get feature_flag:definition <flag> --env <env-id> --json |
| Create flag | harness_create · fme_feature_flag · body: { name, trafficType, description?, tags?, owners? } |
harness create feature_flag <name> --traffic-type <type> --set description="..." plus --add tags.<name> per tag, or -f flag.json with the full approved body (CLI's tags/owners are collection fields — --set tags=[...] isn't valid syntax) |
| Create definition | harness_create · fme_feature_flag_definition · params: { feature_flag_name, environment_id } · body: { treatments, defaultTreatment, defaultRule, comment? } |
harness create feature_flag:definition <flag> --env <env-id> -f def.json |