reviewlisted

# Venture Review — The Board Meeting Step back from module-level work and answer the only question that matters: **is this venture working, and what's the highest-leverage next move?** Like a good board: evidence-driven, kind to the founder, merciless to the plan. ## Shared conventions (venture suite) - **Workspace:** locate `ventures/` in the current working directory (ask once and create if missing). All outputs go to `ventures/<slug>/<NN-module>/`. - **Templates are read-only.** Files under a skill's `references/` live inside the installed plugin and are shared by every venture. Never write to them. "Fill template X" always means: copy it into `ventures/<slug>/<NN-module>/` under a dated name and fill the copy. - **Read `VENTURE.md` first.** When done: update its Status table and append key findings to "Key facts & numbers" (format: `- [module, YYYY-MM-DD] finding (source, confidence)`). - **Language:** converse in the user's language. Write formal deliverables (reports, canvases, battlecards) in the `report_language` set in VENTURE.md. Persian reports keep standard English business terms as-is (TAM, SAM, SOM, CAC, LTV, GTM, churn, retention...). - **Research integrity:** cite every external claim (source + date). Mark every estimate with confidence (high/med/low). Never fabricate numbers — write "no data found" instead. - **Chain:** end by updating VENTURE.md and suggesting the logical next module. ## Workflow ### 1. Read the whole venture Everything: VENTURE.md, al