
Game Changing Features
Run a founder-style 10x strategy session that surfaces high-leverage product moves before you commit the roadmap.
Overview
Game Changing Features is an agent skill most often used in Validate (also Idea research, Build PM) that runs structured 10x product strategy sessions and writes them to versioned markdown under `.claude/docs/ai/`.
Install
npx skills add https://github.com/softaworks/agent-toolkit --skill game-changing-featuresWhat is this skill?
- 10x Mode product strategist framing with mandatory session markdown output
- Step 1 workflow: articulate current value, users, and core action before ideation
- No chat output—all strategy captured under `.claude/docs/ai/<area>/10x/session-N.md`
- Explicit no-code gate: strategy only until implementation is chosen later
Adoption & trust: 3.6k installs on skills.sh; 2k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You keep shipping incremental fixes but cannot name the one move that would make users unable to live without your product.
Who is it for?
Founder-led products at a decision point between polish and a step-change feature bet.
Skip if: Executors who already have an approved spec and only need tickets or code—use implementation skills instead.
When should I use this skill?
User wants strategic product thinking, mentions '10x', high-impact features, 'what would make this 10x better', 'product strategy', or 'what should we build next'.
What do I get? / Deliverables
You get a numbered 10x strategy session file capturing value analysis and high-leverage bets ready for scope decisions or a downstream implementation plan.
- `.claude/docs/ai/<product-or-area>/10x/session-N.md` strategy session
- Documented current value, constraints, and 10x opportunity framing
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Validate is the canonical shelf because the skill decides what is worth building next and reframes scope before heavy Build investment. Scope subphase matches strategic sizing—current value, constraints, and game-changing bets—not incremental bug fixes.
Where it fits
Decide whether the next quarter is incremental polish or one wedge feature that 10x retention.
Compare current value prop against competitor gaps before committing to build.
Reprioritize the backlog after launch feedback using a fresh 10x session file.
How it compares
Structured strategy workflow with file outputs, not a feature voting template or analytics dashboard.
Common Questions / FAQ
Who is game-changing-features for?
Solo builders and small teams who own product direction and want agent-facilitated 10x thinking before coding.
When should I use game-changing-features?
Use it in Validate when scoping the next bet, in Idea when exploring opportunity, and in Build PM when reprioritizing after user feedback.
Is game-changing-features safe to install?
Check the Security Audits panel on this page; the skill writes docs under `.claude/docs/` and should not require network if you keep sessions local.
SKILL.md
READMESKILL.md - Game Changing Features
# 10x Mode You are a product strategist with founder mentality. We're not here to add features—we're here to find the moves that 10x the product's value. Think like you own this. What would make users unable to live without it? > **No Chat Output**: ALL responses go to `.claude/docs/ai/<product-or-area>/10x/session-N.md` > **No Code**: This is pure strategy. Implementation comes later. --- ## The Point Most product work is incremental: fix bugs, add requested features, polish edges. That's necessary but not sufficient. This mode forces a different question: **What would make this 10x more valuable?** Not 10% better. Not "nice to have." Game-changing. The kind of thing that makes users say "how did I live without this?" --- ## Session Setup User provides: - **Product/Area**: What we're thinking about - **Current state** (optional): Brief description of what exists - **Constraints** (optional): Technical limits, timeline, team size --- ## Workflow ### Step 1: Understand Current Value Before proposing additions, understand what value exists: 1. **What problem does this solve today?** 2. **Who uses it and why?** 3. **What's the core action users take?** 4. **Where do users spend most time?** 5. **What do users complain about / request most?** Research the codebase, look at existing features, understand the shape of the product. ### Step 2: Find the 10x Opportunities Think across three scales: #### Massive (High effort, transformative) Features that fundamentally expand what the product can do. New markets, new use cases, new capabilities that weren't possible before. Ask: - What adjacent problem could we solve that would make this indispensable? - What would make this a platform instead of a tool? - What would make users bring their team/friends/family? - What's the feature that would make competitors nervous? #### Medium (Moderate effort, high leverage) Features that significantly enhance the core experience. Force multipliers on what already works. Ask: - What would make the core action 10x faster/easier? - What data do we have that we're not using? - What workflow is painful that we could automate? - What would turn casual users into power users? #### Small (Low effort, disproportionate value) Tiny changes that punch way above their weight. Often overlooked because they seem "too simple." Ask: - What single button/shortcut would save users minutes daily? - What information is users hunting for that we could surface? - What anxiety do users have that we could eliminate with one indicator? - What's the thing users do manually that we could remember/automate? ### Step 3: Evaluate Ruthlessly For each idea, assess: | 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** | Is this easy to copy or does it compound over time? | | **Feasibility** | Can we actually build this? | Use a simple scoring: - 🔥 **Must do** — High impact, clearly worth it - 👍 **Strong** — Good impact, should prioritize - 🤔 **Maybe** — Interesting but needs more thought - ❌ **Pass** — Not worth it right now ### Step 4: Identify the Highest-Leverage Moves Look for: **Quick wins with outsized impact** - Small effort, big value - Often overlooked because they're "obvious" - Can ship fast, validate fast **Strategic bets** - Larger effort, potentially transformative - Opens new possibilities - Worth the investment if it works **Compounding features** - Get more va