prod-prioritization-planner

Prioritize backlog stories by MVP value, dependencies, blockers, and delivery risk.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill prod-prioritization-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prod-prioritization-planner
Source: https://github.com/FernanSuoza/AIDD-project-bootstrap/tree/main/templates/skills/prod-prioritization-planner
Command: npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill prod-prioritization-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prioritize approved features and stories around MVP value, dependencies, blockers, and delivery risk.

Core Features & Use Cases

  • Prioritization plan aligned to MVP value and risk
  • Dependency and blocker mapping to reveal critical path
  • Produce a prioritized backlog and an MVP split for planning

Quick Start

Prioritize the current backlog by MVP value, dependencies, and blockers to produce a ranked plan.

Frequently Asked Questions about prod-prioritization-planner

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

FAQPage Schema
How do I prioritize a backlog by MVP value, dependencies, and delivery risk?

You can prioritize a backlog by evaluating each story's MVP value, mapping dependencies to identify blockers, and ranking items by delivery risk. This produces a prioritized plan with an MVP split and a blocked or unblocked delivery order.

What is the best way to sequence sprint features when blockers and dependencies drive delivery order?

Sequencing sprint features by dependencies requires mapping blockers to reveal the critical path before ranking work by MVP value and risk. This generates an unblocked delivery order that aligns feature organization with actual project constraints.

How do I split a backlog into an MVP and future batches based on risk and dependencies?

Splitting a backlog into an MVP involves ranking approved stories by feature value and delivery risk, then mapping dependencies to isolate blockers. The output is a prioritized MVP split followed by sequenced batches of unblocked work.

Can I apply backlog prioritization to projects where dependencies and risk drive the delivery order?

Backlog prioritization applies directly to projects driven by dependencies and risk by mapping blockers to establish the critical path. It ranks stories around MVP value to produce a sequenced plan tailored to those specific project constraints.

What inputs do I need to generate a prioritized plan with an MVP split and critical path mapping?

Generating a prioritized plan requires backlog stories as the primary input, along with optional project constraints. The tool processes these to map dependencies, assess delivery risk, and output a ranked MVP split and blocked delivery order.