agent-md-refactor
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow…
Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.
$ npx -y skills add softaworks/agent-toolkit --skill game-changing-features --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/game-changing-featuresContext preview
The summary Claude sees to decide when to auto-load this skill.
Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.
name: game-changing-features description: Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.
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.
---
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?"
---
User provides:
---
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.
Think across three scales:
Features that fundamentally expand what the product can do. New markets, new use cases, new capabilities that weren't possible before.
Ask:
Features that significantly enhance the core experience. Force multipliers on what already works.
Ask:
Tiny changes that punch way above their weight. Often overlooked because they seem "too simple."
Ask:
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:
Look for:
**Quick wins with outsized impact**
**Strategic bets**
**Compounding features**
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]
---
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 |
---
# 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
Opinionated skills shared by @leonardocouy for improving daily work efficiency with Claude Code. Skills are packaged instructions and scripts that extend agent capabilities across development, documentation, planning, and professional workflows.
Repo: softaworks/agent-toolkit
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow…
Create API handoff documentation for frontend developers. Use when backend work is complete…
Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create…
Use when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex…
This skill should be used when creating a Claude Code slash command. Use when users ask to…
Create high-quality git commits: review/stage intended changes, split into logical commits,…