retrospective

/aiagentminder:retrospective - Sprint Retrospective

Generate a brief retrospective for the completed sprint. Called automatically at sprint completion, or invoke manually with /aiagentminder:retrospective.

---

Step 1: Gather Sprint Data

Read the following:

1. .sprint-metrics.json — if present, use as primary metrics source (timestamps, cycle counts, rework). Fall back to git log parsing when the metrics file is absent (backward compatible with sprints that ran before metrics collection was added).
2. SPRINT.md — sprint goal, issue list, final statuses (including Post-Merge column)
3. Use TaskList to get final task states and any notes
4. DECISIONS.md — identify entries added during this sprint (by date or sprint reference)
5. Recent git log for this sprint's branches:

   git log --oneline --merges --since="sprint start date"
   

6. Check for any issues that were added or removed after approval (scope changes)

---

Step 2: Compute Metrics

From the data gathered, calculate:

Metric	Value
Planned issues	How many issues were in the approved sprint
Completed issues	How many reached done
Rework items	How many items required rework (post-merge validation failures or test failures after initial "done")
Blocked issues	How many are still blocked at sprint end
Post-merge validations	How many items had post-merge validation tasks; how many passed vs. failed
Risk-tagged issues	How many had [risk] tag
Scope additions	Issues added after sprint approval
Scope removals	Issues removed after sprint approval
Decisions logged	DECISIONS.md entries added this sprint

---

Step 3: Present the Retrospective

Sprint S{n} Retrospective
Goal: {sprint goal}
Date: {today}

Delivery:
  Planned:    {n} issues
  Completed:  {n} issues  ({%} completion rate)
  Rework:     {n} items   [list IDs and failure description if any]
  Blocked:    {n} issues  [list IDs and blocker reason if any]

Quality:
  Post-merge validations: {n} defined, {n} passed, {n} failed
  {If rework items exist: "Rework was needed for: [list items and root cause]"}

Scope:
  {No scope changes} OR {Added: [issue titles] / Removed: [issue titles]}

Decisions:
  {n} decisions logged this sprint
  {list decision topics, one line each — e.g., "Auth approach: JWT over sessions"}

Patterns:
  [One honest observation about what went well]
  [One honest observation about what was harder than expected — e.g., "S2-003 required rework due to staging env mismatch"]

Tooling findings (about AIAgentMinder itself, not this project):
  {None} OR {one line per finding: "{type}/{severity}: {summary}"} — see Step 5