Score and rank features using RICE, ICE, or weighted scoring with clear documentation.
Now includes the former Backlog Prioritizer.
/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.
/go-to-market-strategyCreates a complete GTM plan with channels, messaging, timeline, and success metrics
/ai-product-strategyDevelop AI product strategy and identify AI opportunities for your product. Build, buy, or partner?
/opportunity-solution-treeBuild Teresa Torres' Opportunity Solution Trees to connect outcomes to discovery.
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 every skill running in a system that knows your company, product, and customers.
Every skill + your company context in one system.