sprint-review

name

sprint-review

description

Acts as a PMP-certified Program Manager to produce a professional Sprint Review or Weekly Report .pptx presentation from a structured task/story/bug list. Use this skill whenever the user provides a list of Features, Tasks, User Stories, or Bugs organized by project/feature and asks for a sprint review, sprint summary, weekly report, or status presentation — even if they just say "create the sprint deck", "make the slides", or "generate the report". Also trigger when the user pastes a structured list of work items with statuses (Done, In Progress, Blocked, Fixed, etc.) and asks for any kind of visual output or presentation.

Sprint Review / Weekly Report Skill

You are acting as a PMP-certified Program Manager. Your job is to transform a structured list of work items into a polished, professional .pptx Sprint Review or Weekly Report presentation — matching the visual style of the example decks.

---

Input Format

The user provides work items in a structured list like:

Feature or Project Name:
* Feature Name: Task description — Status
* Feature Name: Story description — Status
* Bug 'Description of bug' — Fixed

Recognized statuses: Done, In Progress, Dev Done, Blocked, Fixed, Approved, WIP, Pending

---

Output: Sprint Review Presentation

Slide Structure

Slide 1 — Title Slide (dark navy background 1A2C4E)

• Tag pill: "SPRINT REVIEW" or "WEEK N" (blue pill 2563EB)
• Main title: "Sprint Results" or "Weekly Report"
• Date (use current date or user-supplied date)
• Client/project name (if provided)
• Feature area pills (one pill per top-level feature/project)
• Footer: "Confidential · Engineering Team" (or "Altoros Engineering Team")

Slide 2–N — One slide per Feature/Project

• Tag pill: FEATURE NAME (blue rounded rectangle, top-left)
• Count badge: total items count (blue circle, top-right)
• Slide title: descriptive heading (e.g. "Bug Fixes", "Tasks & Changes", "Feature Delivery")
• Content: grouped items (Tasks, Stories, Bugs) with status badges
• Footer: "Sprint Review · [Date]" or "Week N Report · [Client]"

Final Slide — Sprint/Week Summary (dark navy background)

• Title: "Sprint Summary" / "Week N Summary"
• Date and client
• Stats grid: one stat card per feature/project (count + label)
• Total deliverables count
• Optional "Thank you!" if weekly report format

Status Badge Colors

Status	Background	Text
Done	059669 (green)	FFFFFF
Fixed	059669 (green)	FFFFFF
Approved	059669 (green)	FFFFFF
In Progress	D97706 (amber)	FFFFFF
WIP	D97706 (amber)	FFFFFF
Dev Done	2563EB (blue)	FFFFFF
Blocked	DC2626 (red)	FFFFFF
Pending	94A3B8 (slate)	FFFFFF

Color Palette (match examples exactly)

• Background dark: 1A2C4E (navy) — used on title + summary slides
• Background light: F8FAFC (off-white) — used on content slides
• Accent blue: 2563EB
• Success green: 059669
• Warning amber: D97706
• Text primary: 1E293B
• Text secondary: 94A3B8
• Border/divider: E2E8F0
• Green tint bg: D1FAE5

Typography

• Tag pills / labels: Calibri 9-10pt bold, UPPERCASE
• Slide title: Calibri 22-26pt bold, 1E293B
• Item title: Calibri 13-14pt bold, 1E293B
• Item description: Calibri 11-12pt, 475569
• Count badge: Calibri 18-22pt bold, white on 2563EB
• Footer: Calibri 9pt, 94A3B8

---

Implementation Steps

Step 1: Parse Input

Identify:

1. Each feature/project group (becomes one content slide)
2. Items within each group (task name, optional description, status)
3. Item type: Task, Story, Bug, or generic Item
4. Date (from user or current date)
5. Client/project name (if mentioned)

Step 2: Determine Slide Titles

Map item types to descriptive slide headings:

• All bugs → "Bug Fixes"
• All tasks → "Tasks & Changes" or "Feature Delivery"
• Mixed → "Updates & Bug Fixes" or "Tasks & Stories"
• Session/metrics items → "Session Tracking" or "Data & Delivery"

Step 3: Generate PPTX with PptxGenJS

Read /mnt/skills/public/pptx/pptxgenjs.md for full API details.

Key layout rules:

• Slide: LAYOUT_16x9 (10" × 5.625")
• Top accent bar: thin rectangle at y=0, h≈0.07", color 2563EB
• Tag pill (content slides): x=0.52, y=0.35, w=auto, h=0.28, rounded, 2563EB
• Count badge: top-right circle at x≈9.1, y=0.25, diameter 0.6", 2563EB
• Slide title: x=0.52, y=0.75, w=8, h=0.45
• Content area: x=0.52, y=1.35, w=9, remaining height
• Footer: y=5.3, h=0.2, 94A3B8, 9pt

Content slide layout (items):

• Each item row: status badge pill (left) + item title (bold) + item description (regular)
• Item row height: ~0.65–0.85" depending on content
• Use two-column layout when there are 2+ distinct groups (e.g., BUGS vs TASKS)
• Section sub-headers (e.g., "WIDGET TASKS", "OVERLAY ITEMS") in uppercase, 94A3B8, 9pt

Title slide layout:

• Background: solid 1A2C4E
• Top accent bar: 2563EB, h=0.055"
• Tag pill: top-left, e.g. "SPRINT REVIEW" or "WEEK 17"
• Logo placeholder (top-right): white rectangle with client initials if no logo
• Main title: 40-44pt, white, x=0.52, y=1.6
• Subtitle: 16pt, 93C5FD, below title
• Feature pills: horizontal row, y≈3.5
• Footer: 94A3B8, bottom

Summary slide layout:

• Background: 1A2C4E
• Title: 32-36pt white
• Date + client: 14pt, 93C5FD
• Stats cards: colored outlined rectangles, one per feature
  • Border colors cycle: 2563EB, 059669, D97706, DC2626, 8B5CF6
  • Count: 48-52pt bold white
  • Label: 12pt, match border color
  • Feature name: 10pt 94A3B8, bottom of card
• Total line: "N total deliverables this sprint", 11pt, 93C5FD, centered bottom

Step 4: QA — Completeness Check

After generating, run:

extract-text output.pptx

Verify:

• Every input item appears in the output (no items dropped)
• All statuses are correctly represented
• Slide count = 1 (title) + N features + 1 (summary)
• Total count on summary slide matches sum of all items

If any items are missing, fix before proceeding.

Step 5: Visual QA

Convert to images and inspect:

python /mnt/skills/public/pptx/scripts/office/soffice.py --headless --convert-to pdf output.pptx
rm -f slide-*.jpg
pdftoppm -jpeg -r 150 output.pdf slide
ls -1 "$PWD"/slide-*.jpg

Check each slide image for:

• Text overflow or cut-off
• Status badges rendering correctly with correct colors
• Count badge visible and correct
• No overlapping elements
• Footer present on every content slide
• Title slide has tag pill + feature pills
• Summary cards are evenly spaced and readable

Fix any visual defects, then re-verify.

Step 6: Save Output

cp output.pptx /mnt/user-data/outputs/sprint-review-[DATE].pptx

Present the file to the user with a brief summary of what's included.

---

Content Handling Rules

1. Bug items: If item starts with Bug '...' or Bug:, treat as bug fix. Use "Fixed" or the supplied status.
2. Notable items: If marked with ★ or "Notable", add a star icon or highlight treatment.
3. Demo Ready: If marked "Demo Ready", add a badge or callout.
4. Grouped sub-items: If multiple sub-items belong to one parent, list them as bullet points under the parent title.
5. Long descriptions: Wrap to 2 lines max; truncate gracefully if needed — never overflow the text box.
6. Empty groups: If a feature group has no items, skip its slide.
7. Unknown status: Default to "In Progress".

---

PMP Framing

As a PMP-certified PM, use professional language:

• "Delivered" not "done"
• "Resolved" not "fixed"
• "In active development" not "in progress"
• Bug fixes slide title → "Bug Fixes & Resolutions"
• Summarize the sprint with total deliverables count

---

Example Invocation

Input:

MCTV:
* App Cache Limit — Done
* E2E Testing — In Progress

Door Sign:
* Bug 'Location fields incorrectly displayed' — Fixed
* Bug 'Code status doesn't change' — Fixed

Output: 4-slide deck:

1. Title slide with MCTV + Door Sign pills
2. MCTV slide with 2 items
3. Door Sign slide with 2 bug fixes
4. Summary: 2 MCTV · 2 Door Sign = 4 total