Sprint Summary Pipeline
Project Manager Official v1.0.16Pulls sprint tickets from Linear via MCP, analyzes velocity and status, and generates a stakeholder-ready sprint report
by skrptiq
Sign in to import this skrpt into your workspace.
Sign inWhat's included 8 nodes
Sprint Summary Pipeline
Fetches sprint tickets from Linear via MCP, analyzes status and velocity, and generates a stakeholder-ready report
Status Categorization
Groups sprint tickets by status — done, in progress, blocked, canceled, and carried over
Velocity Analysis
Computes sprint velocity — points completed vs planned, completion rate, and trends
Analyze Velocity
Computes sprint velocity metrics and trend analysis
Categorize Status
Groups sprint tickets by status, assignee, or label
Fetch Tickets
Retrieves and structures sprint tickets from Linear via MCP
Synthesize Report
Combines status breakdown and velocity into a stakeholder-ready sprint report
Linear MCP
Linear MCP server for reading sprint cycles, issues, and project data
Requirements 2 services, 1 permission
- LLM Service
- linear-mcp
- network:api.linear.app
Security Passed
Detected
- Services: llm-service
- Permissions:
- Data Handling:
Version history 12 releases
GH#845 — republish with American English (en-US) content, completing the source-only GH#805 flip that never reached the Hub. Copy only — no functional or behaviour change.
GH#745 — declare per-step `output: {name, type}` on every execution step (tickets/text, status_breakdown/text, velocity_metrics/text, sprint_report/text, polished_report/text). Lights up the #744 rich flow-map. Content-only. (Completes the #745 sweep for this skrpt after the #754 error fix.)
Fix-forward after Row 3b v1.0.12 publish failure. The v1.0.12 per-skrpt CI's "Register version with Hub API" step failed because the consumer's source `manifest.id` (83273727…) did not match the D1 catalogue row's id (ad284026…) — a legacy drift from before Action 6 (`0bcc5ae0`) made publish-skrpt.mjs Step 2 INSERT use `manifest.id` for the D1 id column. v1.0.13 reconciles the source `manifest.id` to the catalogue authoritative value (Row-5-equivalent for consumers) and republishes. Per Adj-1: no re-tag of v1.0.12; the orphaned GitHub release artefact stays inert (no D1 versions row, no consumer pinned it).
Signature fix — RELEASE_NOTES.md now included in integrity checksum.
Initial catalogue release with full structural and content-quality validation. All scanner checks pass.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
More from Project Manager
View all →Sprint Planning Pipeline
End-to-end sprint planning from backlog to committed plan
Roadmap Update Flow
Revises roadmap based on velocity trends and priority changes
Jira Ticket Triage
Pulls Jira tickets via MCP, categorizes by status and priority, and generates a triage report or sprint summary