pm-sprint

Prioritize agile backlogs using RICE, MoSCoW, and Value vs. Effort frameworks.

2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/elihuvillaraus/skills --skill pm-sprint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-sprint
Source: https://github.com/elihuvillaraus/skills/tree/main/pm-sprint
Command: npx skills add https://github.com/elihuvillaraus/skills --skill pm-sprint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of effectively prioritizing features and managing sprint capacity to maximize team velocity and business value delivery in agile environments.

Core Features & Use Cases

  • Data-Driven Prioritization: Utilizes frameworks like RICE, MoSCoW, and Value vs. Effort to make objective prioritization decisions.
  • Agile Sprint Planning: Guides the entire sprint planning process from backlog refinement to task breakdown and commitment.
  • Capacity & Resource Management: Analyzes team velocity and allocates resources effectively to ensure predictable delivery.
  • Stakeholder Alignment: Facilitates clear communication and buy-in from stakeholders through data-driven reporting and negotiation.
  • Risk Management: Identifies and mitigates potential risks to sprint delivery.
  • Use Case: A product manager can use this Skill to prioritize a backlog of 50 user stories for the upcoming sprint, ensuring the most valuable features are tackled first while considering team capacity and dependencies.

Quick Start

Use the pm-sprint skill to prioritize the backlog for the next sprint using the RICE framework.

Frequently Asked Questions about pm-sprint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize a product backlog using the RICE framework for sprint planning?

Sprint planning prioritization applies frameworks like RICE, MoSCoW, and Value vs. Effort to objectively rank backlog items. This approach maximizes team velocity by ensuring high-impact user stories are addressed first while balancing available development capacity.

What is the best way to manage cross-team dependencies during agile sprint planning?

Agile sprint planning manages cross-team dependencies through multi-criteria decision analysis and risk assessment. Identifying these bottlenecks early ensures predictable delivery and prevents blockers from derailing team velocity during the execution phase.

How does data-driven resource allocation improve team velocity in scrum or kanban environments?

Data-driven resource allocation improves scrum and kanban team velocity by analyzing historical metrics to balance workloads effectively. This ensures development capacity matches sprint commitments, preventing overallocation and fostering consistent, predictable business value delivery.

Can I use product management prioritization frameworks for stakeholder alignment and reporting?

Product management prioritization frameworks facilitate stakeholder alignment by providing objective, data-driven rationales for feature decisions. This transparency streamlines reporting and negotiation, ensuring stakeholders understand why specific backlog items are prioritized over others.

When should I use MoSCoW versus Value vs. Effort for feature prioritization?

MoSCoW categorizes features into mandatory, should-have, could-have, and won't-have buckets, while Value vs. Effort plots items on a matrix to visualize impact against complexity. Both data-driven frameworks optimize sprint planning but suit different prioritization granularity needs.

How do I assess and mitigate delivery risks during agile sprint planning?

Agile sprint planning assesses delivery risks by identifying potential blockers and dependencies during backlog refinement. Mitigation strategies are then integrated into the resource allocation process to maintain predictable delivery and safeguard team velocity.