nicepkg/roadmap-prioritization-planning
Master prioritization frameworks, roadmap planning, timeline estimation, and resource allocation. Create executable roadmaps that drive focus and alignment.
npx skills add https://github.com/nicepkg/ai-workflow --skill roadmap-prioritization-planningMaster the art of saying "no". Create focused roadmaps that align your organization, drive strategic outcomes, and maximize impact with limited resources.
RICE Score = (Reach × Impact × Confidence) / Effort
Reach: How many users affected? (1-100+)
- 10+ = 10
- 100+ = 100
- 1000+ = 1000
Impact: Per-user impact (3, 2, 1, 0.5)
- 3 = Massive (10x improvement)
- 2 = High (significant improvement)
- 1 = Medium (noticeable improvement)
- 0.5 = Low (minor improvement)
Confidence: How confident? (0.25-1.0)
- 1.0 = High (research backed)
- 0.8 = Medium (some validation)
- 0.5 = Low (minimal validation)
- 0.25 = Very low (assumption)
Effort: Engineer-weeks needed (1-20+)
Feature Reach Impact Confidence Effort RICE Score
────────────────────────────────────────────────────────
User Onboarding 50 3 0.8 8 (50×3×0.8)/8 = 15.0
Dark Mode 200 1 0.9 4 (200×1×0.9)/4 = 45.0
API Limits 500 2 0.7 10 (500×2×0.7)/10 = 70.0
Performance Fix 1000 0.5 1.0 5 (1000×0.5×1)/5 = 100.0
Custom Fields 30 3 0.6 12 (30×3×0.6)/12 = 4.5
PRIORITIZE: Performance > API Limits > Dark Mode > Onboarding > Custom Fields
High (1.0) - Research-backed
Medium (0.8) - Some validation
Low (0.5) - Minimal validation
Very Low (0.25) - Pure assumption
Low Effort High Effort
High Value QUICK WINS STRATEGIC
(Do first) (Plan carefully)
Low Value FILL-INS AVOID
(If time) (Skip)
Quick Wins: High value, low effort
Strategic: High value, high effort
Fill-Ins: Low value, low effort
Avoid: Low value, high effort
Must Have (Non-negotiable for launch)
Should Have (Important but deferrable)
Could Have (Nice to have)
Won't Have (Explicitly out of scope)
Three feature categories:
Basic Factors (Threshold)
Performance Factors (Linear)
Delighters (Excitement)
Strategy: Must haves first, then performance, then delighters for differentiation
Structure:
Q1 2025: Initiative Theme
├─ Goal: Business outcome
├─ Key Features: 2-3 major features
├─ Success Metrics: How you measure
└─ Resource: Team size needed
Q2 2025: Initiative Theme
Q3 2025: Initiative Theme
Q4 2025: Initiative Theme
Timeline: Plan month before quarter starts
Week 1: Data Gathering
Week 2: Prioritization
Week 3: Planning
Week 4: Alignment & Launch
Monday: Planning
Daily: Standups
Friday: Retrospective
Team Size: 5 engineers
Sprint Length: 2 weeks
Typical Capacity: 40-50 story points
Planning Reality:
- 50% unplanned work (bugs, interrupts)
- 20% operational tasks
- 30% feature development
Result: 50 points × 30% = 15 points for features
→ Add MUST have items first
→ Fill remaining capacity with SHOULD/COULD
Engineering Team:
Product Manager:
Design Team:
Hard Dependency
Soft Dependency
Cross-Team Dependency
Common Risks:
Weekly: Sprint progress
Monthly: Quarterly progress vs plan
Quarterly: Full roadmap refresh
Annually: Strategic direction review
Triggers for Reprioritization:
| Hata | Olası Sebep | Çözüm |
|------|-------------|-------|
| Roadmap sürekli kayıyor | Unrealistic estimates | 30% buffer ekle |
| Priority debates | Unclear criteria | RICE workshop |
| Resource contention | Over-commitment | Capacity planning |
| Dependencies blocking | Late identification | Sprint 0 mapping |
[ ] RICE scoring consistent mi?
[ ] Capacity realistic mi? (20% buffer)
[ ] Dependencies mapped mi?
[ ] Stakeholder alignment var mı?
[ ] Risk mitigation planı var mı?
Master prioritization and create roadmaps that drive real outcomes!
Take nicepkg/roadmap-prioritization-planning from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.