# Discover High-Impact Product Features

Teams often waste roadmap time on small feature requests. This skill guides a focused strategy session to find, score, and prioritize larger opportunities.

## Install

```bash
npx skillstore add softaworks/game-changing-features
```

## Metadata

- Status: approved
- Slug: softaworks-game-changing-features
- Skillstore revision: r1
- Version status: missing
- Tree hash: ee269f34e40d5bb3f056055b9a21a07d76d44a88e60efa5da41e6e5c3f1d0489
- Author: softaworks
- GitHub username: softaworks
- License: MIT
- Repository: https://github.com/softaworks/agent-toolkit/tree/main/skills/game-changing-features/
- Ref: f93e9bb0daca99badb6a7e574b97737155d57cb3
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/softaworks-game-changing-features
- Manifest: https://skillstore.pages.dev/api/skills/softaworks-game-changing-features/manifest

## Capabilities

- Guides a five-step product strategy workflow from current value to prioritization.
- Explores massive, medium, and small feature opportunities.
- Evaluates ideas using impact, reach, frequency, differentiation, defensibility, and feasibility.
- Groups recommendations into Do Now, Do Next, Explore, and Backlog priorities.
- Documents assumptions, blockers, validation tasks, and next steps.

## Use Cases

- Refresh a product roadmap: Find higher-impact opportunities before committing another cycle to incremental feature work.
- Identify strategic bets: Explore bold moves that could expand the market, deepen retention, or create a stronger moat.
- Prioritize engineering focus: Compare quick wins, platform work, and risky bets before assigning team capacity.

## Prompt Templates

### Start a basic 10x review

```
Find 10x opportunities for [product]. Current users are [users], and the product currently does [current state].
```

### Improve a product area

```
Analyze [product area] for high-impact improvements. Consider speed, automation, intelligence, integration, collaboration, personalization, visibility, confidence, delight, and access.
```

### Compare roadmap options

```
Evaluate these candidate features for 10x potential: [features]. Score impact, reach, frequency, differentiation, defensibility, feasibility, risk, and priority.
```

### Plan a strategic bet

```
Build a prioritized 10x roadmap for [product] with constraints [constraints], known user complaints [complaints], and business goals [goals]. Include assumptions, blockers, and validation steps.
```

## Limitations

- Does not write code, prototypes, or implementation plans.
- Needs product context, current state, and constraints for useful output.
- Recommendations still require user research and market validation.
- Cannot guarantee technical feasibility or commercial success.

## Best Practices

- Provide the product area, user type, current state, and known constraints before starting.
- Ask the skill to separate quick wins from strategic bets.
- Validate the highest-ranked assumptions with users before committing build time.

## Anti Patterns

- Do not use it as a substitute for customer discovery.
- Do not treat every bold idea as ready for implementation.
- Do not ask for code or technical specifications during the strategy session.

## Security Audit

- Audited at: 2026-07-07T04:54:24.37\+00:00
- Summary: All seven static findings are false positives. The flagged locations are Markdown paths, fenced output templates, and ordinary product strategy wording, with no executable command usage or reconnaissance behavior found.

## Stats

- Views: 138
- Downloads: 12
- Favorites: 0
- Popularity score: 0