metrics.sprint-retro
Type: commands | Track: Enterprise
Sprint retrospective ceremony. Collects DORA actuals, agent consensus scores, 4L review (Liked, Learned, Lacked, Longed For), and writes retro evidence. Autonomous local-first. Delegates to observability-engineer. Exempt from PO+CA coordination.
Quick Start
# Run sprint retro
/metrics:sprint-retro
# Override sprint
/metrics:sprint-retro --sprint CloudOps-S1
Output Sections
| Section | Content |
|---|---|
| DORA actuals | DF, LT, CFR, MTTR — actual values with target comparison |
| 4L Review | Liked / Learned / Lacked / Longed For |
| Agent consensus | PO + CA + QA scoring round summary |
| ACT items | Improvement actions with owner and sprint assignment |
| Evidence | JSON retro file written to framework/retrospectives/ |
Benefits
- DORA actuals sourced from
dora.csv— no manual metric collection - Agent consensus section captures scoring round outcomes for governance audit trail
- ACT items written with owner and sprint — prevent
DEFERRED_GAP_LOOPwhere retro findings are never executed - Evidence written to
framework/retrospectives/— git-tracked for continuous improvement audit
When to Use
| Attribute | Detail |
|---|---|
| Persona | HITL / Engineering Manager |
| Trigger | Sprint end (bi-weekly) — after the sprint review, when the team needs to reflect on HOW they performed and capture improvement actions with owners |
| Business Value | 4L review, DORA actuals, and improvement actions with owners — gives the team an objective retrospective with actionable outcomes, not just a feelings-based discussion |
| Frequency | Bi-weekly |
Example: As an Engineering Manager (HITL), I need the sprint retrospective output because I need to capture what worked, what didn't, and what we'll change, with specific ACT items assigned to owners before the next sprint starts. I run /metrics:sprint-retro which produces the 4L review from coordination logs, DORA actuals vs targets, agent consensus summary, and ACT items written to framework/retrospectives/sprint-retro-{sprint}-{date}.md.
Coordination-exempt command. Reads existing data only — no architecture decisions.