Idea Validator

Setup

1. 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.
2. Create project folder under resolved root:

   YYYY_MM_DD_<short_snake_case_name>/

3. Create

   idea.md

   : Document the idea and clarifications
4. Create

   validate.md

   : Document evaluation and recommendations
5. Echo the absolute project folder path in your response so downstream skills can auto-pick it.

$ARGUMENTS

Phase 1: Clarify the Idea

• 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?

idea.md

Phase 2: Gather Technical Context

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

idea.md

Phase 3: Critical Evaluation

validate.md

• Similar existing products
• Market size and competition
• Unique differentiation

• Evidence people will pay
• Problem urgency level

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

• Clear revenue path?
• Willingness to pay?

• Buildable with stated constraints?
• Key technical risks?

Build it

Maybe

Skip it

• Creativity
• Feasibility
• Market Impact
• Technical Execution

Phase 4: Improvements

validate.md

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

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)

ideas

README.md

YYYY_MM_DD_*

• 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)

README.md

## Ideas index

• link to each

  idea.md

• PRD/tasks status
• verdict link to

  validate.md

Reporting with GitHub links (mandatory)

• GitHub link to

  idea.md

• GitHub link to

  validate.md

• GitHub link to

  README.md

  when it was updated
• Commit hash

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

Output Summary

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

File Templates

idea.md

# 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:

## Discussion Notes
[Updates from conversation]

validate.md

# 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

## How to Strengthen
[Actionable improvements]

## Enhanced Version
[Optimized concept]

## Implementation Roadmap
[Phased approach]