Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kdlbs/runtime-feature-flags
Add, roll out, promote, graduate, or remove Kandev runtime feature flags and release toggles across the backend and frontend.
Passed 16 of 19 test cases with the skill, and 6 of 19 without it.
and 14 more in the full report
12 fixed7 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/20/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
What exact `go test` command should be executed from `apps/backend` to verify the backend runtime flags, common config, and profiles packages after changing a flag?
| Checked | Without skill | With skill |
|---|---|---|
| runs go test ./internal/runtimeflags ./internal/common/config ./internal/profiles from apps/backend | Missed | Passed |
The instructions your model reads when the skill loads.
Use this checklist for temporary release toggles and risky features. It is
self-contained: do not depend on the agent having read an ADR or public docs.
Read apps/backend/AGENTS.md and apps/web/AGENTS.md when the change touches
those subtrees.
features.<camelCaseKey>,
KANDEV_FEATURES_<UPPER_SNAKE_CASE>, a Go FeaturesConfig field, its JSON tag,
and the matching frontend key. Never add a parallel flag map or switch.retiredRuntimeFlagIdentities
and its collision/completeness test exist; if they do not, add that
runtimeflags infrastructure before removing a live flag.Update these layers in the same change:
KANDEV_FEATURES_<NAME> under features: in the
root profiles.yaml; use prod: "false", dev: "false", and e2e: "false"
for a release toggle unless the task explicitly documents a test-only
exception.bool field with explicit mapstructure and
json tags to apps/backend/internal/common/config/config.go.apps/backend/internal/runtimeflags/registry.go: key, env var, kind, label,
description, stability, risk, and restart/mutability metadata. The registry
definition is metadata-only; add the key/env constants and update
OptionsFromConfig, ValuesFromConfig, and ApplyStatesToConfig in
runtimeflags/config.go for typed config wiring.test cases passed, vs 6 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.