retrospectivelisted

______________________________________________________________________ ## retrospective Run a sprint or weekly retrospective: ## 1. Gather Data Read sprint specs and progress to build a complete picture: - Read `docs/progress.md` → `## Sprint History` table for trend data - Read the sprint spec(s) being reviewed: `docs/sprints/sprint-N.md` — especially the `## Outcome` and `## Decisions` sections - Git log for commits and their messages - Any blockers or issues encountered (from sprint spec `## Notes` and `## Decisions`) ## 2. Metrics Dashboard ### 2.1. Progress Metrics (single source of truth) Read `docs/progress.md` → `## Metrics` table and display it directly — sprint-end already computed these values. | Metric | Current | Target | Trend | Status | |:-------|:-------:|:------:|:-----:|:------:| [Copy all rows from progress.md Metrics table] **Sprint note:** [Copy from progress.md if present] ### 2.2. Sprint-over-Sprint Comparison Read `docs/progress.md` → `## Sprint History` table. Extract the last 2 rows (current and previous sprint): | Metric | This Sprint | Previous | Δ | Direction | |--------|-------------|----------|---|-----------| | Goal achieved | [✅/❌] | [✅/❌] | — | [streak] | | Tasks completed | [X] | [Y] | [+/-] | [↑/↓/→] | | Cycle time | [X.Xd] | [Y.Yd] | [+/-] | [↑/↓/→] | | Change failure rate | [X%] | [Y%] | [+/-] | [↑/↓/→] | | Test coverage Δ | [+X%] | [+Y%] | [+/-] | [↑/↓/→] | | Code churn ratio | [0.XX] | [0.YY] | [+/-] | [↑/↓/→] | | AI effect