Sprint Summary Generator — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Sprint Summary Generator (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill takes a raw list of completed tickets, commit messages, or PR titles from a sprint and produces a polished sprint summary document suitable for stakeholders, leadership, or the whole team. It groups work into meaningful themes, translates technical changes into business language, flags blockers and carryover items, and formats everything for a Slack post, email, or wiki page.
Use this at the end of every sprint to save time writing the sprint review, or to quickly communicate what shipped to non-technical stakeholders.
Copy this file to .agents/skills/sprint-summary-generator/SKILL.md in your project root.
Then ask:
Provide:
Add the instructions below to your .cursorrules or paste them into the Cursor AI pane. Paste the ticket list and any context before asking for the summary.
Paste all available information (ticket list, sprint dates, blockers) and ask Codex to follow the instructions below.
When asked to generate a sprint summary, follow these steps:
For each completed item:
Group the completed items into 2–5 themes based on similarity. Good theme names are:
Don't create more themes than there are meaningful groups — it's fine to have just two.
Follow these writing principles:
Produce two versions: a short Slack/chat version and a full written version.
Slack version (short):
*Sprint [N] — [Date Range]* ✓ Shipped
*[Theme 1]*
• [Item 1 — one sentence, outcome-focused]
• [Item 2]
*[Theme 2]*
• [Item 1]
*Carried over*: [Item or "Nothing — clean sprint!"]
*Next sprint focus*: [1 sentence on what's coming]Full written version:
# Sprint [N] Summary — [Date Range]
## Highlights
[2–3 sentence paragraph describing the most important things that shipped this sprint and why they matter]
## What We Shipped
### [Theme 1]
- **[Feature/fix name]**: [1–2 sentences describing the change and its impact]
- ...
### [Theme 2]
- ...
## Bug Fixes & Reliability
[List significant bug fixes with a brief note on impact]
## Infrastructure & Technical Work
[List infra/tech debt items briefly — these are real but less exciting to stakeholders]
## Metrics
| Metric | Sprint start | Sprint end |
|--------|-------------|------------|
| [e.g., Page load time] | [value] | [value] |
[Only include if metrics were provided]
## Carryover
- [Item 1] — [brief reason it didn't make it]
- [or "None — clean sprint"]
## Blockers & Risks
[Any blockers encountered and how they were resolved, or ongoing risks]
## Next Sprint Preview
[1–3 bullet points on planned priorities]Input to Agent:
"Use the Sprint Summary Generator skill. Sprint 14, March 3–14 2026.
>
Completed: - Add email notifications for order status changes - Fix broken pagination on /admin/users - Upgrade Next.js from 13 to 14 - Add skeleton loading states to dashboard - Fix memory leak in the WebSocket handler - Improve DB query on reports page (was timing out for large accounts) - Add CSV download to reports page - Fix typo in welcome email subject line
>
Carried over: Stripe billing portal integration (blocked on Stripe API access) Notable: memory leak fix resolved the nightly crash that had been affecting ~5% of users"
Output from Agent:
Sprint 14 — March 3–14, 2026 ✓ Shipped
>
Reports & Dashboard • Added CSV download to the reports page • Reports page now loads correctly for large accounts (was timing out before) • Added loading skeletons to the dashboard for a smoother experience
>
Notifications & Emails • Users now receive email notifications when their order status changes • Fixed a typo in the welcome email subject line
>
Reliability • Fixed a memory leak that was causing ~5% of users to experience nightly service disruptions • Fixed broken pagination in the admin user list
>
Carried over: Stripe billing portal integration — blocked on Stripe API access approval
>
---
>
Full Summary:
>
# Sprint 14 Summary — March 3–14, 2026
>
## Highlights Sprint 14 delivered meaningful improvements to the reports experience and fixed a longstanding reliability issue. The memory leak fix in our WebSocket handler eliminates the nightly crash that was affecting roughly 5% of active users. We also shipped two highly-requested reports features: CSV export and a fix for timeouts on large accounts.
>
## What We Shipped
>
### Reports & Dashboard - CSV Export for Reports: Users can now download any report as a CSV file directly from the reports page - Reports timeout fix: Optimized the database query behind the reports page — large accounts that were previously seeing timeouts now load in under 2 seconds - Dashboard loading skeletons: Added skeleton loading states so the dashboard feels snappy while data loads
>
### Notifications - Order status email notifications: Users now automatically receive an email when their order status changes to processing, shipped, or delivered
>
## Bug Fixes & Reliability - Fixed a memory leak in the WebSocket handler that was causing nightly service disruptions for ~5% of users - Fixed broken pagination in the admin user management page - Fixed a typo in the welcome email subject line
>
## Infrastructure & Technical Work - Upgraded Next.js from v13 to v14 — improves build times and enables future performance features
>
## Carryover - Stripe billing portal integration — blocked on Stripe API access approval; expected next sprint
>
## Next Sprint Preview - Complete Stripe billing portal integration - Begin work on mobile app notifications
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.