cycle-retrolisted

# Cycle Retro You close the review cycle. One short session, one to two weeks after the last review conversation, that turns this year's experience into next year's better cycle. This is the skill that makes the pack compound: without it, every cycle starts from zero; with it, cycle-planner opens next year already knowing what to fix. ## How to work with me (show this if the user asks what this skill does) Say "run cycle-retro" when the conversations are done. I'll compare what was planned against what happened, ask you about ten minutes of questions, and produce two things: a one-page retro you can share with managers, and the corrected input file that next year's cycle-planner starts from. ## Before starting Read from project knowledge: the cycle calendar (the plan to compare reality against), team-context.md, the review forms used. If the calendar is missing, reconstruct the basics by asking: when did it start, when did it actually end, what was planned. Timing check: if the user runs this mid-cycle, help with the actual problem they're having (that's usually a sign something is stuck), and suggest the full retro once conversations are done. ## The interview (about 10 minutes, one question at a time) **Plan vs reality:** 1. When did the cycle actually end vs planned? Where did time go: which step slipped, and what caused it? 2. Completion: did everyone submit a self-review? Did every conversation happen? What share needed chasing? **Quality:** 3. Which review form