Score and rank features using RICE, ICE, or weighted scoring with clear documentation.
/prioritization-engine4-6 hrs → 45 min
Compared to doing it manually
/prioritization-engineType this in Claude to run the skill
Prioritization is political. Without a framework, the loudest voice or highest-paid person's opinion wins. Data gets cherry-picked to justify predetermined conclusions.
/welcome/prioritization-engine in Claude to run the skill/strategic-roadmap-reviewA facilitated thinking exercise: look back at what happened, then look forward to set strategic direction — before building the tactical roadmap.
/north-star-finderIdentify and validate your product's North Star metric with supporting input metrics.
/go-to-market-strategyCreates a complete GTM plan with channels, messaging, timeline, and success metrics
/value-proposition-canvasCreates a Value Proposition Canvas mapping customer needs to product value
There's no single best framework — it depends on context. RICE for data-driven decisions, MoSCoW for stakeholder alignment, ICE for quick estimates. The best framework is one your team will actually use.
Force-rank ruthlessly. Use constraints: "If you could only ship one thing this quarter, what would it be?" Stack rank, don't tier. If you have 10 P1s, you have no P1s.
Get all 70 skills running in a system that knows your company, product, and customers.
All 70 skills + your company context in one system.