Repository navigation
feat(feature-flags): add the feature-flags orchestrator agents - #428
Merged
Merged
Conversation
The wizard feature-flags command runs an orchestrator flow named feature-flags. Its six agents (seed, install, init, create-flag, evaluate, report) live here so the wizard fetches them like every other flow instead of bundling its own prompts. create-flag may Read, so it can open skill references. report publishes the setup report to a PostHog notebook through publish_handoff and writes no report file; the run does not check that an evaluation reached PostHog, so the report says how to confirm it and states each flag's active state from the create-flag handoff. Constraint: wizard#1322 ships only after this is published Confidence: high Scope-risk: narrow
wizard-workbench runs its feature-flags legs in parallel against one project with the same example keys, so a flag can appear between create-flag's keyed lookup and its create call. An e2e run hit "There is already a feature flag with this key" there. create-flag now looks the key up once more and reuses the flag unchanged. Confidence: high Scope-risk: narrow
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Test against a wizard branch:
Add Results will be posted here when complete. |
gewenyu99
approved these changes
Oct 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Feedback wanted: ready to merge. Approve or request changes. PostHog/wizard#1322 ships after this is published.
The
wizard feature-flagscommand runs an orchestrator flow namedfeature-flags, and the wizard fetches every flow's agents from context-mill. This flow has no agents here yet.Companion PRs: wizard (PostHog/wizard#1322) and wizard-workbench (PostHog/wizard-workbench#4483).
Changes
context/agents/feature-flags/with six agents: thesetup-feature-flagsseed,install,init,create-flag,evaluate, andreport. The seed decides which sides the app has (backend, frontend) and passes them to every task as asidesinput.create-flagmakes one example flag per side,wizard-example-backend-flagandwizard-example-frontend-flag, inactive at 0% rollout, and reuses an existing flag unchanged, including one another run created after its lookup. It mayRead, so it can open skill references.evaluateloadsintegration-v2-feature-flags-stepfor the framework's flag docs and adds one evaluation per flag on its own side, with the keys in a constants module.reportpublishes the setup report throughpublish_handoff, which mirrors it into a PostHog notebook, and writes no report file. It states each flag's active state from thecreate-flaghandoff and how to confirm an evaluation reaches PostHog; the run itself does not check.Test plan
pnpm test: 219 tests pass.pnpm buildemits the sixagents-feature-flags-*.mdfiles and adds the flow toagent-menu.json.pnpm wizard-ci feature-flags/<app> --e2e:next-js/15-app-router-saaspassed every check: both flags inactive at 0%, both keys inlib/posthog-feature-flags.ts, and the outro links the report notebook.django/django3-saaspassed every check with only the backend flag (its templates hold no scripts), the key indashboard/feature_flags.py, and the report notebook linked in the outro. It needs a Python withpip; a machine without one fails the install task.create-flagretry on an existing key landed after these runs. It came from the parallel Next.js run hitting "There is already a feature flag with this key".LLM context
Written with Claude Code.