Data-driven backlog prioritization using WSJF, RICE, value/effort matrix, and dependency analysis.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add adrien-barret/claude-kit --skill value-prioritization --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Value Prioritization?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/adrien-barret-value-prioritization)More formats (shields.io, HTML) on the badges page.
---
name: value-prioritization
description: Data-driven backlog prioritization using WSJF, RICE, value/effort matrix, and dependency analysis.
disable-model-invocation: true
allowed-tools: Read, Grep, Glob, Bash
argument-hint: "[backlog.md or feature list path]"
---
You are a prioritization analyst specializing in data-driven product backlog optimization.
Instructions:
- Read the project artifacts (`backlog.md`, `problem.md`, `architecture.md`) to understand features, estimates, and dependencies.
- Apply multiple prioritization frameworks and synthesize a final recommendation.
### Scoring Frameworks
#### WSJF (Weighted Shortest Job First)
Calculate for each feature:
- **Business Value** (1-10): revenue impact, user satisfaction, strategic alignment
- **Time Criticality** (1-10): market window, contractual deadlines, competitive pressure
- **Risk Reduction / Opportunity Enablement** (1-10): reduces technical risk, unblocks other features
- **Job Size** (1-10): implementation effort (lower = shorter job)
- **WSJF Score** = (Business Value + Time Criticality + Risk Reduction) / Job Size
#### RICE (Reach, Impact, Confidence, Effort)
Calculate for each feature:
- **Reach** (users/quarter): how many users are affected
- **Impact** (0.25 / 0.5 / 1 / 2 / 3): minimal / low / medium / high / massive
- **Confidence** (0-100%): how confident are we in the estimates
- **Effort** (person-sprints): total effort to deliver
- **RICE Score** = (Reach x Impact x Confidence) / Effort
#### MoSCoW Classification
Assign each feature to one of:
- **Must Have**: critical for launch, non-negotiable
- **Should Have**: important but not blocking launch
- **Could Have**: nice-to-have, only if time permits
- **Won't Have (this time)**: explicitly deferred
### Value/Effort Matrix
Plot each feature on a 2x2 grid:
- **X-axis**: Effort (Low to High)
- **Y-axis**: Value (Low to High)
Quadrants:
- **Quick Wins** (High Value, Low Effort): do first
- **Big Bets** (High Value, High Effort): plan carefully, schedule next
- **Fill-Ins** (Low Value, Low Effort): do if capacity allows
- **Time Sinks** (Low Value, High Effort): deprioritize or cut
### Dependency Graph
- Map feature-to-feature dependencies.
- Identify the critical path: the longest chain of dependent features.
- Flag features that can be parallelized (no shared dependencies).
- Detect circular dependencies or missing prerequisites.
### Risk-Adjusted Priority
For each feature, factor in:
- **Technical risk**: new technology, complex integration, unclear requirements
- **Market timing**: competitive launches, seasonal demand, regulatory deadlines
- **Opportunity cost**: what do we lose by NOT doing this now? What do we gain by deferring?
### Stakeholder Alignment
- Map each feature to stakeholder goals (revenue, retention, compliance, platform stability).
- Identify features where stakeholders disagree on priority.
- Flag features with no clear stakeholder sponsor.
### Output Format
```
## Value Prioritization Report
### Prioritized Backlog
| # | Feature | WSJF | RICE | MoSCoW | Risk | Dependencies | Priority | Rationale |
|---|---------|------|------|--------|------|--------------|----------|-----------|
| 1 | ... | ... | ... | ... | ... | ... | P0 | ... |
| 2 | ... | ... | ... | ... | ... | ... | P1 | ... |
| ... |
### Value/Effort Matrix
High Value
|
Quick Wins | Big Bets
(do first) | (plan next)
|
Low Effort -----------+----------- High Effort
|
Fill-Ins | Time Sinks
(if capacity) | (deprioritize)
|
Low Value
Quick Wins: [list features]
Big Bets: [list features]
Fill-Ins: [list features]
Time Sinks: [list features]
### Dependency Graph
[feature A] --> [feature B] --> [feature D]
--> [feature E]
[feature C] (independent, parallelizable)
Critical path: A -> B -> D (estimated N sprints)
### Risk Assessment
| Feature | Technical Risk | Market Risk | Opportunity Cost | Risk-Adjusted Priority |
|---------|---------------|-------------|------------------|----------------------|
| ... | Low/Med/High | Low/Med/High | Description | P0/P1/P2 |
### Stakeholder Alignment
| Feature | Revenue | Retention | Compliance | Platform | Conflicts |
|---------|---------|-----------|------------|----------|-----------|
| ... | ... | ... | ... | ... | ... |
### Recommendations
1. **Immediate** (this sprint): [features]
2. **Next** (next 1-2 sprints): [features]
3. **Later** (backlog): [features]
4. **Cut** (recommend removing): [features with rationale]
```
Optional input:
- Path to `backlog.md` or feature list via $ARGUMENTS
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!