ideation

name	ideation
description	Generate and frame software product or feature ideas using user problems, market signals, constraints, and opportunity analysis. Use when brainstorming, discovering opportunities, or deciding what should exist and why it matters.

Purpose

This skill helps turn vague prompts, observations, or opportunities into clear software product or feature concepts worth considering.

Use this skill when:

• Brainstorming product or feature ideas
• Exploring opportunity areas
• Framing user problems
• Comparing possible solution directions
• Clarifying why an idea matters
• Preparing an idea for validation

Inputs

Expected inputs:

• Starting prompt
• User pain or observation
• Target audience
• Market or operational signal
• Business context
• Constraints
• Existing product boundaries

If inputs are missing, this skill can help elicit them. Later lifecycle work typically depends on an idea produced here, especially validation and goal-setting.

Ideation Principles

Always optimize for:

1. Clear problem framing
2. Specific target users
3. Multiple plausible options
4. Explicit assumptions
5. Fast paths to validation

Avoid optimizing solely for:

• Novelty
• Internal preference
• Technology enthusiasm
• Feature volume
• Vague market trends

Process

Step 1: Frame the Problem

Clarify:

• Who has the problem
• What they are trying to accomplish
• Why current options are insufficient
• What constraint or trigger makes the problem important now

Flag vague audiences, unsupported claims, or solution-first framing.

---

Step 2: Generate Candidate Ideas

Produce multiple possible product or feature directions.

For each idea, identify:

• Target user
• Core problem
• Proposed solution
• Expected value
• Key assumption

---

Step 3: Compare Opportunities

Evaluate each idea across:

Factor	Questions
User Pain	Is the problem frequent, severe, or costly?
Reach	How many users or workflows are affected?
Fit	Does this align with product and business direction?
Feasibility	Can this plausibly be built or tested?
Differentiation	Why would this be better than alternatives?

Use judgment instead of forcing ideas into numeric rankings too early.

---

Step 4: Select Testable Concepts

Choose the strongest candidates and express each as a testable concept.

Include:

• Problem statement
• Target user
• Value hypothesis
• Riskiest assumption
• Suggested validation approach

Anti-Patterns

Avoid:

• Starting with a fixed implementation
• Brainstorming without a target user
• Treating every idea as equally viable
• Ignoring constraints
• Confusing internal requests with user needs
• Skipping validation assumptions

Reviewer Checklist

Before finalizing ideation:

• Is the target user specific?
• Is the problem more than a vague inconvenience?
• Are assumptions explicit?
• Are there multiple options?
• Is at least one idea ready for validation?

Escalation Guidance

Escalate when:

• The strategic direction is unclear
• User groups have conflicting needs
• Constraints make all options implausible
• The problem appears unsupported by evidence
• Stakeholders disagree on the opportunity area

Example

Input:

• Support team reports repeated customer confusion during onboarding
• Product wants to reduce manual setup calls

Expected output:

1. Guided onboarding checklist
2. Setup health dashboard
3. Contextual in-app setup prompts

Recommended next skill:

• Use validation to test whether the onboarding problem and proposed solution matter.