product-prioritization

Rank features by evidence-driven scoring and forcing questions.

1|Updated May 11, 2026
One-click install
npx skills add https://github.com/zeropoint-foundation/ironclaw --skill product-prioritization-zeropoint-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-prioritization
Source: https://github.com/zeropoint-foundation/ironclaw/tree/main/skills/product-prioritization
Command: npx skills add https://github.com/zeropoint-foundation/ironclaw --skill product-prioritization-zeropoint-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prioritizing features based on opinions or gut feel leads to biased roadmaps and wasted effort. This skill helps teams surface real user demand and objective criteria to decide what to build next.

Core Features & Use Cases

  • Evidence-driven scoring: evaluates demand, impact, effort, and alignment to rank features.
  • Forcing questions: prompts to ensure concrete user needs and MVP criteria are identified.
  • Roadmap prioritization: aids quarterly planning, sprint planning, and backlog grooming with transparent rationale.
  • Use Case: during a roadmap session, feed in backlog items and create a prioritized list with rationale and next steps.

Quick Start

Provide a prioritized feature list based on user demand and effort estimates from your backlog data.

Frequently Asked Questions about product-prioritization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize my product backlog using evidence instead of opinions?

You prioritize your backlog by applying a structured scoring framework that evaluates user demand, impact, effort, and alignment. This approach surfaces real user signals to rank features, replacing gut feel with objective criteria.

What is evidence-driven feature scoring in product management?

Evidence-driven feature scoring is a prioritization method that ranks backlog items using real user demand and effort estimates. It enforces structured scoring and forcing questions to ensure robust, unbiased roadmapping decisions.

Can I use this framework for quarterly roadmap planning and sprint grooming?

Yes, you can use this framework for quarterly roadmap planning, sprint planning, and backlog grooming. It generates a transparent rationale for each prioritized feature, ensuring strategy sessions rely on concrete user needs.

How do forcing questions improve backlog prioritization decisions?

Forcing questions improve backlog prioritization by prompting teams to identify concrete user needs and MVP criteria before scoring. This ensures every feature ranked in the roadmap has a validated basis in real user demand.

What is the best way to rank features for a product roadmap session?

The best way to rank features is feeding backlog items into a structured scoring framework that evaluates demand, impact, effort, and alignment. This outputs a prioritized feature list with clear rationale and next steps.

When should I not use opinion-based feature prioritization for my roadmap?

You should avoid opinion-based prioritization when it risks creating biased roadmaps and wasting development effort. Switch to an evidence-driven scoring method to ensure backlog items reflect actual user demand and objective impact criteria.