---

name: yepai-pm-prioritize description: >- Prioritization and tradeoff specialist for competing ideas, roadmap conflicts, resource constraints, and sequencing decisions. Use when the user must choose what to do now, what to defer, and how to justify the ranking. metadata: {"openclaw":{"emoji":"⚖️"}} license: MIT-0

YepAI PM Prioritize

Use this skill when the user is choosing among too many valid options.

Use Cases

• backlog or initiative ranking
• roadmap conflict resolution
• "what should we do first?"
• limited engineering capacity
• tradeoff decisions across teams
• "what do we cut?"

Core Rule

Prioritization is not listing everything that matters. It is making an explicit choice under constraint.

Prioritization Workflow

1. Frame the decision

Clarify:

• options being compared
• decision horizon
• available resources
• success criteria
• hard constraints

2. Choose the right prioritization lens

Use a fitting lens, such as:

• impact vs effort
• RICE-style comparison
• strategic fit
• risk reduction
• time sensitivity
• dependency unlock

Do not force a framework that does not match the decision.

3. Score or rank the options

For each option, assess:

• user impact
• business impact
• effort / complexity
• strategic fit
• urgency / timing
• risk / uncertainty

4. Make the tradeoff explicit

State:

• what is recommended now
• what is deferred
• what is rejected
• why that tradeoff is rational

5. Define revisit conditions

A good prioritization decision should say when it changes.

Output Format

Prefer this structure:

## Decision Frame
## Options Considered
## Ranking Logic
## Recommended Priority Order
## Tradeoffs / What Not To Do Now
## Risks / Assumptions
## Revisit Conditions
## Recommended Next Step

Quality Rules

• Rank the options clearly
• Explain why the top option wins
• Make "not now" visible
• Avoid fake precision if inputs are weak
• If data is missing, state the provisional basis for the decision
• Always leave the user with a concrete next step