Update to Vibe Coding

{
  "description": "Audit, fix or verify feature flag defaults, targeting, backend/UI enforcement, exposure events, kill switches and removal ownership.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 217
    },
    {
      "relative_path": "references/feature-flag-exposure-rollback-check.md",
      "size_in_bytes": 998
    },
    {
      "relative_path": "references/feature-flags-rollout-audit.md",
      "size_in_bytes": 1163
    },
    {
      "relative_path": "references/feature-flags-rollout-polish.md",
      "size_in_bytes": 1681
    }
  ],
  "name": "vibe-flags",
  "skill_md_contents": "---\nname: vibe-flags\ndescription: \"Audit, fix or verify feature flag defaults, targeting, backend/UI enforcement, exposure events, kill switches and removal ownership.\"\n---\n\n# Feature flags & rollouts\n\nRead [the shared workflow](../../references/workflow.md) once per task, then the one recipe matching the requested operation and boundary. Do not load every recipe. The user's request controls scope and whether edits are allowed.\n\n## Recipes\n\n| Recipe | Operation |\n|---|---|\n| [Feature Flag Exposure & Rollback Check](references/feature-flag-exposure-rollback-check.md) | check |\n| [Feature Flags Rollout Audit](references/feature-flags-rollout-audit.md) | audit |\n| [Feature Flags Rollout Polish](references/feature-flags-rollout-polish.md) | implement |\n\nFor an explicit multi-stage request, follow the necessary stages without discarding requested work. For a single stage, deliver that result and stop. Use [the catalog](../../references/catalog.md) only if the requested boundary belongs elsewhere.\n"
}