cycle-review
Cycle Review
The cycle review is a round trip through a GitHub Discussion. Branch A publishes the meeting
notes as a Discussion and drafts them as the email agenda, the meeting works through them, the
project manager posts their decisions as a comment, and branch B turns those decisions into tracker
writes. Before branch A or B, load house-rules and writing-lean.
The Discussion is the record, and the baseline the next cycle's notes are diffed against. See Editing Discussions for where they live and how to read and write one.
The notes are not edited during the meeting. The project manager posts a comment using the same headers, and branch B integrates it afterwards.
A cycle is an iteration of the Cycle field; work state is the Status field. Both live on the
CLHbid Delivery project. Read the field mechanics, the Status values, the reference convention
and every board query from the issue-tracker skill — this skill names the recipes it needs and
never restates them, so the two cannot drift.