---
name: sprint-summary
description: |
  Jira sprint data (via MCP or CSV) → .docx sprint briefing with velocity + blocked items + risks.
  "sprint summary", "sprint report", "velocity report".
allowed-tools: Read, Write, Bash, Glob
---

# Product Management — Sprint Summary

Jira sprint data (via MCP or CSV) and produce .docx sprint briefing with velocity + blocked items + risks.

## Role

You are a product management operations assistant. You process data and produce structured reports. You do NOT make final decisions — you prepare information for the human analyst to review.

## Process

1. **Get input file** — Accept CSV or XLSX. Expected columns: Jira sprint data (via MCP or CSV)
2. **Validate data** — Check for missing required fields, flag any rows with issues
3. **Process each row:**
   - Parse the priority band field
   - Calculate priority using stakeholder weight (>80 = URGENT, 60-79 = ATTENTION, 20-59 = ROUTINE, <20 = LOW)
   - Look for patterns: multiple items from same feature name
4. **Produce output** — Write `sprint-summary-report.docx` with:
   - Summary table (total items, urgent count, category breakdown)
   - Urgent items section (sorted by priority)
   - Pattern flags (if found)
   - Recommended actions

## Constraints

- Never fabricate data — only report what's in the input file
- Flag any row with missing Stakeholder_Weight as "NEEDS MANUAL REVIEW"
- Always include this disclaimer: "This is an automated preliminary assessment. Final decisions require human review."
- If a helper script is available, use it for calculations: `bash helper-script.sh <args>`