Game-Changing Features
Product skill, available on Zeplik
Game-Changing Features is a ready-to-run product management skill on Zeplik. Stack-ranked 10x opportunity analysis across massive/medium/small bets. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer. It returns a structured document you can keep and reuse: 10x analysis -- current value, opportunities (massive/medium/small) scored, stack-ranked priority (now/next/explore/backlog).
The Game-Changing Features skill loads automatically when your request matches it, or you can invoke it directly by typing /game-changing-features in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.
What the Game-Changing Features skill can do
- Analyzes current product value before proposing new bets
- Generates 10x opportunities across massive, medium, and small effort scales
- Scores each idea on impact, reach, differentiation, defensibility, and feasibility
- Stack ranks opportunities into Do Now, Do Next, Explore, and Backlog
Try these prompts on Zeplik
Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.
How the Game-Changing Features skill works
Game-Changing Features (10x Mode)
Product strategist with founder mentality. Not here to add features -- here to find the moves that 10x the product's value. Think like an owner: what would make users unable to live without it?
This is pure strategy, not implementation. The question is not "10% better" or "nice to have" -- it's "how did I live without this?"
Session Setup
User provides:
- Product/Area -- what we're thinking about
- Current state (optional) -- what exists today
- Constraints (optional) -- technical limits, timeline, team size
Workflow
Step 1: Understand Current Value
Before proposing additions: What problem does this solve today? Who uses it and why? What's the core action? Where do users spend most time? What do they complain about or request most? Research the product's actual shape.
Step 2: Find 10x Opportunities at Three Scales
Massive (high effort, transformative) -- Fundamentally expand what the product can do. What adjacent problem would make this indispensable? What turns it from a tool into a platform? What makes users bring their team? What makes competitors nervous?
Medium (moderate effort, high leverage) -- Force multipliers on what works. What makes the core action 10x faster/easier? What data are we not using? What painful workflow could we automate? What turns casual users into power users?
Small (low effort, disproportionate value) -- Tiny changes that punch above their weight. What one button/shortcut saves minutes daily? What info are users hunting for? What anxiety could one indicator eliminate? What manual step could we remember for them?
Step 3: Evaluate Ruthlessly
| Criteria | Question |
|---|---|
| Impact | How much more valuable does this make the product? |
| Reach | What % of users would this affect? |
| Frequency | How often would users encounter this value? |
| Differentiation | Does this set us apart or just match competitors? |
| Defensibility | Easy to copy, or does it compound over time? |
| Feasibility | Can we actually build this? |
Score each: š„ must do, š strong, š¤ maybe, ā pass.
Step 4: Identify Highest-Leverage Moves
Look for quick wins with outsized impact, strategic bets that open new possibilities, and compounding features (network/data/habit effects that build moats).
Step 5: Prioritize
Stack rank, don't just list: Do Now (quick wins), Do Next (high leverage), Explore (strategic bets, note risk + upside), Backlog (good but not now).
Idea Categories to Force Through
| Category | Question |
|---|---|
| Speed | What takes too long? |
| Automation | What's repetitive? |
| Intelligence | What could be smarter? |
| Integration | What else do users use? |
| Collaboration | How do users work together? |
| Personalization | How is everyone different? |
| Visibility | What's hidden that shouldn't be? |
| Confidence | What creates anxiety? |
| Delight | What could spark joy? |
| Access | Who can't use this yet? |
Rules
- Think big first -- don't self-censor; capture, then evaluate.
- Small can be huge -- one button can change everything.
- User value, not feature count -- 10 features at 1% each ā one at 10x.
- Be specific -- "better UX" is not an idea; "one-click reschedule from notification" is.
- Question assumptions -- what users say they want may be wrong.
- Compound thinking -- prefer features that improve over time.
- No safe ideas -- if every idea is obviously good, think harder.
- Cite evidence -- reference what you saw in the product or research.
Unstick Prompts
If stuck: What would make a user tell a friend? What daily annoyance persists? What would we build with 10x the team? 1/10th? What must a competitor build to beat us? What do power users do manually? What insight from data do users never see?
Output
Produce a 10x analysis document: current value, the core question, opportunities grouped as Massive / Medium / Small Gems (each with what, why 10x, effort, risk, and score), followed by a stack-ranked recommended priority (Do Now / Do Next / Explore / Backlog) and open questions plus next steps.
How to use the Game-Changing Features skill
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the Game-Changing Features skill right away.
Describe your product management task
Ask in plain language, or type /game-changing-features to invoke the skill directly. Zeplik recognizes the Game-Changing Features skill and applies its method.
Review and refine the result
Zeplik returns a structured document you can edit, download, and reuse. Ask follow-ups to refine it.
Source and credit
- Author
- davila7 community
- License
- MIT
Adapted from the open-source davila7/claude-code-templates project and tuned to run natively on Zeplik. View source on GitHub.
Frequently asked questions
- What is the Game-Changing Features skill?
- Game-Changing Features is a ready-to-run product management skill on Zeplik. Stack-ranked 10x opportunity analysis across massive/medium/small bets. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer. It returns a structured document you can keep and reuse: 10x analysis -- current value, opportunities (massive/medium/small) scored, stack-ranked priority (now/next/explore/backlog).
- How do I use Game-Changing Features on Zeplik?
- Sign in to Zeplik and ask in plain language, or type /game-changing-features in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.
- Which AI model does the Game-Changing Features skill use?
- Any model you choose. Zeplik works across every model in one chat, so the Game-Changing Features skill runs on your preferred model for the task.
- Where does the Game-Changing Features skill come from?
- The Game-Changing Features skill is adapted from the open-source davila7/claude-code-templates project (MIT) and tuned to run natively on Zeplik. The original source is linked on this page.
- How much does the Game-Changing Features skill cost?
- Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.
Related product skills
- Agile Product OwnerUse when writing INVEST user stories, acceptance criteria, or grooming and prioritizing a product backlog. Not for sprint ceremony planning (use sprint-planning).
- AI Product BuilderUse when building a paid product that wraps AI APIs: architecture, prompts as product, cost metering, differentiation. Not for calling the Anthropic API in code (use claude-api).
- AI Product DevelopmentIntegration, safety and cost guidance for building or hardening a production LLM feature. Not for a thin one-API SaaS (use ai-wrapper-product).
- Idea to SpecTurn a rough product idea into build-ready documents through staged gates: a clarifying interview in chat, then a design doc artifact, an optional UI brief, and an implementation plan. Use when the user has an app or feature idea and wants it captured, shaped, and specified before any code. Not for tasks that already have a clear spec (use plan or execplan) or for pure research questions.
- Pre-Build Risk ReviewUse for a pre-build risk review of demand, positioning, monetization, retention, distribution before committing to build. Not for turning an idea into a full spec (use idea-to-spec).
- Product Brainstorm PartnerUse as a product thinking partner -- exploring a new opportunity, generating solutions to a product problem, stress-testing an idea, challenging assumptions before converging on a direction. Not for exploring a code or feature design (use brainstorming) or writing the spec (use write-spec).
More on Zeplik
Try Game-Changing Features on Zeplik
Every model, one chat. Bring the Game-Changing Features skill into your next conversation and let the assistant do the work.