<!-- docs/retrospectives/fall.md -->

# Retrospective

Run the 4Ls session first (Liked, Learned, Lacked, Longed for), then distill it here. The write-up is themes and actions, not the raw sticky notes. The [Term Retrospective](https://capstone.alexulbrich.com/assignments/term-retrospective/) page owns the format.

## Themes (from the 4Ls)

2 or 3 patterns that explain the term, not a list of events.

### Theme A: _<name the pattern>_

- **What we saw (examples):**
- **Why this happened (plausible causes):**
- **So what for next term:**

### Theme B: _<name the pattern>_

- **What we saw (examples):**
- **Why this happened (plausible causes):**
- **So what for next term:**

### Theme C (optional): _<name the pattern>_

- **What we saw (examples):**
- **Why this happened (plausible causes):**
- **So what for next term:**

## Evidence

At least one artifact per theme (a PR, a review thread, a board snapshot, a chart) with a caption saying what it shows. Screenshots or links are fine; NDA teams use PR titles or IDs only.

## Team Actions (3)

Each action has a single owner (a name, not "the team"), a timeframe, and a plain recognition cue so you can tell it is working.

1. **Action**: ... Owner: ... By: ... We will know it works when: ...
2. **Action**: ... Owner: ... By: ... We will know it works when: ...
3. **Action**: ... Owner: ... By: ... We will know it works when: ...

## Individual Pages

One short page per student, clearly labeled. 1 or 2 wins and 1 or 2 gaps, each tied to a concrete example (a PR, a review, a decision you drove or dodged), plus **one** commitment for next term: what you will do differently, how progress will be visible, and by when.

### <Student name>

- **Wins:**
- **Gaps:**
- **Commitment:**

## Optional Appendix

Extra screenshots, quoted snippets, links, or notes you do not want in the main flow.
