{
  "schema_version": 2,
  "kind": "shortening-method",
  "format": "agent-skill",
  "id": "sprint-summary",
  "name": "Sprint summary",
  "category": "Work",
  "summary": "Group team updates into completed work, blockers, and next week's plan.",
  "use_cases": [
    "Sprint channel updates",
    "Team status reports",
    "Weekly engineering reviews"
  ],
  "word_count": 115,
  "url": "https://sho.rten.it/methods/sprint-summary/",
  "instructions_url": "https://sho.rten.it/methods/sprint-summary/SKILL.md",
  "skill_url": "https://sho.rten.it/methods/sprint-summary/SKILL.md",
  "json_url": "https://sho.rten.it/methods/sprint-summary/llms.txt",
  "plain_text_url": "https://sho.rten.it/methods/sprint-summary/prompt.txt",
  "license": "MIT",
  "sources_url": "https://sho.rten.it/sources/#sprint-summary",
  "skill_name": "sprint-summary",
  "skill_description": "Group team updates into completed work, blockers, and next week's plan. Use for Sprint channel updates, Team status reports, Weekly engineering reviews.",
  "agents_md_url": "https://sho.rten.it/methods/sprint-summary/AGENTS.md",
  "sources": [
    {
      "title": "pnp/copilot-prompts · Weekly Sprint Summary from Teams Channel",
      "url": "https://github.com/pnp/copilot-prompts/blob/11e6e1e4d5b587f87e1fb4babbcda48c1c5c4746/samples/prompts/m365-teams-sprint-summary/README.md",
      "repository": "https://github.com/pnp/copilot-prompts",
      "revision": "11e6e1e4d5b587f87e1fb4babbcda48c1c5c4746",
      "path": "samples/prompts/m365-teams-sprint-summary/README.md",
      "license": "MIT",
      "license_url": "https://github.com/pnp/copilot-prompts/blob/11e6e1e4d5b587f87e1fb4babbcda48c1c5c4746/LICENSE",
      "license_file": "licenses/pnp--copilot-prompts.txt",
      "copyright": "Copyright (c) 2024 Microsoft 365 & Power Platform Community",
      "repository_stars": 875,
      "checked_at": "2026-09-10",
      "license_scope": "Root MIT license covers this repository's samples; no separate license or NOTICE files found in the pinned tree.",
      "adaptation": "Keeps the source's date-bounded completed/blockers/next-plan structure. Replaces Teams lookup with supplied messages and protects completion state, dependencies, and commitments.",
      "author": "Sai Siva Ram Bandaru"
    }
  ],
  "instructions": "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.\n\nCount 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.\n\nDo 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": {
    "before": "Team messages, 7–11 September:\n7 September, Mei: EXP-72 is nearly ready, but the export permission check is still failing. Nothing has shipped yet.\n8 September, Mei: The permission check now passes. We still need the release review.\n9 September, Mei: EXP-72 passed review and shipped. Customers can export their own case records; administrators can export all records.\n10 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.\n11 September, Mei: To repeat Wednesday's update, EXP-72 is now live.\n11 September, Joel: Next week, MOB-19 testing is the priority if the handset arrives. We have not committed to finishing it next week.",
    "after": "7–11 September\n\nCompleted\n- EXP-72 shipped on 9 September after permission checks and review. Customers export their own case records; administrators export all.\n\nBlockers\n- MOB-19 testing cannot start without the handset. Joel owns testing; procurement is checking delivery. Arrival date unconfirmed.\n\nNext week's plan\n- Prioritize MOB-19 testing if the handset arrives. Completion next week is not committed.",
    "context": "Fictional sprint messages",
    "must_preserve": [
      "Available range: 7–11 September; release on 9 September",
      "EXP-72 passed permission checks and review; customer and administrator export scopes differ",
      "MOB-19 is blocked by the missing handset; Joel owns testing and procurement is checking delivery",
      "Arrival is unconfirmed; next week’s testing is conditional and completion is not committed"
    ],
    "omitted": [
      "Repeated release announcement and superseded almost-ready status"
    ],
    "kind": "illustrative"
  }
}