sprint-review-summarizer

Sprint Review Summarizer

This skill transforms plain-language sprint summary notes into a structured stakeholder document covering delivered items, deferred work, risks, and next sprint focus. It works from any free-form text or markdown file — no integrations, no YAML, no Jira required.

Input:

• Sprint notes as pasted text or markdown file (any format accepted)
• Optional: sprint number, team name, sprint goal (for metadata enrichment)

Output:

• Markdown stakeholder document with sections: Executive Summary, Delivered, Deferred, Risks & Issues, Next Sprint Focus, Key Decisions (if detected)

---

Language Detection

Detect the user's language from their message:

• If Russian (or contains Cyrillic): respond in Russian
• If English (or other Latin-script language): respond in English
• If ambiguous: respond in the language of the trigger phrase used

---

Instructions

Step 1: Validate and Parse Input

1. Check that sprint notes content is provided (pasted text or file reference)

   • If input is empty or whitespace only: Stop. Return: "No sprint notes provided. Paste your sprint summary or provide a file path."

2. Check input format

   • If input resembles a structured Jira/CSV export (column headers, ID fields, etc.): Inform the user — "This looks like a structured export, not plain-language notes. This skill works best with free-form sprint notes." Offer to attempt processing if user confirms.
   • Otherwise: proceed with parsing

3. Extract optional sprint metadata if present in notes:

   • Sprint name or number (e.g., "Sprint 24", "Q2 Sprint 3")
   • Dates (e.g., "May 5–19")
   • Team name
   • Sprint goal
   • If metadata is missing: use placeholder "Sprint [YYYY-MM-DD]" for the heading and continue without blocking

Step 2: Classify Items into Four Categories

1. Read all content and identify discrete items (sentences, bullet points, paragraphs describing work)

2. Map each item to one of four categories using semantic heuristics: