Use Breakthrough Ideation Prover with your AI.

Validate breakthrough ideation

You must: (1) name the CONVENTIONAL approach. the boring, obvious solution everyone would suggest. A cautious manager, a Google search, a consulting deck. what would they say? You MUST name it to prove you have transcended it. If you cannot name the conventional, you do not know the space well enough to innovate, (2) propose a BREAKTHROUGH idea. not a variation on the conventional ("do it faster/cheaper"). a genuine paradigm shift. What assumption does the industry share that might be wrong? What approach is NO ONE considering? What would a founder from a different industry do? (3) ground it in VERIFIABLE FACTS. cite specific technologies, companies, research papers, benchmarks, case studies. "Studies show" and "proven technology" are not facts. NAME the source. Breakthrough ideas are built on overlooked facts, not imagination, (4) integrate REAL-WORLD CONSTRAINTS. budget ($X), timeline (Y months), team (Z people with specific skills), regulatory barriers, technical maturity gaps, organizational inertia. "No constraints" means you have not thought hard enough. Every breakthrough navigates constraints, (5) map a CONCRETE IMPLEMENTATION ROADMAP. not "Phase 1: Plan, Phase 2: Build." WHO does WHAT by WHEN to produce WHAT RESULT? Week 1 first action, Month 1 milestone, Quarter 1 validation point with measurable success criteria, (6) PROVE FEASIBILITY. for each critical blocker, name the specific workaround or mitigation. "Easily overcome" is not a mitigation. name the blocker, name the workaround, acknowledge residual risk. If the capability rejects, your idea is either too safe, too fantasy, or has no path to reality. Push harder. Find the way. Structured reflection capability for breakthrough ideation on complex challenges. Forces the agent to ideate RADICALLY while staying GROUNDED in reality. The agent must name the conventional approach to prove it has been transcended, propose a genuinely non-obvious idea, anchor it in verifiable facts, integrate real-world constraints, map a concrete implementation path, and prove feasibility by mitigating every critical blocker. Catches Conventional Thinking (suggesting the obvious, safe, Google-first-result answer), Fantasy Ideation (ideas that sound revolutionary but have no factual basis), Constraint Blindness (ignoring budget, timeline, regulation, team reality), Vision Without Path (a beautiful destination with no roadmap to get there), and Unrealizable Commitments (critical blockers with no viable workaround). Call once per challenge that demands a breakthrough solution