Menu
Feature flags and toggles management. Trigger when the user wants to implement feature flagging, A/B testing, or progressive deployment.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Multi-agent team orchestration with native Agent Teams. Trigger when the user wants to launch a team of agents, coordinate parallel work with inter-agent communication, or use swarm mode.
Perform a thorough code review. Use when the user requests a review, wants to verify code quality, or before merging a PR.
Context transfer between AI sessions. Trigger when the user wants to save the context, resume a task, or hand off the work to another session.
API mock configuration for tests. Trigger when the user wants to mock APIs, use MSW, or test without a backend.
Debug and resolve problems. Use when the user has a bug, an error, an unexpected behavior, or wants to understand why something is not working.
TDD development with Red-Green-Refactor cycle. Use to implement a feature by writing tests BEFORE the code. Trigger automatically when the user asks for TDD, wants to write tests first, mentions "test first", or asks to implement, add, create, fix, correct code, a new feature, a bugfix, or a functionality.
| name | feature-flags |
| description | Feature flags and toggles management. Trigger when the user wants to implement feature flagging, A/B testing, or progressive deployment. |
| allowed-tools | ["Read","Write","Edit","Glob","Grep"] |
| context | fork |
| user-invocable | false |
SDK code, targeting rules syntax and dashboard integration drift on each vendor release and are canonical at:
| Type | Purpose | Lifetime |
|---|---|---|
| Release toggle | Deploy inactive code; flip on after smoke test | Short (days/weeks) |
| Experiment toggle | A/B test; emits exposure events for analysis | Bounded by experiment duration |
| Ops toggle | Circuit breakers, kill switches, degraded modes | Long-lived |
| Permission toggle | Feature gating by role/plan/cohort | Permanent (treat like config) |
Choose by lifetime: short → cheap implementation, long-lived → invest in observability + naming discipline.
qa-tech-debt.<scope>_<feature>_<variant> (e.g. checkout_express_enabled). Scope-first sorts/filters cleanly in dashboards.growth-ab-test skill — experiment design, sample-size, exposure analysis (consumes experiment toggles)qa-tech-debt — flag-debt scan surfaces stale flags past the 2-sprint windowdev-tdd — flag-gated code paths must be tested in BOTH states (on/off), not just the new path