strategy-innovate

Identify and evaluate software innovation ideas using SCAMPER and Jobs-to-be-Done frameworks with impact–effort ranking.

1|Updated Sep 12, 2025
One-click install
npx skills add https://github.com/JimmyTranDev/dotfiles --skill strategy-innovate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategy-innovate
Source: https://github.com/JimmyTranDev/dotfiles/tree/main/src/opencode/skills/strategy-innovate
Command: npx skills add https://github.com/JimmyTranDev/dotfiles --skill strategy-innovate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured ideation and evaluation for software projects using established frameworks to convert vague brainstorming into actionable opportunities.

Core Features & Use Cases

  • Framework-driven idea generation (SCAMPER, Jobs-to-be-Done, Pain Point Mining, Competitive Gap, Workflow Analysis, Constraint Removal)
  • Systematic evaluation with impact-effort perspectives to prioritize features and improvements
  • Guidance on converting ideas into tasks, roadmaps, and measurable outcomes with real-world examples

Quick Start

Generate a prioritized list of 5 product ideas for a given project using the included frameworks and evaluation criteria.

Frequently Asked Questions about strategy-innovate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate product innovation ideas using impact-effort ranking?

To evaluate product innovation ideas, apply an impact-effort matrix to prioritize features by mapping their potential value against implementation difficulty. This systematic approach converts vague brainstorming into a ranked, actionable list of high-impact opportunities.

What is the best way to brainstorm software features using the SCAMPER framework?

The SCAMPER framework drives feature brainstorming by guiding you through Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, and Reverse techniques. This structured method generates targeted software improvements across UX, performance, and automation scenarios.

How do I use Jobs-to-be-Done theory for feature prioritization?

Jobs-to-be-Done theory aids feature prioritization by identifying the underlying user needs your software must fulfill. By mining pain points and mapping solutions to these jobs, you can systematically evaluate and rank features based on real user outcomes.

Can I convert competitive gap analysis into a structured product roadmap?

Competitive gap analysis identifies missing features in your market, which can be structured into an actionable roadmap. By evaluating these gaps with an impact-effort perspective, you generate measurable outcomes and a prioritized next-step plan.

Does structured ideation work for evaluating workflow automation scenarios?

Structured ideation works effectively for evaluating workflow automation scenarios by applying systematic frameworks like constraint removal and workflow analysis. This process identifies automation opportunities and ranks them through impact-effort evaluation.

When should I avoid using systematic ideation frameworks for product brainstorming?

Avoid using systematic ideation frameworks when you need rapid, unstructured exploration without immediate evaluation constraints, or when your project lacks a defined target audience for Jobs-to-be-Done analysis and pain point mining.