Sprint summary

Group team updates into completed work, blockers, and next week's plan.

Summarize the supplied team messages for the requested date range. Organize the result into completed work, blockers, and next week's plan. Use brief bullets and merge repeated updates about the same work.

Count work as completed only when the messages say it is complete. Keep work in progress distinct from finished work. For blockers, preserve the impact, owner, and dependency when stated. For planned work, retain explicit priorities and dates.

Do not invent progress, commitments, estimates, or a plan where none was recorded. Note meaningful contradictions or missing status. Keep links and identifiers needed to find the original work. If no date range is provided, summarize the supplied messages and state their available date range.

Example

Fictional sprint messages

Before 121 words

Team messages, 7–11 September: 7 September, Mei: EXP-72 is nearly ready, but the export permission check is still failing. Nothing has shipped yet. 8 September, Mei: The permission check now passes. We still need the release review. 9 September, Mei: EXP-72 passed review and shipped. Customers can export their own case records; administrators can export all records. 10 September, Joel: Mobile testing for MOB-19 cannot start because the test handset has not arrived. I own the testing; procurement is checking delivery, but no arrival date is confirmed. 11 September, Mei: To repeat Wednesday's update, EXP-72 is now live. 11 September, Joel: Next week, MOB-19 testing is the priority if the handset arrives. We have not committed to finishing it next week.

After 59 words

7–11 September Completed - EXP-72 shipped on 9 September after permission checks and review. Customers export their own case records; administrators export all. Blockers - MOB-19 testing cannot start without the handset. Joel owns testing; procurement is checking delivery. Arrival date unconfirmed. Next week's plan - Prioritize MOB-19 testing if the handset arrives. Completion next week is not committed.

Examples illustrate the method. They do not measure model output.

Files and sources

prompt.txt Complete prompt as plain text.
SKILL.md The same prompt with a skill header.
llms.txt (JSON) Prompt, metadata, example, and sources.
LICENSE MIT license text.

Adapted from pnp/copilot-prompts · Weekly Sprint Summary from Teams Channel. Source notes.