sprint-retro

BASE_DIR=!~/.agents/scripts/get-env NOTES_DIR TODAY=!date +%Y-%m-%d YEAR=!date +%Y MONTH=!date +%m DAY=!date +%d

Generate Sprint Retrospective

Produces a structured sprint retrospective by reviewing the past two weeks of daily notes, GitHub activity, and Slack activity.

Prerequisites

• Slack MCP server connected and authenticated
• gh CLI authenticated
• NOTES_DIR environment variable set (resolved via ~/.agents/scripts/get-env NOTES_DIR)
• ~/.agents/scripts/get-env utility available
• At least one week of daily notes present in {BASE_DIR}

Steps

1. Gather Data

1. Resolve the notes directory:

   ~/.agents/scripts/get-env NOTES_DIR
   

2. Read all daily note files from the past two weeks within {BASE_DIR} (.github.md, .slack.md, .overall.md, .timeline.md, weekly summaries).
3. Fetch recent GitHub activity (PRs opened, reviewed, merged; issues closed) for the past two weeks using gh.
4. Fetch recent Slack activity via the Slack MCP server for context on collaboration, blockers, and thanks.

2. Analyze and Categorize

Review all gathered data and categorize findings into the five retrospective sections below.

3. Write Retrospective

Write the output to {BASE_DIR}/{YEAR}/{MONTH}/{DAY}.sprint-retro.md using this template:

# Sprint Retrospective ({TODAY})

## Kudos
People who helped, collaborated well, or went above and beyond.
- **[Person]**: [What they did and why it mattered]

## Went Well
Things that worked effectively this sprint.
- [Item with brief supporting evidence]

## Could Have Gone Better
Things that did not go as smoothly as hoped.
- [Item with brief explanation of what happened]

## What Would I Have Needed to Move Faster This Sprint?
Blockers, missing context, tooling gaps, or process friction that slowed progress.
- [Item with specific suggestion if possible]

## Action Items
Concrete next steps to improve the next sprint, derived from the sections above.
- [ ] [Actionable item with owner if applicable]