本文へ移動
cccskills
無料GitHub で公開

idea-validator

Structured validation framework that scores product ideas. Use when evaluating problem severity, willingness-to-pay, or founder-market fit. For market intelligence, see market-research.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Idea Validator Skill

When to Use

  • After completing Phase 0 (Idea) before entering Phase 1 (Validation)
  • When the user proposes a new idea or pivot
  • When deciding between multiple product directions
  • As a sanity check before committing resources

Tools Required

ToolPurpose
firecrawl_searchValidate market signals, demand indicators
firecrawl_extractPull data from market reports, forums

Instructions

1. Collect Idea Inputs

Get from the user (or from completed Phase 0 deliverables):

  • Problem statement: What pain does this solve?
  • Target user: Who has this pain? (be specific: role, company size, industry)
  • Proposed solution: How does this solve it? (one sentence)
  • Revenue model: How does this make money?
  • Differentiator: Why can't they just use {existing solution}?

2. Score on 5 Dimensions

Each dimension scored 1-5. Total score determines recommendation.

A. Problem Severity (1-5)

ScoreCriteria
1Nice-to-have. Users tolerate current solutions fine.
2Mild annoyance. Users complain but don't switch.
3Real pain. Users actively search for alternatives.
4Hair-on-fire. Users lose money/time daily without a solution.
5Mission-critical. Business cannot function without solving this.

Validate with:

firecrawl_search: "{problem_statement} pain point frustrated"
firecrawl_search: "site:reddit.com {target_user} struggling with {problem}"

B. Willingness to Pay (1-5)

ScoreCriteria
1Users expect free. No existing paid solutions.
2Users pay reluctantly. < $10/mo willingness.
3Established paid market. $10-50/mo common.
4Users budget for this. $50-200/mo normal.
5Enterprise budgets. $200+/mo, multi-seat deals.

Validate with:

firecrawl_search: "{category} pricing SaaS"
firecrawl_search: "{competitor} pricing plans"

C. Market Timing (1-5)

ScoreCriteria
1Market is saturated or declining.
2Market exists but growth is flat.
3Growing market with room for new entrants.
4Emerging market with strong tailwinds (AI, regulation, etc.).
5Category creation opportunity — no one owns this yet.

D. Founder-Market Fit (1-5)

ScoreCriteria
1No domain expertise, no network, no unfair advantage.
2Some interest but learning from scratch.
3Adjacent experience. Understand the user but not the domain deeply.
4Direct experience. Have felt this pain personally.
5Deep domain expertise + network + distribution advantage.

E. Execution Feasibility (1-5)

ScoreCriteria
1Requires team of 10+, $1M+, regulatory approval.
2Needs specialized skills the founder lacks.
3Achievable solo with AI tools in 3-6 months.
4MVP shippable in 30-60 days with existing tools.
5Can validate in a weekend with no-code or AI agents.

3. Generate Scorecard

# Idea Validation Scorecard: {Idea Name}

| Dimension | Score | Evidence |
|-----------|-------|----------|
| Problem Severity | X/5 | {one-line justification} |
| Willingness to Pay | X/5 | {one-line justification} |
| Market Timing | X/5 | {one-line justification} |
| Founder-Market Fit | X/5 | {one-line justification} |
| Execution Feasibility | X/5 | {one-line justification} |
| **TOTAL** | **XX/25** | |

## Recommendation
- 20-25: **STRONG GO** — Execute immediately.
- 15-19: **CONDITIONAL GO** — Proceed but validate {weakest dimension} first.
- 10-14: **PAUSE** — Significant risks. Pivot or de-risk before investing.
- 5-9:  **NO GO** — Fundamental problems. Explore different ideas.

4. Risk Flags

Regardless of score, flag these as deal-breakers:

  • Problem Severity = 1 → "No one needs this"
  • Willingness to Pay = 1 → "Can't monetize"
  • Execution Feasibility = 1 → "Can't build it"

5. Output Format

Save to BRAINIAC/0. Idea/VALIDATION_SCORECARD.md

Quality Gates

  • Every score must have evidence (search result, data point, or user testimony)
  • WTP score must reference actual competitor pricing
  • Total recommendation must match the scoring bands exactly

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

changelog

無料

Generates and maintains changelogs following Keep a Changelog format. Use when updating release notes, finishing tasks, or tagging versions. For version bumps, see semantic-versioning.

日本語の概要は準備中です。原文の説明を表示しています。

tuliosousapro/SaaS-blueprint52026年8月31日 更新

Structured competitor teardown skill. Use when scraping competitor sites, extracting pricing/features/positioning, or analyzing strategic gaps. For general research, see market-research.

日本語の概要は準備中です。原文の説明を表示しています。

tuliosousapro/SaaS-blueprint52026年8月31日 更新

Enforces Conventional Commits format for git commit messages. Use when formatting commits or validating message structures. For git commands, see git-control.

日本語の概要は準備中です。原文の説明を表示しています。

tuliosousapro/SaaS-blueprint52026年8月31日 更新

Creates an llms.txt file from scratch based on repository structure. Use when configuring LLM discovery files. For updating existing configurations, see update-llms.

日本語の概要は準備中です。原文の説明を表示しています。

tuliosousapro/SaaS-blueprint52026年8月31日 更新

Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans ./ directory files and creates a README.md file for the project. Only used when creating a new repository. or when the README.md file is missing.

日本語の概要は準備中です。原文の説明を表示しています。

tuliosousapro/SaaS-blueprint52026年8月31日 更新

Standardizes git operations, branch management, and disaster recovery. Use when committing, branching, or resolving conflicts. For commit formatting, see conventional-commits.

日本語の概要は準備中です。原文の説明を表示しています。

tuliosousapro/SaaS-blueprint52026年8月31日 更新

tuliosousapro のスキルをすべて見る

このスキルの問題を報告する