project-idea-validator

Assess project ideas for market viability and fatal-flaw risks.

22|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill project-idea-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-idea-validator
Source: https://github.com/jshsakura/awesome-opencode-skills/tree/main/skills/project-idea-validator
Command: npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill project-idea-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces brutal reality checks on early project ideas, surfacing market flaws, weak differentiation, and adoption barriers before significant resources are committed.

Core Features & Use Cases

  • Comprehensive fatal-flaw detection: identifies hidden risks, competition gaps, and unproven demand.
  • Competitor teardown and differentiation analysis: evaluates incumbents and substitutes, revealing real moats or gaps.
  • Demand signals and feasibility checks: assesses market signals, technical MVP complexity, and distribution viability.
  • Clear go/no-go guidance with actionable next steps: kill, pivot to a niche, or proceed with a tightly scoped MVP.

Quick Start

Provide a brutal, evidence-based verdict on the described idea, including the unfair-advantage, market signals, and recommended next step.

Frequently Asked Questions about project-idea-validator

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

FAQPage Schema
How do I validate a project idea before committing development resources?

Idea validation requires checking market viability and fatal-flaw risks by evaluating competitor differentiation, demand signals, and adoption barriers to determine a decisive kill, pivot, or proceed verdict.

What is the best way to assess market viability for an early product strategy?

Assessing market viability involves performing a competitor teardown and verifying demand signals to ensure differentiation claims are supported by observable evidence and real market needs.

How do I identify fatal-flaw risks and adoption barriers for an MVP?

Identify fatal-flaw risks by analyzing technical feasibility, distribution viability, and competitor gaps, ensuring MVP planning accounts for unproven demand and weak differentiation before committing resources.

Can I get a go or no-go decision for my project based on competitor analysis?

Yes, a go or no-go decision comes from conducting a competitor teardown to evaluate incumbents and substitutes, revealing real moats or gaps and providing a decisive verdict on proceeding with a scoped MVP.

When do I need to pivot an idea to a niche instead of killing it completely?

Pivot an idea to a niche instead of killing it when fatal-flaw detection reveals weak differentiation against broad incumbents but observable evidence shows viable demand signals and technical feasibility for a scoped MVP.

What are the limitations of relying on market validation for technical feasibility?

Relying on market validation alone misses technical feasibility constraints and distribution viability barriers, so MVP planning must evaluate both demand signals and technical complexity to avoid unviable products.