Skip to main content
ClaudeWave
ES, Spanish
Skill2.6k estrellas del repoactualizado 7mo ago

game-changing-features

This Claude Code skill applies structured strategic thinking to product development by identifying transformational opportunities across three effort levels: massive features that expand market reach, medium-effort enhancements that accelerate core workflows, and small changes with disproportionate impact. Use it when seeking high-leverage product improvements, exploring 10x value creation, or planning strategic direction rather than incremental feature additions.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/softaworks/agent-toolkit /tmp/game-changing-features && cp -r /tmp/game-changing-features/skills/game-changing-features ~/.claude/skills/game-changing-features
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# 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 valuable over time
- Network effects, data effects, habit formation
- Build moats

### Step 5: Prioritize

Don't just list ideas—stack rank them:

```
## Recommended Priority

### Do Now (Quick wins)
1. [Feature] — Why: [reason], Impact: [what changes]

### Do Next (High leverage)
1. [Feature] — Why: [reason], Unlocks: [what becomes possible]

### Explore (Strategic bets)
1. [Feature] — Why: [reason], Risk: [what could go wrong], Upside: [what we gain]

### Backlog (Good but not now)
1. [Feature] — Why later: [reason]
```

---

## Idea Categories to Explore

Force yourself through each category:

| Category | Question | Example |
|----------|----------|---------|
| **Speed** | What takes too long? | Instant search, predictive loading |
| **Automation** | What's repetitive? | Auto-scheduling, smart defaults |
| **Intelligence** | What could be smarter? | Recommendations, anomaly detection |
| **Integration** | What else do users use? | Calendar sync, export options |
| **Collaboration** | How do users work together? | Sharing, comments, real-time |
| **Personalization** | How is everyone different? | Custom views, preferences |
| **Visibility** | What's hidden that shouldn't be? | Dashboards, progress tracking |
| **Confidence** | What creates anxiety? | Confirmations, undo, previews |
| **Delight** | What could spark joy? | Animations, celebrations, polish |
| **Access** | Who can't use this yet? | Mobile, offline, accessibility |

---

## Output Format

```markdown
# 10x Analysis: <Product/Area>
Session N | Date: YYYY-MM-DD

## Current Value
What the product does today and for whom.

## The Question
What would make this 10x more valuable?

---

## Massive Opportunities

### 1. [Feature Name]
**What**: Description
**Why 10x**: Why this is transformative
**Unlocks**: What becomes possible
**Effort**: High/Very High
**Risk**: What could go wrong
**Score**: 🔥/👍/🤔/❌

### 2. ...

---

## Medium Opportunities

### 1. [Feature Name]
**What**: Description
**Why 10x**: Why this matters more than it seems
**Impact**: What changes for users
**Effort**: Medium
**Score**: 🔥/👍/🤔/❌

### 2. ...

---

## Small Gems

### 1. [Feature Name]
**What**: Description (one line)
**Why powerful**: Why this punches above its weight
**Effort**: Low
**Score**: 🔥/👍/🤔/❌

### 2. ...

---

## R
agent-md-refactorSkill

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

ascii-ui-mockup-generatorSubagent

Use this agent when you need to visualize UI concepts through ASCII mockups before implementation. Examples: <example>Context: User has an idea for a dashboard layout with data tables and charts. user: 'I want to create a dashboard that shows user analytics with a sidebar navigation, main content area with charts, and a data table below' assistant: 'I'll use the ascii-ui-mockup-generator agent to create multiple ASCII mockup variations for your dashboard concept.' <commentary>The user wants to visualize a UI concept, so use the ascii-ui-mockup-generator to create multiple ASCII representations they can choose from.</commentary></example> <example>Context: User is designing a form layout with multiple input fields. user: 'I need a contact form with name, email, message fields and a submit button' assistant: 'Let me use the ascii-ui-mockup-generator to create several ASCII mockup options for your contact form layout.' <commentary>Since the user needs to visualize form layouts, use the ascii-ui-mockup-generator to provide multiple ASCII design options.</commentary></example>

backend-to-frontend-handoff-docsSkill

Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'create handoff', 'document API', 'frontend handoff', or 'API documentation'.

c4-architectureSkill

Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context/container/component/deployment diagrams. Triggers include "architecture diagram", "C4 diagram", "system context", "container diagram", "component diagram", "deployment diagram", "document architecture", "visualize architecture".

codebase-pattern-finderSubagent

codebase-pattern-finder is a useful subagent_type for finding similar implementations, usage examples, or existing patterns that can be modeled after. It will give you concrete code examples based on what you're looking for! It's sorta like codebase-locator, but it will not only tell you the location of files, it will also give you code details!

codexSkill

Use when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing. Uses GPT-5.2 by default for state-of-the-art software engineering.

codex-planSlash Command

Create a detailed implementation plan using Codex 5.2 with high reasoning

command-creatorSkill

This skill should be used when creating a Claude Code slash command. Use when users ask to "create a command", "make a slash command", "add a command", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.