Claude
The skeptical founder
Pressure-tests the idea, looks for the wedge, calls out weak demand, and asks what should be cut before anyone builds.
Founder planning instrument
IdeaClyst runs a structured council between Claude and Codex on your machine. It researches the market, lets each role challenge the other, and writes a planning packet you can build from.
Why a council
One prompt gives an answer. IdeaClyst gives each model a job, makes them read each other, and keeps the disagreement visible until the recommendation is clear.
Claude
Pressure-tests the idea, looks for the wedge, calls out weak demand, and asks what should be cut before anyone builds.
Codex
Designs a buildable MVP, names the data model and services, and flags any strategy that becomes expensive in code.
Synthesis
The final packet keeps the tradeoffs, but it does not leave you with a maybe. It chooses a direction and the next proof step.
How it works
Each step writes to disk as it completes. The run is local-first, readable, and designed to degrade gracefully when a browser or source is not available.
Web research
Competitors, demand signals, and source notes ground the council before the models speak.
Product strategy
Claude turns the raw idea into a focused customer, offer, and risk map.
MVP architecture
Codex designs the smallest useful release and calls out technical traps.
Critique
The product lens asks what is too large, too slow, or not tied to proof.
Critique
The engineering lens asks which assumptions are costly or infeasible for an MVP.
Synthesis
The debate resolves into a recommendation, backlog, risks, validation tests, and prompts.
What you get
The packet is structured for the next week of work, not for a slide deck nobody opens again.
01
The recommended product, the customer, and the reason to build this version first.
02
An ordered list of the smallest valuable release, ready for a coding agent.
03
The assumptions that can break the plan, paired with practical mitigations.
04
Concrete experiments, success metrics, and kill criteria for the first proof loop.
05
Prompt handoffs for product, design, engineering, validation, and follow-up research.
Files
Every run writes readable artifacts locally, including research notes and the founder brief.
Research and discovery
A headless browser scouts competitors and source lanes before the council starts. You can also ask IdeaClyst to find candidate ideas in a market before you promote one to a full run.
Research toolkit
Sources become a dossier, competitor matrix, opportunity map, validation experiments, distribution plan, kill criteria, and a one-page founder brief.
Idea discovery
Name a market and a goal. IdeaClyst looks for complaints, fresh launches, and gaps, then ranks buildable candidates with clear kill criteria.
Promotion
The selected report carries its thesis, founder fit, core offer, and roast verdict into a full planning run.
Workspace
IdeaClyst is more than a generator. It keeps a local library of ideas, reports, decisions, validation outcomes, and build-ready specs.
Profile
A founder profile adds skills, capital, time, risk tolerance, and unfair advantages to discovery and ranking.
Evidence
Claims, experiments, and validation outcomes move the score. Stale evidence gets sent back to research.
Decision log
Open assumptions and council disagreements become inspectable memory for the next run.
Build queue
A council verdict compiles into requirements, tasks, GitHub issues, and status visible in operations.
Intelligence suite
The surrounding tools help compare bets, listen for market changes, and move from a plan to a proof loop without losing provenance.