Weekly retro board, ready to go
Auto-create a fresh retrospective board in Miro before each sprint retro — set up and waiting.
Every Monday morning, set up this week's sprint retrospective board in Miro so it's ready before the
team meets.
Create a new board named "Retro — week of <this Monday's date>". Lay it out with three clearly
labelled columns as large frames, left to right:
1. What went well
2. What could improve
3. Action items
Add a short title at the top and a one-line instruction ("Add a sticky under each column before the
retro"). Keep it clean and empty — the team fills it in. If we have a standard retro format you know
about, follow it.
Then give me the board's shareable link in your result so I can drop it into the calendar invite.Weekly retro board — 29 Jun 2026 ✅ Created: "Retro — week of 29 Jun 2026" • 3 columns: What went well · What could improve · Action items • Header + instruction added, columns empty and ready Open it → [board link] Drop this link into today's retro invite.
Someone always ends up creating the retro board five minutes before the meeting. This routine does it every Monday — a fresh, cleanly laid-out retrospective board with the right columns — and emails you the link, so setup is done before the day starts.
How it works
- It uses Miro to create a new board each week with three labelled columns for the retro.
- The board is left empty and ready — the team fills in stickies during the meeting.
- The shareable link lands in your inbox, ready to paste into the calendar invite.
Make it yours
- Change the columns to your team's format (Start/Stop/Continue, Mad/Sad/Glad, 4Ls).
- Shift the cadence to match your sprint length — every two weeks, or the day before your retro.
- Pair it with Google Calendar so the routine can find your retro event and attach the link for you.
Run “Weekly retro board, ready to go” on autopilot
Copy it to your account, tweak the details, and it runs mondays at 9:00 am.
Use this routine →More Engineering templates
Every Friday, scan Cloudflare's developer docs for the Workers, Pages, and security features that matter to your setup — plus recent changelog posts — emailed as a prioritized digest.
Every Monday, check Context7 for the current documented version, API, and migration notes of the libraries your project depends on — emailed as a short upgrade to-do list.
Every Thursday, ask DeepWiki what's new in the public GitHub repos you depend on — releases, breaking changes, and migration notes — emailed as a prioritized summary.
Each weekday, triages new, stale, and needs-triage issues across the repos you pick — grouped, prioritized, with a suggested label and owner per issue.