Make the flags-not-megabranch pattern (pickforge/pickforge#152, @pickforge/flags from #10) a workspace-wide default policy instead of a per-epic rule, so multiple in-flight features stay trackable from merge to release.
The rule being codified (decision rule, not "always flag"):
- Flag a feature when it merges to main before the release that enables it (multi-PR, spans releases, or held back).
- Skip the flag when the feature ships in the next release anyway — the release tag is the switch.
- Flags come from
@pickforge/flags, default-off; enabling = shipping a new default.
- Flag removal is part of the feature, not optional cleanup.
Checklist
Validation
gh label list shows flagged in all four app repos- Release-skill PR through the normal review loop
Note: plan-issue/kickoff skills and workspace AGENTS.md live outside tracked repos — those edits are direct, recorded here. Only the release skill change gets a PR.
Make the flags-not-megabranch pattern (pickforge/pickforge#152,
@pickforge/flagsfrom #10) a workspace-wide default policy instead of a per-epic rule, so multiple in-flight features stay trackable from merge to release.The rule being codified (decision rule, not "always flag"):
@pickforge/flags, default-off; enabling = shipping a new default.Checklist
AGENTS.md: canonical "Feature flags" section (other docs reference it, never restate)plan-issueskill: flagged-feature lifecycle checklist (merged behind flag → tested on main → enabled in vX.Y.Z → flag removed)kickoffskill: flag-or-not decision at planning time, recorded in the issuereleaseskill (this repo): note which flags the version flips; check for stale flags shipped enabled earlier → PRflaggedlabel in pickforge, pickscribe, pickgauge, picklabValidation
gh label listshowsflaggedin all four app reposNote:
plan-issue/kickoffskills and workspaceAGENTS.mdlive outside tracked repos — those edits are direct, recorded here. Only thereleaseskill change gets a PR.