evaluating-new-ideas

Guides structured Go/Park/Kill evaluation of early-stage project ideas via three-gate analysis.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/michaelkd01/dic-skills --skill evaluating-new-ideas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evaluating-new-ideas
Source: https://github.com/michaelkd01/dic-skills/tree/main/evaluating-new-ideas
Command: npx skills add https://github.com/michaelkd01/dic-skills --skill evaluating-new-ideas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill stops new ideas from being pursued without a disciplined, documented evaluation and gives you a go/park/kill verdict backed by buyer insight, market context, and build feasibility.

Core Features & Use Cases

  • Gate 1 … Problem & Market guides you through problem clarity, buyer-pain alignment, and competitive research with a mandate for real-sourced data before any serious commitment.
  • Gate 2 … Viability & Build checks the business model, build complexity, and revenue timeline to ensure the idea can be executed with existing capabilities.
  • Gate 3 … Strategic Fit evaluates timing, moat, and whether the opportunity reinforces current strengths and priorities, then records everything in the IDEA LOG and chat log.
  • Use Case: When a stakeholder shares a new product pitch, run this three-gate process to decide whether to move toward starting a project or park/kill the idea.

Quick Start

Evaluate the new idea description to decide Go, Park, or Kill through the three-gate process.

Frequently Asked Questions about evaluating-new-ideas

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

FAQPage Schema
How do I evaluate new product ideas to decide whether to go, park, or kill them?

Evaluating new product ideas for a go/park/kill decision requires a structured three-gate vetting process analyzing problem clarity, buyer alignment, market context, build effort, and strategic fit. This framework ensures disciplined documentation before any project commitment.

What is the best way to vet a new project pitch before starting development?

Vetting a project pitch effectively requires gate-by-gate analysis of problem and market context, business viability, and strategic timing. This structured evaluation framework prevents pursuing ideas without documented buyer insight and build feasibility.

How do I run a market analysis and buyer-pain alignment check for early-stage ideas?

Running market analysis and buyer-pain alignment checks involves passing ideas through an initial problem and market gate. This evaluation step mandates real-sourced competitive research and problem clarity validation before any serious development commitment.

Can I use a decision framework to assess build complexity and revenue timeline for new proposals?

Yes, a viability and build evaluation gate checks business models, build complexity, and revenue timelines for new proposals. This decision framework ensures your idea can be executed with existing capabilities before you move toward project initiation.

When should I park or kill a new product idea instead of moving forward?

You should park or kill a new product idea when it fails the strategic fit evaluation gate, lacking timing alignment, a defensible moat, or reinforcement of current priorities. Documenting these results in an idea log ensures structured vetting outcomes.