SOTG
← Back to The Library

The End-of-Season Debrief — One Workflow, the Full Stack

The End-of-Season Debrief — One Workflow, the Full Stack
Section 01 — Why this matters

End of season. Two weeks of writing, reviewing, and presenting back — to the squad, the staff, the board, the owners. The information is everywhere: Fireflies transcripts of every coaches' meeting, your Season Project, every Player Project, every match review. This is the workflow that runs the entire chain at season scale. Tier: Claude Pro + Fireflies Pro + Gamma Pro. The most expensive workflow in the library, and the one that pays back fastest.

Section 02 — What this actually upgrades

A output tool, not a notes tool. The distinction matters.

Layer · Output

This upgrades the Output layer for the moment of the season where output matters most. Every previous workflow in this batch — projects, MCP, meeting brain, deck pipeline — converges here. The whole stack becomes one assembly line.

Cognitive load removed

It removes the 'I have to be the entire ops team for two weeks' load. You stay the editorial brain; everything else delegates.

Workflow slot

The week the season ends. Block a half-day for the first run-through; the full deck and supporting docs are usually ready by end of day 2.

Section 03 — This week's upgrade

Three steps. Twelve minutes total.

  1. Step 01
    Install
    In Claude Pro, open the Season Project. Run the master prompt below: 'Pull from Fireflies all coaches' meetings, board meetings, and review meetings from the last [N] months. Pull from each Player Project the headline progression. Pull from Project Knowledge the principles and pre-season targets. Build the season-debrief outline.'
  2. Step 02
    Use once
    Claude returns a 12-section outline — pre-season targets, what was achieved, what wasn't, why, individual player narratives, staff narratives, operational learnings, recommendations for next season. Read every word. The structure is right; the judgement calls are yours. Edit until it's defensible.
  3. Step 03
    Store
    Build three deliverables in parallel from the same source: • A Gamma deck for the board (executive aesthetic, 12–15 slides) • A Gamma deck for the squad (different framing — what we built together, what's next) • A long-form written document for the staff and incoming coaches (detail the decks won't carry) All three feed off the same Claude-generated outline. Total assembly time: 2–3 hours after the outline is approved.
Section 04 — The prompts

3 prompts, one unlocked.

Master pull promptClaude Pro (with Fireflies + Drive MCP)
Using Fireflies, pull every meeting in the last 9 months (or full season — adjust dates as needed) tagged: Coaches Meeting, Senior Leadership, Board, Performance Review, Player 1:1.

Using Project Knowledge across all my Player Projects, pull each player's pre-season target and current progress note.

Using the Season Project Knowledge, pull the pre-season principles and stated targets.

Return raw aggregated material organised under these headers:
1. Pre-season targets (verbatim from Knowledge)
2. Tactical decisions made during the season (with dates)
3. Player progressions, by player
4. Staff changes
5. Operational issues that recurred (anything raised in 3+ meetings)
6. Wins (with citations)
7. Failures or unmet targets (with citations)

Do not summarise yet. I want the raw material first.
Outline construction promptClaude Pro
Member-only prompt — click to unlock.
🔒 Member only
Free email account unlocks all prompts.
Three-deliverable split promptClaude Pro
Member-only prompt — click to unlock.
🔒 Member only
Free email account unlocks all prompts.
Section 05 — How each role uses it

Same tool. 3 different jobs.

Head Coach
uses it to deliver three coherent end-of-season narratives where they used to deliver one rushed one.
Performance Ops
uses the staff written document as the operational handover for the next pre-season.
Performance Analyst
uses it to compile the data appendices that the decks reference but don't show.
Section 06 — Who shouldn't use this
⚠ Skip this if
If you've not been recording meetings or maintaining player projects across the season, you can't run this workflow at the season's end. Start now for next season — this is one of the few workflows where the prep is non-trivial and the payback is at a fixed moment in the year.
Section 07 — Stack position

Where this fits in the system.

Section 08 — Leverage scorecard

The spec sheet.

The End-of-Season Debrief — One Workflow, the Full Stack · Output
SOTG-17
10/ 10
Leverage Score
Time to install6 hours (first season); 3 hours thereafter
Time saved per weekreclaims 60–80 hours at season end
Cognitive load removedHigh
AI literacy requiredMedium
Free tier sufficientNo