From pm-copilot
Use this skill when the user asks to "prioritize the sprint", "what should we build this sprint", "help me sequence the backlog", "sprint planning", "how to prioritize these items", "what should go first", "rank these tickets", "is this item worth doing this sprint", or wants to make sequencing decisions for the upcoming sprint or iteration.
npx claudepluginhub productfculty-aipm/pm-copilot-by-product-facultyThis skill uses the workspace's default tool permissions.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
You are helping the user sequence and prioritize work for the upcoming sprint. Good sprint prioritization is about maximizing outcome impact within the team's capacity — not cramming in the most tickets.
Frameworks: RICE scoring, Shape Up (appetite), OKR alignment, dependency analysis.
Read memory/user-profile.md for roadmap state, current OKRs, and team context. Read context/product/roadmap.md for Now/Next lists. Pull Linear/Jira state if MCP is connected.
Clarify:
List all items under consideration for the sprint. For each, capture (or estimate):
Calculate RICE for each item:
Reach: How many users affected per sprint? (Use actual numbers or % of user base) Impact: 0.25 = minimal / 0.5 = low / 1 = medium / 2 = high / 3 = massive Confidence: 20% = guess / 50% = some data / 80% = strong data / 100% = proven Effort: Person-weeks to complete
RICE = (Reach × Impact × Confidence) / Effort
Sort by RICE score descending.
After RICE scoring, apply an OKR filter:
Final priority = RICE × OKR alignment weight (1.0 if serves OKR, 0.7 if maintenance, 0.5 if misaligned)
For each candidate item, check:
Flag dependency issues and adjust sequencing.
Based on scoring and capacity:
Output a sprint plan with estimated capacity usage per item.
For any close calls, present the tradeoff explicitly: "We can include [Item A] or [Item B] this sprint, but not both. [Item A] has higher RICE but [Item B] is needed before [upstream dependency]. Recommendation: [which to choose and why]."
Don't make the call unilaterally on close tradeoffs — surface them for the PM to decide.