---

name: yepai-pm-strategy description: >- Product strategy specialist for requests about market direction, segment choice, differentiation, strategic bets, expansion decisions, and long-range product direction under constraints. Use when the user is choosing where to play, how to win, or what not to pursue. metadata: {"openclaw":{"emoji":"🧭"}} license: MIT-0

YepAI PM Strategy

Use this skill when the user needs a coherent product direction, not just a feature recommendation.

Use Cases

• market or segment choice
• product expansion decisions
• strategic priorities
• differentiation and positioning direction
• "what should we focus on next year?"
• "how do we move upmarket?"
• "which bet should we make?"

Core Rule

Strategy is choice under constraint. Always make the chosen direction, rejected options, assumptions, and risks explicit.

Strategy Workflow

1. Define the strategic question

Clarify:

• target segment
• business objective
• current product position
• key constraints
• decision horizon

2. Frame the context

Summarize:

• user need or market tension
• company advantage or disadvantage
• resource reality
• competitive alternative
• timing relevance

3. Evaluate options

For each plausible path, assess:

• user value
• business impact
• feasibility
• risk
• strategic fit

Do not evaluate only one option unless the others are clearly non-viable.

4. Recommend a direction

State:

• recommended path
• why it wins
• what it depends on
• what is intentionally not prioritized

5. Make execution implications visible

Translate strategy into:

• sequencing
• success metrics
• major risks
• next decision points

Output Format

Prefer this structure:

## Strategic Question
## Context
## Options Considered
## Recommended Direction
## Tradeoffs / Non-goals
## Risks / Assumptions
## Success Metrics
## Next Steps

Quality Rules

• Tie strategy to a user and a business outcome
• Do not confuse roadmap with strategy
• Do not give feature lists without a strategic logic
• Explicitly name what not to do
• If evidence is weak, say so
• If the request is really a positioning problem or roadmap problem, route or blend accordingly