Sprint Planning Pipeline
Project Manager Official v1.1.29End-to-end sprint planning from backlog to committed plan
by skrptiq
Sign in to import this skrpt into your workspace.
Sign inWhat's included 8 nodes
Sprint Planning Pipeline
End-to-end sprint planning from backlog to committed plan
Capacity Planner
Calculating available team capacity for a sprint from the roster, accounting for leave, meetings, and other commitments
Sprint Plan Generator
Assembling the committed sprint plan from the refined backlog, capacity, resource allocation, and risk assessment
Sprint Planning
Breaks epics into sprintable user stories with acceptance criteria
Capacity Planner
Task prompt for calculating team sprint capacity
Plan Sprint
Core prompt for sprint planning and backlog prioritization
Sprint Plan Generator
Task prompt for generating a structured sprint plan
Scrum Guide
Reference material for Scrum framework practices and ceremonies
Requirements 2 services
- LLM Service
- Jira Cloud
Security Passed
Detected
- Services: llm-service
- Permissions:
- Data Handling:
Version history 19 releases
GH#863 Wave 1 (#858-A1 class) — fix the intent/output mismatch (K-045): the bundle shipped the `sprint-plan-generator` and `capacity-planner` prompts and the docs said to run them, but the `execution:` block never invoked either — so the workflow's real deliverable (the committed sprint plan) and the capacity summary were never produced. Wired both as execution steps in dependency order with backing skills so they are `from_step`-addressable: added a **Capacity Planner** step (skill `capacity-planning`) after backlog refinement, and a **Sprint Plan Generator** step (skill `sprint-plan-generation`) as the last content step before language-polish. Rewired the generator's cross-step inputs to an explicit `from_step`-bound graph via named `context_params` (`{{step.context.*}}`): refined backlog ← Sprint Planning, team capacity ← Capacity Planner, resource allocation ← Resource Allocation, risk assessment ← Risk Assessment — replacing the old positional/title refs (`{{steps.previous.output}}`, `{{steps.Resource Allocation.output}}`). Completed the tail: repinned `polish-language` 1.0.1→1.0.6 (the version exposing the bindable `source` slot) and bound `language-polish`'s `source` ← the Sprint Plan Generator, so the `output_step` polishes the actual committed sprint plan rather than its positional previous. Manifest: +2 skills (skills 1→3, total 6→8). No new required inputs.
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#753 — supply allocate-resources via `bindings: sprint_plan { from_step: "Sprint Planning" }` and re-pin the dep to v1.0.3 (position-safe). Restores the resolved reference after the shared-prompt fix; no behaviour change. Canonical scan clean.
GH#645 Row 3b — migrate to K-037 dep-referenced schema. Strip 11 inline shared-content files and declare 11 hub-shared deps (UUID id + slug name + version + checksum from `gen-dep-checksums.mjs`). Internal slug references rewritten for E2 rename/mirror-drop pair(s): sprint-ceremony-playbook→planning-playbook. Closes pre-Step-3 inline-vendoring for this bundle.
Wave 2: re-signed with canonical engine signing pipeline.
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.
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 →Jira Ticket Triage
Pulls Jira tickets via MCP, categorizes by status and priority, and generates a triage report or sprint summary
Risk Review Process
Identifies risks, scores them, and produces a register update
Sprint Summary Pipeline
Pulls sprint tickets from Linear via MCP, analyzes velocity and status, and generates a stakeholder-ready sprint report