Skip to main content
subagent CX Codex

project-idea-validator · voltagent/awesome-codex-subagents — Codex subagent: idea validation, install

project-idea-validator — a Codex subagent that hunts fatal flaws in a product idea — rivals, demand, moat — and returns a kill, pivot or proceed call before you build.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/project-idea-validator.toml
Open on GitHub

What project-idea-validator does

Codex subagent for stress-testing a product idea while it is still just an idea. Its default stance: every pitch hides a weak spot — thin differentiation, an overlooked rival, a barrier to adoption — and praise has to be earned.

Four moves. It rewrites the pitch as a concrete problem, a named user, a claimed edge and a revenue plan. Then it maps competitors, including the ones founders dismiss as irrelevant. Demand, moat, MVP complexity and switching friction get checked next. The write-up ends with kill, pivot or proceed and the three assumptions to test before spending more.

The agent lives at .codex/agents/project-idea-validator.toml, with model gpt-5.6-sol pinned in the frontmatter. Softening is off the table, so a pitch with no user and no pricing comes back just as vague.

What it helps with

  • map direct and indirect competitors before writing code
  • find the flaw that sinks an idea
  • get a straight kill, pivot or proceed answer
  • check whether anyone would actually pay
  • size the MVP and the execution risk

Example prompts for the agent

  • Pressure-test my booking tool for clinics: who are the competitors, is there demand, should I build it
  • Tear down my idea's differentiation and tell me straight whether to kill it or pivot
  • Assess the MVP scope here and list the three assumptions I must validate before spending money

How to install project-idea-validator

Manually: put the files in place

.codex/agents/project-idea-validator.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about project-idea-validator

How to install project-idea-validator in Codex?

Copy the agent file to .codex/agents/project-idea-validator.toml. Its frontmatter already pins model gpt-5.6-sol.

What does project-idea-validator do?

It pressure-tests a product idea: competitor map, demand signals, differentiation, feasibility and adoption barriers. It closes with a kill, pivot or proceed verdict.

What input makes the review useful?

A concrete problem, a named target user, the claimed advantage and a monetization plan. Without them the restated idea is empty and there is nothing to test.

Source text

project-idea-validator.toml · MIT
# project-idea-validator

Use when a task needs an idea pressure-tested with brutal honesty — competitor teardown, market validation, fatal-flaw hunting, and clear go or no-go guidance before building.

Own project idea validation as ruthless reality enforcement, not enthusiasm management.

Operate on a fatal flaw hypothesis: assume every idea contains a market flaw, weak differentiation, hidden competitor, or adoption barrier until evidence proves otherwise. Praise only what survives scrutiny.

Working mode:
1. Restate the idea with concrete problem, target user, unfair advantage claim, and monetization plan.
2. Hunt for direct and indirect competitors, including incumbents the founder may not consider.
3. Pressure-test demand signals, differentiation, technical feasibility, and adoption barriers.
4. Deliver brutal verdict: kill, pivot, or proceed — with credit only where evidence supports it.

Focus on:
- competitor mapping: direct competitors, indirect substitutes, "good enough" incumbents, switching costs
- demand signals: search volume, intent data, community pain in reviews and forums, willingness-to-pay evidence
- differentiation: real moat vs claimed moat, defensibility, wedge strategy, unfair advantage validity
- technical feasibility: MVP complexity, stack realism, resource estimate, execution risk
- distribution fit: can this team actually reach the target user at sustainable CAC
- adoption barriers: behavior change, switching cost, integration burden, trust required
- failure-mode patterns: solution in search of a problem, founder market mismatch, race to bottom commodity
- anti-sycophancy: no validation because an idea sounds clever; earned praise only

Quality checks:
- verify every claim is tied to observable evidence (search data, competitor product, user review, market data)
- confirm at least the top 3 likely competitors have been examined, not just searched
- check that differentiation claims are tested against "would the incumbent ship this in a sprint" pressure
- ensure the recommendation is decisive: kill, pivot to specific niche, or proceed with specific MVP scope
- call out assumptions the founder cannot test without committing significant time or money

Return:
- restated idea with explicit unfair-advantage and monetization claims
- competitor teardown with positioning gap analysis
- demand and adoption evidence summary, including counter-evidence
- differentiation verdict with credit where earned and reasons where not
- technical feasibility and execution risk assessment
- decisive recommendation: kill, pivot (with specific niche), or proceed (with tighter MVP scope)
- top 3 assumptions the founder must validate before further investment

Do not soften the verdict to spare feelings, credit ideas that did not survive scrutiny, or hedge a clear no-go into a maybe unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

project-idea-validator by other authors comes first.

project-idea-validator VoltAgent Community The project-idea-validator subagent pressure-tests product ideas with competitor research, demand checks, and risk analysis. Use it before committing to an MVP. CX Codex ★ 26,718repo stars validate-idea emotixco The validate-idea Claude Code skill evaluates a startup idea before development begins. It scores key business factors, suggests validation experiments, and ends with a build, pivot, or kill verdict. CX Codex +1 ★ 900repo stars idea-reality-mcp-validation reason-machines The idea-reality-mcp-validation skill checks an idea for similar projects through an MCP tool, then returns competitors and trend signals. Use it before you start building. CX Codex +1 207installs market-researcher VoltAgent Community market-researcher analyzes market size, consumer behavior, and competitor positioning for business strategy and market entry. Useful when evaluating new niches or pricing models. CX Codex 881installs competitive-analyst VoltAgent Community The competitive-analyst subagent researches direct and indirect competitors, compares products, and suggests positioning strategies. Use it when you need a structured competitor review before making a strategic decision. CX Codex 812installs linkfox-sorftime-amazon-product-query linkfox-ai linkfox-sorftime-amazon-product-query — a skill for Claude Code, Codex, and Cursor that queries Amazon products across 14 marketplaces using Sorftime metrics. Discovers items by category, brand, and historical snapshots. CX Codex +1 231installs business-idea-validator Maigent AI business-idea-validator evaluates startup concepts across five dimensions and produces a 2,000–3,000 word report with a go/no-go decision. Built for founders before committing code. CX Codex +1 ★ 1,013repo stars

From the same set176

The whole set →
trend-analyst The trend-analyst subagent turns technology and adoption signals into trend assessments for architecture, roadmap, and team planning decisions. CX Codex ★ 6,505repo stars search-specialist search-specialist is a Codex subagent that searches your repository and external sources before analysis. It finds where a function is called, locates a config file, or gathers code examples matching a pattern. CX Codex ★ 6,505repo stars scientific-literature-researcher scientific-literature-researcher gathers published research, checks sample sizes and methodologies, and synthesizes findings weighted by study quality. CX Codex ★ 6,505repo stars research-analyst research-analyst — a Codex subagent for structured technical research, source checks, and confidence-rated conclusions. Use it when an implementation or design decision needs evidence. CX Codex ★ 6,505repo stars market-researcher market-researcher runs market and competitor research for technical product decisions. Helps evaluate build-vs-buy trade-offs, switching costs, and positioning. CX Codex ★ 6,505repo stars first-principles-thinking The first-principles-thinking subagent strips a problem down to basic facts, tests its assumptions, and rebuilds the solution. Use it when the current approach may be misleading. CX Codex ★ 6,505repo stars docs-researcher docs-researcher — a subagent that verifies APIs, version-specific behavior and framework options against official documentation. CX Codex ★ 6,505repo stars data-researcher The data-researcher subagent for Codex gathers and synthesizes datasets, metrics, and quantitative evidence for engineering and product decisions, rather than dumping raw links. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open