idea-validator

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Idea Validator

创意验证工具

Critically evaluate ideas with honest feedback on market viability, technical feasibility, and actionable improvements.

批判性地评估创意，提供关于市场可行性、技术可行性的真实反馈以及可执行的改进建议。

Setup

设置步骤

Resolve storage location (tool-agnostic, ask once per environment)
- Prefer env var
```
IDEAS_ROOT
```
  if set.
- Else use shared marker file:
```
~/.config/ideas-root.txt
```
  .
- Backward compatibility: if shared marker is missing but legacy
```
~/.openclaw/ideas-root.txt
```
  exists, reuse its value and write it into
```
~/.config/ideas-root.txt
```
  .
- If no marker exists (new environment), ask user once where to store generated docs.
- Suggested default:
```
/home/luongnv/workspace/ideas
```
  .
- Save chosen root to
```
~/.config/ideas-root.txt
```
  .
- Only ask again if the user explicitly asks to change location.
Create project folder under resolved root:
```
YYYY_MM_DD_<short_snake_case_name>/
```
Create
idea.md
: Document the idea and clarifications
Create
validate.md
: Document evaluation and recommendations
Echo the absolute project folder path in your response so downstream skills can auto-pick it.

If no idea provided in

$ARGUMENTS

, ask user to describe their concept.

确定存储位置（与工具无关，每个环境仅询问一次）
- 如果已设置环境变量
```
IDEAS_ROOT
```
  则优先使用。
- 否则使用共享标记文件：
```
~/.config/ideas-root.txt
```
  。
- 向后兼容：如果共享标记文件不存在，但旧版
```
~/.openclaw/ideas-root.txt
```
  存在，则复用其值并写入
```
~/.config/ideas-root.txt
```
  。
- 如果没有标记文件（新环境），仅询问用户一次生成的文档存储位置。
- 建议默认路径：
```
/home/luongnv/workspace/ideas
```
  。
- 将选定的根路径保存到
```
~/.config/ideas-root.txt
```
  。
- 仅当用户明确要求更改位置时才再次询问。
在确定的根目录下创建项目文件夹：
```
YYYY_MM_DD_<short_snake_case_name>/
```
创建
idea.md
：记录创意及相关说明
创建
validate.md
：记录评估结果及建议
在回复中返回项目文件夹的绝对路径，以便后续技能自动获取。

如果

$ARGUMENTS

中未提供创意，请要求用户描述其概念。

Phase 1: Clarify the Idea

阶段1：明确创意

Ask user (via AskUserQuestion):

What problem does this solve? Who has this pain?
Who is your target user? Be specific.
What makes this different from existing solutions?
What does success look like in 6-12 months?

Update

idea.md

with responses.

通过AskUserQuestion询问用户：

这个创意解决什么问题？目标用户是谁？
你的目标用户是谁？请具体化。
与现有解决方案相比，它的独特之处是什么？
6-12个月内的成功标准是什么？

将回复内容更新到

idea.md

中。

Phase 2: Gather Technical Context

阶段2：收集技术背景信息

Ask user:

Preferred tech stack?
Timeline and team size?
Budget situation (bootstrapped/funded/side project)?
Existing assets (code, designs, research)?

Update

idea.md

technical section.

询问用户：

偏好的技术栈是什么？
项目时间线和团队规模？
预算情况（自筹资金/获得投资/副业项目）？
现有资源（代码、设计、研究成果）？

将内容更新到

idea.md

的技术部分。

Phase 3: Critical Evaluation

阶段3：批判性评估

Evaluate honestly and update

validate.md

Market Analysis:

Similar existing products
Market size and competition
Unique differentiation

Demand Assessment:

Evidence people will pay
Problem urgency level

Feasibility:

Can this ship in 2-4 weeks MVP?
Minimum viable features
Complex dependencies?

Monetization:

Clear revenue path?
Willingness to pay?

Technical Risk:

Buildable with stated constraints?
Key technical risks?

Verdict:

Build it

Maybe

Skip it

Ratings (1-10):

Creativity
Feasibility
Market Impact
Technical Execution

进行真实评估并更新

validate.md

：

市场分析：

同类现有产品
市场规模与竞争情况
独特差异化优势

需求评估：

用户付费意愿的证据
问题的紧急程度

可行性分析：

是否能在2-4周内推出MVP？
最小可行功能
是否存在复杂依赖？

盈利模式：

是否有清晰的盈利路径？
用户付费意愿如何？

技术风险：

在给定约束条件下是否可实现？
主要技术风险是什么？

结论：

Build it

Maybe

Skip it

评分（1-10分）：

创意性
可行性
市场影响力
技术执行难度

Phase 4: Improvements

阶段4：优化建议

Update

validate.md

with:

How to Strengthen: Specific, actionable improvements
Enhanced Version: Reworked, optimized concept
Implementation Roadmap: Phased approach (if applicable)

将以下内容更新到

validate.md

中：

优化方向：具体、可执行的改进建议
优化后的创意：重新梳理、优化后的概念
实施路线图：分阶段实施计划（如适用）

Tone

沟通语气

Brutally honest: Don't sugarcoat fatal flaws
Constructive: Every criticism includes a suggestion
Specific: Concrete examples, not vague feedback
Balanced: Acknowledge strengths alongside weaknesses

极度坦诚：不掩饰致命缺陷
富有建设性：每一条批评都附带改进建议
具体明确：给出具体案例，而非模糊反馈
客观平衡：同时认可优势与不足

README Maintenance (when running inside ideas repo)

README维护（在创意仓库内运行时）

If the current working directory looks like the root of an

ideas

repo (contains

README.md

+ multiple

YYYY_MM_DD_*

idea folders):

After creating/updating
```
idea.md
```
+
```
validate.md
```
, update the repo index table by running:
- ```
python3 scripts/update_readme_ideas_index.py
```
  (if the script exists)

If the script does not exist, update

README.md

manually by inserting/updating an

## Ideas index

table with:

link to each
```
idea.md
```
PRD/tasks status
verdict link to
```
validate.md
```

如果当前工作目录是

ideas

仓库的根目录（包含

README.md

及多个

YYYY_MM_DD_*

格式的创意文件夹）：

创建/更新
```
idea.md
```
和
```
validate.md
```
后，运行以下命令更新仓库索引表：
- ```
python3 scripts/update_readme_ideas_index.py
```
  （如果该脚本存在）

如果脚本不存在，手动更新

README.md

，插入/更新

## Ideas index

表格，包含：

每个
```
idea.md
```
的链接
PRD/任务状态
指向
```
validate.md
```
的结论链接

Reporting with GitHub links (mandatory)

报告要求（必须包含GitHub链接）

When reporting completion, include:

GitHub link to
```
idea.md
```
GitHub link to
```
validate.md
```
GitHub link to
```
README.md
```
when it was updated
Commit hash

Link format:

https://github.com/luongnv89/ideas/blob/main/<relative-path>

完成后提交报告时，需包含：

```
idea.md
```
的GitHub链接
```
validate.md
```
的GitHub链接
若更新了
```
README.md
```
，需提供其GitHub链接
提交哈希值

链接格式：

https://github.com/luongnv89/ideas/blob/main/<relative-path>

Output Summary

输出总结

After all phases:

Confirm folder/files created
State verdict and key ratings
Top 3 strengths, top 3 concerns
Single most important next step

完成所有阶段后：

确认文件夹/文件已创建
说明结论及关键评分
列出Top3优势与Top3顾虑
指出最重要的下一步行动

File Templates

文件模板

idea.md

markdown

undefined

markdown

undefined

Idea: [Name]

Original Concept

[From $ARGUMENTS]

Clarified Understanding

[After Phase 1]

Target Audience

[Specific user profile]

Goals & Objectives

[Success criteria]

Technical Context

Stack:
Timeline:
Budget:
Constraints:

Stack:
Timeline:
Budget:
Constraints:

Discussion Notes

[Updates from conversation]

undefined

[Updates from conversation]

undefined

validate.md

markdown

undefined

markdown

undefined

Validation: [Name]

Quick Verdict

[Build it / Maybe / Skip it]

Why

[2-3 sentence explanation]

Similar Products

[Competitors]

Differentiation

[Unique angle]

Strengths

Concerns

Ratings

Creativity: /10
Feasibility: /10
Market Impact: /10
Technical Execution: /10

Creativity: /10
Feasibility: /10
Market Impact: /10
Technical Execution: /10

How to Strengthen

[Actionable improvements]

Enhanced Version

[Optimized concept]

Implementation Roadmap

[Phased approach]

undefined

[Phased approach]

undefined