team-retro

Independently evaluate whether a team's planner, code lead, coders, reviewers and minder are converging on their gate tickets, on a schedule, like a sprint retro. Takes metric snapshots with ix-board retro, compares them with the previous snapshot and a baseline, scores the role rubrics, names the repeating loops and messages the planner, code lead or user with owned actions. Use when invoked as /team-retro <team> [interval], or when asked to find out why a team is busy but not finishing, to run a retro, or to set up a recurring health check.