agency-sprint-prioritizer

Prioritize agile sprint features using RICE, MoSCoW, and Kano models.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill agency-sprint-prioritizer-immamdouhaboammar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-sprint-prioritizer
Source: https://github.com/imMamdouhaboammar/kaku-chatgpt-harness/tree/main/.agents/skills/product-sprint-prioritizer
Command: npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill agency-sprint-prioritizer-immamdouhaboammar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the friction in agile teams caused by subjective feature prioritization, poor capacity planning, and misalignment between stakeholders and development velocity.

Core Features & Use Cases

  • Prioritization Frameworks: Apply RICE, MoSCoW, and Kano models to objectively rank features based on business value and effort.
  • Capacity & Risk Management: Analyze team velocity and identify bottlenecks to ensure predictable delivery and proactive risk mitigation.
  • Use Case: When a product team is overwhelmed by a massive backlog, use this skill to score features using the RICE framework and generate a prioritized roadmap that aligns with current team capacity.

Quick Start

Use the agency-sprint-prioritizer to analyze the current backlog and suggest a prioritized sprint plan based on the RICE framework.

Frequently Asked Questions about agency-sprint-prioritizer

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

FAQPage Schema
How do I prioritize a product backlog using RICE and MoSCoW frameworks?

Backlog prioritization applies RICE, MoSCoW, and Kano models to objectively rank user stories by scoring business value against effort estimates. This generates a data-driven roadmap aligned with current team capacity.

What's the best way to plan an agile sprint with cross-team dependencies?

Agile sprint planning resolves cross-team dependencies by analyzing team velocity and identifying bottlenecks to ensure predictable delivery. It requires structured input of user stories and effort estimates to forecast accurate delivery timelines.

How do I calculate capacity planning for agile teams to avoid bottlenecks?

Capacity planning for agile teams analyzes historical velocity to identify bottlenecks and mitigate risks proactively. It matches the prioritized backlog scope against available development capacity to ensure predictable delivery.

Do I need structured user stories and effort estimates for sprint planning?

Structured user stories and effort estimates are required inputs for sprint planning to generate actionable sprint goals. Business impact metrics are also necessary to drive data-driven prioritization frameworks like RICE.

When should I use data-driven prioritization over subjective feature ranking?

Data-driven prioritization should be used when subjective feature ranking causes stakeholder misalignment and poor capacity planning. It resolves this friction by applying objective frameworks to manage backlogs and forecast delivery timelines.