docs: Add feature flag audit example to PostHog MCP cookbook

[continue]

Summary

Added a comprehensive feature flag audit and cleanup workflow to the PostHog MCP cookbook as requested in CON-4162. This complements the existing session recordings example with another practical use case.

Changes Made

• ✅ Added new "Feature Flag Audit and Cleanup" section
• ✅ Included practical Continue CLI prompts for flag management
• ✅ Added required API scopes ()
• ✅ Updated repository labels to include , ,
• ✅ Provided sample outputs and MCP tool requirements
• ✅ Enhanced advanced prompts section with flag-related examples

Key Features

The new workflow helps users:

• Identify 100% rolled out flags that can be safely removed
• Find stale flags that haven't been updated in 90+ days
• Detect overly complex targeting rules that need simplification
• Create organized GitHub issues for flag cleanup tasks
• Correlate flag performance with user experience metrics

Example Use Cases

• Flag Cleanup: "🏁 Feature Flag Cleanup: dark-mode-toggle" (100% rollout, safe to remove)
• Flag Review: "🏁 Feature Flag Review: experimental-checkout" (unused for 120 days)
• Flag Simplification: "🏁 Feature Flag Simplify: complex-user-targeting" (overly complex rules)

This addresses the request to add feature flag auditing as another example alongside session recordings in the PostHog cookbook.

fixes CON-4162

---

This agent session was co-authored by nate and Continue.

---

Summary by cubic

Adds a feature flag audit and cleanup workflow to the PostHog MCP cookbook so teams can find stale or 100% rollout flags and create cleanup tasks. Addresses CON-4162 by adding a second practical example alongside session recordings.

• New Features

  • Added Feature Flag Audit and Cleanup in Example Use Cases (with a dedicated card).
  • Included practical Continue CLI prompts and sample outputs for flag analysis and issue creation.
  • Listed required PostHog MCP tools for flag auditing.
  • Expanded advanced prompts to correlate flags with performance impact.

• Migration

  • Add PostHog OAuth scope: feature_flag:read.
  • Ensure repo labels exist: technical-debt, feature-flag, cleanup.

[github-actions]

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

• feat: add changelog generation support
• fix: resolve login redirect issue
• docs: update README with new instructions
• chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

• 📝 Automatic changelog generation
• 🚀 Automated semantic versioning
• 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

[bdougie]

@sestinj try this out and see if it works. You mentioned this idea for the PostHog MCP IRL, and I had the agent open a PR.

[sestinj]

🎉 This PR is included in version 1.22.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sestinj]

🎉 This PR is included in version 1.26.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sestinj]

🎉 This PR is included in version 1.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀