一键在 Manus 中运行任何 Skill

product-strategy

Find high-leverage product opportunities. Use when the user wants product strategy, asks what would make something 10x better, or wants to decide what to build next.

在 Manus 中运行

星标0

分支0

更新时间2026年6月8日 09:01

来源

MuhammedAlkhudiry

MuhammedAlkhudiry/my-setup

打开 GitHub 仓库查看创作者相关仓库

安装命令

下载

在 Manus 中运行

SKILL.md

readonly

name	product-strategy
description	Find high-leverage product opportunities. Use when the user wants product strategy, asks what would make something 10x better, or wants to decide what to build next.

Product Strategy

Find product moves that materially change value, not just feature count.

Workflow

Understand the product’s current value, users, and main workflows.
Inspect product context so recommendations reflect reality.
Generate opportunities from user pain, constraint removal, opposite bets, competitor pressure, and tiny proof moves.
Organize the strongest opportunities at three levels:
- Massive: transformative bets
- Medium: strong leverage on the core workflow
- Small: low-effort changes with outsized value
Score by impact, reach, frequency, differentiation, defensibility, and feasibility.
Stack-rank into Do now, Do next, Explore, and Backlog.

Output

Structure the response as:

Current value
Massive opportunities
Medium opportunities
Small gems
Recommended priority
Questions
Recommended action

Rules

Prefer a few sharp ideas over a long feature list.
Include a credible "not now" or "do not build" path when warranted.
Flag attractive traps: ideas that are novel but weak on adoption, proof, timing, or fit.
Tie each recommendation to user value, not novelty.
Cite evidence from product context or research when it influenced the ranking.

同仓库更多 Skills

同仓库

bug-learning

MuhammedAlkhudiry/my-setup

Use after fixing or investigating a hard-earned bug that took significant debugging, crossed multiple files or systems, had misleading symptoms, or revealed durable system behavior worth preserving in docs/knowledge/learnings.

2026-06-080

dependency-upgrade

MuhammedAlkhudiry/my-setup

Systematically upgrade project dependencies. Use for Composer, npm, bun, pnpm, yarn, lockfile updates, security updates, Laravel/PHP upgrades, React/JavaScript upgrades, framework bumps, package modernization, or dependency cleanup.

2026-06-080

project-knowledge

MuhammedAlkhudiry/my-setup

Use when answering questions about a project feature, documenting existing functionality, investigating product behavior, or maintaining docs/knowledge feature packs, glossary terms, aliases, key files, and feature history.

2026-06-080

workshop

MuhammedAlkhudiry/my-setup

Stress-test and challenge ideas before building. Use when the user wants to think through code architecture, UX/UI, or product direction before implementation.

2026-06-080

check-and-fix

MuhammedAlkhudiry/my-setup

Run project checks from repo-root `CHECKLIST.md` and fix task-related failures, including skipped tests. Use when the user asks to run checks, lint and fix, or verify code quality.

2026-06-080

planning

MuhammedAlkhudiry/my-setup

Create, review, refine, or execute conversational plans before implementation. Use when the user asks for a plan, implementation plan, roadmap, task breakdown, sequence, scope, phases, or multi-step work. For uncertain architecture, product, UX, or pre-implementation direction, apply the workshop skill first.

2026-06-080

name	product-strategy
description	Find high-leverage product opportunities. Use when the user wants product strategy, asks what would make something 10x better, or wants to decide what to build next.

Product Strategy

Find product moves that materially change value, not just feature count.

Workflow

Understand the product’s current value, users, and main workflows.
Inspect product context so recommendations reflect reality.
Generate opportunities from user pain, constraint removal, opposite bets, competitor pressure, and tiny proof moves.
Organize the strongest opportunities at three levels:
- Massive: transformative bets
- Medium: strong leverage on the core workflow
- Small: low-effort changes with outsized value
Score by impact, reach, frequency, differentiation, defensibility, and feasibility.
Stack-rank into Do now, Do next, Explore, and Backlog.

Output

Structure the response as:

Current value
Massive opportunities
Medium opportunities
Small gems
Recommended priority
Questions
Recommended action

Rules

Prefer a few sharp ideas over a long feature list.
Include a credible "not now" or "do not build" path when warranted.
Flag attractive traps: ideas that are novel but weak on adoption, proof, timing, or fit.
Tie each recommendation to user value, not novelty.
Cite evidence from product context or research when it influenced the ranking.