Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getcore.me/llms.txt

Use this file to discover all available pages before exploring further.

Identify core features worth building and validating across multiple professional viewpoints to test product viability.

​
Tools Required

This skill runs using CORE memory only. No integrations required.

​
Step 1: Clarify the Opportunity

Align your team on the product concept:
  • Product: What is the core product or service you’re exploring?
  • Problem: What problem does it solve or what job does it do?
  • Target audience: Which specific customer segment or user type should you focus on?
  • Desired user outcomes: What should users be able to accomplish with this product?
Review any supporting materials like market research, competitive landscape analysis, or customer interviews. If you have explicit customer feedback, share it with the team.

​
Step 2: Generate Feature Ideas

Develop five specific feature concepts from each perspective. Focus on features that address the core problem or enable the desired user outcome.
  • Product Manager perspective: Market fit and competitive positioning, value creation and customer willingness to pay, business model and monetization
  • Designer perspective: Ease of initial adoption and onboarding, user experience and interface design, retention mechanics and delight factors
  • Engineer perspective: Technical feasibility and required infrastructure, available APIs or third-party integrations, scalability constraints and platform dependencies
Encourage diverse thinking. All ideas are valid at this stage; prioritization follows.

​
Step 3: Rank Top 5 Ideas

Select the strongest feature concepts using these criteria:
  • Solves the core problem: Does this directly address the user problem or job-to-be-done?
  • Can we test this quickly?: Is there a fast, low-cost way to validate user interest?
  • Creates meaningful differentiation: Does this offer unique value versus existing alternatives?
  • Feasibility: Can core functionality be built with reasonable engineering effort?

​
Step 4: Develop Rationale

For each prioritized idea, articulate:
  • Feature name and concise description
  • Why this idea was selected and aligns with the product concept
  • Core assumptions that require validation in market testing
  • Initial thinking on how to validate or test this feature

​
Output Format

New Product Ideation 💡 Product Concept
  • Product name/concept: [What you’re building]
  • Core problem: [Problem it solves]
  • Target audience: [Who you’re building for]
  • Desired outcome: [What users should be able to do]
🎯 Top 5 Ideas for MVP Feature 1: [Name]
  • Description: [How it works]
  • Selection rationale: [Why this made the top 5]
  • Core assumptions:
    • [Assumption 1: What users need this]
    • [Assumption 2: How they’ll use it]
    • [Assumption 3: Market demand signal]
  • Validation approach: [Quick test or experiment]
Feature 2: [Name] [Same structure] Feature 3: [Name] [Same structure] Feature 4: [Name] [Same structure] Feature 5: [Name] [Same structure] Recommended MVP Scope [Which 2-3 ideas form the core MVP] Validation Plan [Experiments or user research to test top assumptions]

​
Edge Cases

  • Scope creep: All ideas sound important for a new product. Prioritize ruthlessly to focus on the minimal core that addresses the main problem.
  • Premature technical optimization: Engineers may suggest scalability infrastructure before product-market fit is established. Build simple first.
  • Solution without problem: Ensure ideation is grounded in actual customer problems, not feature lists from competitors.
  • Untested assumptions: Most new product ideas are wrong initially. Plan aggressive validation experiments rather than extended planning.
  • Feature vs. positioning: Sometimes the differentiator is how the core features are packaged or marketed, not the features themselves.