Notre avis

Ordonne les éléments du backlog en utilisant les frameworks RICE, MoSCoW ou Value-Effort pour prioriser.

Points forts

Frameworks structurés et éprouvés (RICE, MoSCoW, Value-Effort)
Ordre de priorité basé sur des données quantitatives
Mise à jour automatique des fichiers PBI avec le champ de priorité
Tableau ordonné avec scores pour une communication claire

Limites

Nécessite des estimations précises de portée, impact et effort
Ne prend pas en compte les facteurs subjectifs ou politiques
Peut être chronophage pour de très grands backlogs

Quand l'utiliser

Utilisez cette compétence lors de la planification de sprint ou du classement des fonctionnalités pour le roadmap.

Quand l'éviter

Évitez de l'utiliser pour des décisions stratégiques complexes qui nécessitent un jugement humain approfondi.

name: prioritize description: Order backlog items using RICE, MoSCoW, or Value-Effort frameworks. Use when prioritizing backlog, ranking features, or ordering work items. Triggers on keywords like "prioritize", "RICE score", "MoSCoW", "rank backlog", "order by value". infer: true allowed-tools: Read, Write, Edit, Grep, Glob, TodoWrite

Backlog Prioritization

Order backlog items using data-driven prioritization frameworks.

When to Use

Sprint planning needs ordered backlog
Stakeholder requests priority ranking
Feature roadmap ordering

Pre-Workflow

Activate Skills

Activate product-owner skill for prioritization frameworks (RICE, MoSCoW, Value/Effort)

Quick Reference

Frameworks

RICE Score

Score = (Reach x Impact x Confidence) / Effort

Reach: Users affected per quarter
Impact: 0.25 | 0.5 | 1 | 2 | 3
Confidence: 0.5 | 0.8 | 1.0
Effort: Person-months

MoSCoW

Must Have: Critical, non-negotiable (release blocker)
Should Have: Important, not vital
Could Have: Nice to have
Won't Have: Out of scope (not this release)

Value vs Effort

High Value + Low Effort = Quick Wins (do first)
High Value + High Effort = Strategic (plan carefully)
Low Value + Low Effort = Fill-ins (if time permits)
Low Value + High Effort = Time sinks (avoid)

Workflow

Read PBIs from team-artifacts/pbis/
Filter by scope if specified; exclude done/rejected items
Apply selected framework
Sort by score/classification; assign numeric priority (1 = highest)
Update PBI frontmatter priority
Output ordered list with scores

Output

Priority field: Numeric 1-999 (not High/Med/Low)
Console: Ordered table with scores

Report Template

## Backlog Priority - {Date}

**Framework:** {framework}
**Scope:** {scope}

| Rank | PBI     | Score   | Rationale |
| ---- | ------- | ------- | --------- |
| 1    | {title} | {score} | {why}     |

Role Skill: product-owner
Command: /prioritize

Example

/prioritize rice
/prioritize moscow scope:sprint

IMPORTANT Task Planning Notes

Always plan and break many small todo tasks
Always add a final review todo task to review the works done at the end to find any fix or enhancement needed

Priorisation du Backlog

Recommandé pour