ventureos 1.1.1 → 1.1.3

package/README.md

@@ -148,7 +148,7 @@ Everything is saved automatically. Come back tomorrow and Victor picks up exactl
 
 **Guided mode** (default) — Victor pauses after each step, shows you the output, and asks for your approval before moving on. Best for real ventures where decisions matter.
 
-**Auto mode** — Victor runs the full phase on its own and shows you everything at the end. Best when you want to quickly screen an idea.
+**Yolo mode** — Victor runs the full phase on its own and shows you everything at the end. Best when you want to move fast without stopping at every checkpoint.
 
 **Autopilot** — Type `AP` and Victor runs the entire 12-week journey in one go: market research, synthetic customer interviews, solution design, business case, board evaluation, and a full pitch deck. No input needed. You get a complete `venture-scan-report.md` at the end — a single document covering every phase, clearly marked as AI-generated, with a prioritised list of what to validate with real customers first.
 

package/install.js

@@ -252,8 +252,9 @@ output_folder: "_ventures"
 # deep     = exhaustive multi-source research with cross-validation
 research_depth: "${researchDepth}"
 
-# Your AI provider (used when running via built-in chat)
-# Options: anthropic | openai | gemini
+# Your AI tool or provider
+# IDE users: claude-code | cursor | windsurf | other
+# API users: anthropic | openai | gemini
 llm: "${llm}"
 
 # Execution mode for workflows
@@ -303,7 +304,7 @@ async function runSetupWizard(rl, { forIDE = false } = {}) {
 
   console.log('\n  How should workflows run by default?\n');
   console.log('     1.  Guided  — pauses so you review each step  (recommended)');
-  console.log('     2.  Auto    — runs everything on its own\n');
+  console.log('     2.  Yolo    — runs everything on its own\n');
   const modeInput = await rl.question('     Select [1-2]: ');
   const defaultMode = modeInput.trim() === '2' ? 'yolo' : 'guided';
 
@@ -502,7 +503,8 @@ async function main() {
     console.log('  Installing...');
     console.log(line() + '\n');
 
-    const configYaml = generateConfig({ userName, researchDepth, llm: 'anthropic', defaultMode });
+    const ideLlm = chosenIDE.id === 'claude' ? 'claude-code' : (['cursor', 'windsurf'].includes(chosenIDE.id) ? chosenIDE.id : 'other');
+    const configYaml = generateConfig({ userName, researchDepth, llm: ideLlm, defaultMode });
     installFiles(projectRoot, ventureOSDir, configYaml);
 
     console.log('\n' + line());

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ventureos",
-  "version": "1.1.1",
+  "version": "1.1.3",
   "description": "VentureOS — AI-powered venture building framework. From raw idea to investor-ready pitch in 12 structured weeks.",
   "type": "module",
   "bin": {

package/workflows/0-explore/domain-deep-dive/instructions.xml

@@ -129,7 +129,7 @@
     <template-output file="{output_folder}/{venture_name}/venture-canvas.md">
       Save venture canvas as starting artifact.
     </template-output>
-    <state-update file="{project-root}/ventureOS/_memory/venture-sidecar/venture-state.yaml">
+    <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
       Update: venture_name, entry_point: "domain", current_phase: "1-setup-team", completed_artifacts with all domain research files
     </state-update>
   </step>

package/workflows/0-explore/domain-deep-dive/workflow.yaml

@@ -21,13 +21,13 @@ default_output_folder: "{output_folder}/{venture_name}/domain-research/"
 
 # Templates used
 templates:
-  - "{project-root}/ventureOS/data/templates/venture-canvas.md"
-  - "{project-root}/ventureOS/data/templates/market-sizing.md"
-  - "{project-root}/ventureOS/data/templates/stakeholder-map.md"
+  - "{project-root}/ventureOS/templates/venture-canvas.md"
+  - "{project-root}/ventureOS/templates/market-sizing.md"
+  - "{project-root}/ventureOS/templates/stakeholder-map.md"
 
 # Data files
 data:
-  brainstorming: "{project-root}/ventureOS/data/techniques/brainstorming-techniques.csv"
+  brainstorming: "{project-root}/ventureOS/techniques/brainstorming-techniques.csv"
 
 tags:
   - exploration

package/workflows/1-setup-team/mothership-alignment/instructions.xml

@@ -81,7 +81,7 @@
       Add Sponsor details to mothership-asset-map.md (Sponsor Alignment section).
       Update venture-state.yaml: category_progress.mothership = "complete".
     </instructions>
-    <state-update file="{project-root}/ventureOS/_memory/venture-sidecar/venture-state.yaml">
+    <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
       Update: completed_artifacts, category_progress.mothership, guiding_questions.setup answers for mothership questions
     </state-update>
   </step>

package/workflows/1-setup-team/mothership-alignment/workflow.yaml

@@ -14,8 +14,8 @@ installed_path: "{project-root}/ventureOS/workflows/1-setup-team/mothership-alig
 instructions: "{installed_path}/instructions.xml"
 
 templates:
-  - "{project-root}/ventureOS/data/templates/mothership-asset-map.md"
-  - "{project-root}/ventureOS/data/templates/stakeholder-map.md"
+  - "{project-root}/ventureOS/templates/mothership-asset-map.md"
+  - "{project-root}/ventureOS/templates/stakeholder-map.md"
 
 tags:
   - mothership

package/workflows/1-setup-team/team-formation/instructions.xml

@@ -81,7 +81,7 @@
     <template-output file="{output_folder}/{venture_name}/team-charter.md">
       Save completed Team Charter.
     </template-output>
-    <state-update file="{project-root}/ventureOS/_memory/venture-sidecar/venture-state.yaml">
+    <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
       Update: completed_artifacts, category_progress.team, guiding_questions.setup answers
     </state-update>
   </step>

package/workflows/1-setup-team/team-formation/workflow.yaml

@@ -16,8 +16,8 @@ instructions: "{installed_path}/instructions.xml"
 default_output_folder: "{output_folder}/{venture_name}/"
 
 templates:
-  - "{project-root}/ventureOS/data/templates/team-charter.md"
-  - "{project-root}/ventureOS/data/templates/venture-canvas.md"
+  - "{project-root}/ventureOS/templates/team-charter.md"
+  - "{project-root}/ventureOS/templates/venture-canvas.md"
 
 tags:
   - setup-team

package/workflows/2-understand-market/market-mapping/instructions.xml

@@ -93,7 +93,7 @@
       5. Is this market large enough to support a venture? (≥$100M TAM?)
       Update venture-state.yaml with completed artifacts and guiding_questions.domain answers.
     </instructions>
-    <state-update file="{project-root}/ventureOS/_memory/venture-sidecar/venture-state.yaml">
+    <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
       Update: completed_artifacts (market-sizing, competitive-analysis, market-landscape), guiding_questions.domain
     </state-update>
   </step>

package/workflows/2-understand-market/market-mapping/workflow.yaml

@@ -15,7 +15,7 @@ installed_path: "{project-root}/ventureOS/workflows/2-understand-market/market-m
 instructions: "{installed_path}/instructions.xml"
 
 templates:
-  - "{project-root}/ventureOS/data/templates/market-sizing.md"
+  - "{project-root}/ventureOS/templates/market-sizing.md"
 
 tags:
   - market-mapping

package/workflows/2-understand-market/stakeholder-identification/instructions.xml

@@ -82,7 +82,7 @@
     <template-output file="{output_folder}/{venture_name}/stakeholder-map.md">
       Save completed Stakeholder Map.
     </template-output>
-    <state-update file="{project-root}/ventureOS/_memory/venture-sidecar/venture-state.yaml">
+    <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
       Update: completed_artifacts, hypotheses.customer, guiding_questions.domain
     </state-update>
   </step>

package/workflows/2-understand-market/stakeholder-identification/workflow.yaml

@@ -14,8 +14,8 @@ installed_path: "{project-root}/ventureOS/workflows/2-understand-market/stakehol
 instructions: "{installed_path}/instructions.xml"
 
 templates:
-  - "{project-root}/ventureOS/data/templates/stakeholder-map.md"
-  - "{project-root}/ventureOS/data/templates/pain-hypothesis.md"
+  - "{project-root}/ventureOS/templates/stakeholder-map.md"
+  - "{project-root}/ventureOS/templates/pain-hypothesis.md"
 
 tags:
   - stakeholder-mapping

package/workflows/3-find-pain/customer-pain-discovery/step-4-pain-atomization.md

@@ -10,7 +10,7 @@ Decompose the validated broad pain into atomic, testable units. Score each unit
 ## 4.1 Load FIP Framework and Context
 
 Load:
-- `{project-root}/ventureOS/data/scoring/pain-scoring.yaml` — FIP scoring framework
+- `{project-root}/ventureOS/scoring/pain-scoring.yaml` — FIP scoring framework
 - `interview-synthesis.md` — all interview learnings
 - `pain-hypothesis.md` — current pain hypothesis
 

package/workflows/3-find-pain/customer-pain-discovery/workflow.md

@@ -24,10 +24,10 @@ Modes can be combined (e.g., run real interviews AND run synthetic simulations t
 
 Before starting, the agent should:
 1. Load `{project-root}/ventureOS/config.yaml`
-2. Load `{project-root}/ventureOS/_memory/venture-sidecar/venture-state.yaml`
+2. Load `{project-root}/ventureOS/_memory/venture-state.yaml`
 3. Load `pain-hypothesis.md` if it exists (from Phase 2)
 4. Load `stakeholder-map.md` if it exists (from Phase 2)
-5. Load `{project-root}/ventureOS/data/scoring/pain-scoring.yaml` (FIP framework)
+5. Load `{project-root}/ventureOS/scoring/pain-scoring.yaml` (FIP framework)
 6. Confirm: discovery mode (T/S/I) and execution mode (Guided/Yolo)
 
 ---

package/workflows/4-define-solution/feasibility-assessment/instructions.xml

@@ -73,7 +73,7 @@
 
       Update venture-state.yaml: completed_artifacts, guiding_questions.solution (technical feasibility question)
     </instructions>
-    <state-update file="{project-root}/ventureOS/_memory/venture-sidecar/venture-state.yaml">
+    <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
       Update: completed_artifacts (solution-feasibility, ecosystem-map), guiding_questions.solution
     </state-update>
   </step>

package/workflows/4-define-solution/feasibility-assessment/workflow.yaml

@@ -14,8 +14,8 @@ installed_path: "{project-root}/ventureOS/workflows/4-define-solution/feasibilit
 instructions: "{installed_path}/instructions.xml"
 
 templates:
-  - "{project-root}/ventureOS/data/templates/solution-feasibility.md"
-  - "{project-root}/ventureOS/data/templates/ecosystem-map.md"
+  - "{project-root}/ventureOS/templates/solution-feasibility.md"
+  - "{project-root}/ventureOS/templates/ecosystem-map.md"
 
 tags:
   - feasibility

package/workflows/4-define-solution/wedge-design/workflow.md

@@ -24,8 +24,8 @@ Load from venture-state.yaml:
 1. Primary pain hypothesis (hypotheses.problem)
 2. ICP hypothesis (hypotheses.customer)
 3. Load `pain-atomization.md`, `icp-profile.md`, `pain-journey-map.md`
-4. Load `{project-root}/ventureOS/data/techniques/brainstorming-techniques.csv` for wedge-storm and value-prop-sprint techniques
-5. Load `{project-root}/ventureOS/data/techniques/synthetic-tools.csv` for vibe-code-wedge and synthetic testing tools
+4. Load `{project-root}/ventureOS/techniques/brainstorming-techniques.csv` for wedge-storm and value-prop-sprint techniques
+5. Load `{project-root}/ventureOS/techniques/synthetic-tools.csv` for vibe-code-wedge and synthetic testing tools
 
 ---
 

package/workflows/5-business-case/checkin-pitch/step-3-nvb-review.md

@@ -12,7 +12,7 @@ Simulate the New Venture Board check-in review. The Venture Evaluator acts as th
 Load:
 - `pitch/checkin-pitch.md` (the deck)
 - `checkin-evidence.md` (supporting evidence)
-- `{project-root}/ventureOS/data/scoring/gate-rubric.yaml` (rubric + checkin_gate focus criteria)
+- `{project-root}/ventureOS/scoring/gate-rubric.yaml` (rubric + checkin_gate focus criteria)
 - All completed artifacts from venture-state.yaml
 
 Note: For the check-in gate, focus evaluation on:

package/workflows/5-business-case/initial-business-case/instructions.xml

@@ -75,7 +75,7 @@
       Save pilot pipeline to experiment-plan.md (Pilot section).
       Update venture-state.yaml with guiding_questions.business_case answers.
     </instructions>
-    <state-update file="{project-root}/ventureOS/_memory/venture-sidecar/venture-state.yaml">
+    <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
       Update: completed_artifacts, guiding_questions.business_case
     </state-update>
   </step>

package/workflows/5-business-case/initial-business-case/workflow.yaml

@@ -14,8 +14,8 @@ installed_path: "{project-root}/ventureOS/workflows/5-business-case/initial-busi
 instructions: "{installed_path}/instructions.xml"
 
 templates:
-  - "{project-root}/ventureOS/data/templates/venture-killer-risks.md"
-  - "{project-root}/ventureOS/data/templates/experiment-plan.md"
+  - "{project-root}/ventureOS/templates/venture-killer-risks.md"
+  - "{project-root}/ventureOS/templates/experiment-plan.md"
 
 tags:
   - business-case

package/workflows/6-design-business/business-model-design/instructions.xml

@@ -74,7 +74,7 @@
     <template-output file="{output_folder}/{venture_name}/monetisation-plan.md">
       Save monetisation plan.
     </template-output>
-    <state-update file="{project-root}/ventureOS/_memory/venture-sidecar/venture-state.yaml">
+    <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
       Update: completed_artifacts (business-model-canvas, pricing-model, monetisation-plan), guiding_questions.design_business
     </state-update>
   </step>

package/workflows/6-design-business/business-model-design/workflow.yaml

@@ -14,12 +14,12 @@ installed_path: "{project-root}/ventureOS/workflows/6-design-business/business-m
 instructions: "{installed_path}/instructions.xml"
 
 templates:
-  - "{project-root}/ventureOS/data/templates/business-model-canvas.md"
-  - "{project-root}/ventureOS/data/templates/pricing-model.md"
-  - "{project-root}/ventureOS/data/templates/monetisation-plan.md"
+  - "{project-root}/ventureOS/templates/business-model-canvas.md"
+  - "{project-root}/ventureOS/templates/pricing-model.md"
+  - "{project-root}/ventureOS/templates/monetisation-plan.md"
 
 data:
-  brainstorming: "{project-root}/ventureOS/data/techniques/brainstorming-techniques.csv"
+  brainstorming: "{project-root}/ventureOS/techniques/brainstorming-techniques.csv"
 
 tags:
   - business-model

package/workflows/6-design-business/final-pitch/step-4-nvb-final-review.md

@@ -12,8 +12,8 @@ Simulate the full NVB final gate review. The Venture Evaluator acts as the NVB p
 Load:
 - `pitch/pitch-deck.md` — the final deck
 - ALL completed artifacts from venture-state.yaml
-- `{project-root}/ventureOS/data/scoring/gate-rubric.yaml` — full rubric (all 7 criteria + weights)
-- `{project-root}/ventureOS/data/scoring/pivot-triggers.yaml` — if pivot is needed
+- `{project-root}/ventureOS/scoring/gate-rubric.yaml` — full rubric (all 7 criteria + weights)
+- `{project-root}/ventureOS/scoring/pivot-triggers.yaml` — if pivot is needed
 
 The Venture Evaluator simulates a 5-person NVB panel:
 1. **NVB Chair** — overall investment thesis

package/workflows/venture-status/instructions.xml

@@ -9,8 +9,8 @@
     <title>Load Venture State</title>
     <instructions>
       Load and parse:
-      1. {project-root}/ventureOS/_memory/venture-sidecar/venture-state.yaml
-      2. {project-root}/ventureOS/_memory/venture-sidecar/pivot-history.yaml
+      1. {project-root}/ventureOS/_memory/venture-state.yaml
+      2. {project-root}/ventureOS/_memory/pivot-history.yaml
       3. {project-root}/ventureOS/config.yaml (for venture_name, user_name)
     </instructions>
   </step>