Claude Code Product Opportunities Skill for Prioritizing Features

Compare feature ideas by the user problem they address, how often it occurs and how feasible the proposed change is.

Install in Claude Code

Bring a product scenario, an existing user task and any supporting observations. Label assumptions that need a test.

Get the complete `cli-tool/components/skills/productivity/game-changing-features` directory from the pinned GitHub checkout.
Copy it under the target project's `.claude/skills/`. Confirm `.claude/skills/game-changing-features/SKILL.md`, open Claude Code at the project root, and call `/game-changing-features`.

Example task

Readers repeatedly add the same books. Compare bulk import, recently used books and manual entry defaults, then choose what to prototype first.

What to check

The comparison explains its priorities and names a user task or measure that the first prototype should improve. The source skill writes the analysis under .claude/docs/ai/<area>/10x/session-N.md.

Original SKILL.md on GitHub · Updated 2026-11-13

Frequently asked question

Can estimated impact stand in for measured impact?

Treat estimates as hypotheses and update them after observing representative users or task data.