game-changing-features

Overview of game-changing-features skill

The game-changing-features skill is a product strategy workflow for finding 10x opportunities, not a feature brainstorming template. It is designed for founders, PMs, and product-minded builders who need sharper answers to questions like “what should we build next?”, “what would make this 10x better?”, or “which move could materially change adoption, retention, or defensibility?”

What game-changing-features actually does

Instead of generating a long wish list, game-changing-features pushes the agent to:

• understand the product’s current value first,
• look for transformative moves at different scales,
• evaluate ideas against concrete product criteria,
• and produce a ranked set of bets rather than scattered suggestions.

That makes it more useful for Requirements Planning than ordinary ideation prompts, especially when a team is deciding where to invest limited time.

Best-fit users and use cases

The game-changing-features skill fits best when you already have a product, product area, or workflow to evaluate. It is especially useful for:

• roadmap resets,
• feature prioritization workshops,
• product differentiation work,
• “quick wins vs strategic bets” discussions,
• and early requirements framing before implementation tickets exist.

What makes this skill different from a generic prompt

The main differentiator is discipline. The skill is explicit about two boundaries:

• No code: this is strategy work, not solution implementation.
• Write to file: outputs are meant to be saved as session documents, which is helpful when you want reusable planning artifacts instead of chat-only advice.

It also forces a sequence: understand current value, generate possible leaps, evaluate ruthlessly, then prioritize.

When this skill is a poor fit

Skip game-changing-features if you need:

• detailed engineering specs,
• UI copy,
• implementation tasks,
• bug triage,
• or validation from real customer data you do not have.

It is strongest at structured strategic exploration, not proof that a feature will succeed.

How to Use game-changing-features skill

Install context for game-changing-features

The repository does not publish a single universal install command inside SKILL.md, so game-changing-features install depends on your skill runner. In Skills-compatible setups, the common pattern is to add the softaworks/agent-toolkit repository, then invoke the game-changing-features skill by name.

A typical install pattern is:

npx skills add softaworks/agent-toolkit --skill game-changing-features

If your environment uses a different skill loader, keep the same repo and skill slug:

• repo: softaworks/agent-toolkit
• skill: game-changing-features

Files to read before first use

For fast adoption, read these in order:

1. skills/game-changing-features/SKILL.md
2. skills/game-changing-features/README.md

SKILL.md contains the real operating rules and workflow. README.md is useful for quick fit-checking, but it is not the main execution guide.

What input the skill expects

The skill works best when you provide three inputs up front:

• Product or area: what you want analyzed
• Current state: what exists today
• Constraints: team, time, tech, market, or business limits

The current state and constraints are technically optional, but output quality drops quickly without them.

The minimum viable prompt

A workable game-changing-features usage prompt looks like:

Use game-changing-features for Requirements Planning.

Product/Area: Team inbox triage for support managers
Current state: Shared inbox, tags, macros, basic SLA reporting, high manual sorting
Constraints: 2 engineers, 1 designer, 8-week window, no model fine-tuning, must work inside existing Zendesk workflow
Goal: Identify the highest-leverage feature moves, then rank them into now/next/later.

This is enough to trigger the intended workflow without overloading the model.

How to turn a rough idea into a strong prompt

Weak prompt:

What features should we add to our support product?

Stronger prompt:

Use game-changing-features on our support platform.

Product/Area: Agent workflow and queue management
Who uses it: Support managers and frontline agents at B2B SaaS companies
Current value: Helps teams process tickets, collaborate, and track SLAs
Core user action: Sort, assign, and resolve inbound issues
Pain points: Repetitive triage, poor prioritization, hard handoffs, weak visibility into urgent revenue-risk tickets
Constraints: We need something shippable in one quarter, must fit our existing UI, and should differentiate us from help desk competitors
Output needed: 10x opportunities, scoring rationale, and ranked recommendations for Requirements Planning

The stronger version gives the skill enough product context to find leverage instead of guessing.

Recommended workflow in practice

A good game-changing-features guide session usually follows this order:

1. define the product area narrowly,
2. summarize current user value,
3. list recurring pains or repeated requests,
4. state hard constraints,
5. ask for 10x opportunities at multiple scales,
6. ask for evaluation and stack ranking,
7. convert the top 2–3 ideas into requirements candidates.

This avoids a common failure mode: asking for “game-changing” ideas before the current value and friction are clear.

What the skill is trying to produce

From the repository signals, the workflow centers on:

• understanding current value,
• finding opportunities across different scales,
• evaluating ideas by impact and feasibility,
• identifying highest-leverage moves,
• and prioritizing the result.

That means your goal should not be “more ideas.” Your goal should be “better decisions.”

Practical output handling

SKILL.md instructs the agent to write results to a session file under .claude/docs/ai/<product-or-area>/10x/session-N.md. If your environment supports file-writing skills, keep that behavior because it makes strategy outputs reviewable and easier to compare across sessions.

If your environment does not support that path, ask the agent to preserve the same structure in your preferred docs folder.

How to use it for Requirements Planning

game-changing-features for Requirements Planning works best as a front-end filter before writing specs. A productive pattern is:

• run the skill to identify 10x moves,
• choose one “Do Now” and one “Strategic Bet,”
• then write requirements only for the shortlisted options.

This prevents teams from over-specifying low-leverage work.

Common adoption blockers

Teams usually struggle with this skill when:

• the product area is too broad,
• the prompt includes no user behavior or pain points,
• every idea is treated as equally valid,
• or the team jumps straight from “big idea” to “build it.”

The skill gives better results when the strategic question is narrow and the operating constraints are explicit.

game-changing-features skill FAQ

Is game-changing-features only for startups?

No. game-changing-features is useful anywhere a team needs high-leverage prioritization. Startups benefit from the founder-style framing, but internal tools, SaaS products, and mature platforms can also use it to find outsized bets in a specific product area.

Is this better than a normal brainstorming prompt?

Usually yes, if your problem is prioritization quality rather than idea quantity. A normal prompt can produce lots of features. The game-changing-features skill is more valuable when you need the model to judge which ideas could actually change user value in a meaningful way.

Does it generate product requirements directly?

Not really. It is a strategy-first skill. It helps you choose what deserves requirements work next. Use it before PRDs, spec drafting, or implementation planning.

Can beginners use game-changing-features?

Yes, but beginners should provide more context than experienced PMs usually need. If you are new to product strategy, include:

• who the user is,
• what they do today,
• the main pain points,
• and what constraints are real.

Without that, the output may sound impressive but stay generic.

When should I not use game-changing-features?

Do not use game-changing-features as your main tool when you need:

• customer research synthesis,
• exact market sizing,
• delivery estimates,
• or feature specs ready for engineers.

It complements those activities; it does not replace them.

Does the skill require access to my codebase?

Not strictly, but it helps. The workflow explicitly starts by understanding current value, and repository or product evidence improves that step. If no codebase or documentation is available, compensate with a precise product description and known user pain points.

How to Improve game-changing-features skill

Give it a narrower product surface area

The fastest way to improve game-changing-features output is to scope the session tightly. “Our product” is too broad. “Onboarding activation for first-time workspace admins” is much better. Narrow scope produces sharper leverage points and less filler.

Provide evidence, not only opinions

Good inputs include:

• top user complaints,
• repeated feature requests,
• churn reasons,
• support themes,
• usage bottlenecks,
• and known competitive weaknesses.

The skill is designed for strategic thinking, but it becomes far more credible when grounded in observed behavior.

State constraints early and specifically

Constraints improve output because they force prioritization. Include things like:

• team size,
• delivery window,
• platform limits,
• compliance concerns,
• pricing model,
• and integration boundaries.

If you leave constraints out, the agent may over-recommend moonshots that are interesting but not useful.

Ask for ranking criteria in the output

To make the skill more actionable, ask the model to score each idea on criteria already implied by the repository workflow, such as:

• impact,
• reach,
• frequency,
• differentiation,
• defensibility,
• and feasibility.

That turns a creative session into something a product team can debate concretely.

Separate quick wins from strategic bets

A common failure mode is mixing “ship this in weeks” ideas with “change the product category” ideas. Improve game-changing-features usage by requiring three buckets:

• quick wins,
• medium-term bets,
• and compounding strategic moves.

This makes the final output easier to convert into roadmap planning.

Force stronger reasoning after the first draft

After the first pass, ask follow-up questions like:

• Which idea changes user behavior the most?
• Which idea is hardest for competitors to copy?
• Which idea increases retention rather than just acquisition?
• Which option is realistic inside our constraints?

The first output often surfaces possibilities; the second pass is where decision quality improves.

Turn the top idea into requirements-ready inputs

Once game-changing-features identifies a winner, do not stop there. Ask for:

• target user,
• triggering problem,
• desired behavior change,
• success metrics,
• risks,
• and dependencies.

That creates a clean bridge from strategy into Requirements Planning without asking the skill to become an implementation spec writer.

Watch for common failure modes

The most common output problems are:

• generic “AI-powered” suggestions,
• ideas disconnected from current user value,
• too many features with weak ranking,
• and recommendations that ignore business constraints.

If you see those patterns, the fix is usually better inputs, narrower scope, and a stricter request for evaluation criteria.

Improve game-changing-features with comparison prompts

One high-value pattern is to ask for contrast, not just ideas. For example:

Use game-changing-features and compare:
1. the best 10x move for retention,
2. the best 10x move for expansion revenue,
3. the best 10x move for user delight.
Then recommend only one to prioritize this quarter and explain why.

Comparison forces tradeoff thinking, which is where this skill is most useful.

Re-run the skill after strategy shifts

Revisit game-changing-features whenever your market, positioning, or product maturity changes. A feature that is game-changing at one stage can become table stakes later. The skill is most valuable as a repeatable strategic lens, not a one-time brainstorm.