ventureos 1.1.25 → 1.1.27

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ventureos",
-  "version": "1.1.25",
+  "version": "1.1.27",
   "description": "VentureOS — AI-powered venture building framework. From raw idea to validated venture — 12 weeks of structured ideation and incubation.",
   "type": "module",
   "bin": {

package/venture-master.md

@@ -25,12 +25,18 @@ IF venture_name is empty (first run) → skip the status table and the menu enti
 
 Hi {user_name}, I'm Victor — your AI venture orchestrator.
 
-Would you like to **start a new venture**, or **explore a domain** first?
+Where are you starting from?
+
+**[I] I have a specific idea** — jump straight into market research and customer discovery
+**[D] I have a domain to explore** — I'll map the landscape, rank opportunities, and help you pick the right one to build
+
 ---
 
 Then STOP and wait:
-- Any form of "start" / "new venture" / "idea" / "venture" → trigger NV
-- Any form of "explore" / "domain" / "research" → trigger EX
+- Any form of "idea" / "I" / "start" / "specific" / "venture" → trigger NV, pre-select entry point = Idea
+- Any form of "domain" / "D" / "explore" / "research" / "landscape" → trigger NV, pre-select entry point = Domain
+
+Both paths go through NV first (venture setup, folder creation, venture-brief.md). Domain entry runs EX as Phase 0 then continues automatically into the full incubation journey. EX from the menu is for returning users who want to run additional domain research on an active venture.
 
 IF venture_name is set → display the venture context banner and proceed to step 5:
 

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

@@ -124,13 +124,16 @@
       2. Fill in: venture name/codename, challenge statement, market forces, starting hypotheses
       3. Set entry_point: "domain" in venture-state.yaml
       4. Initialize venture-state.yaml with the new venture details
-      5. Ask user: "Is this the opportunity you want to take into incubation? If yes, we move to Phase 1: Setup the Team."
+      5. Display to user: "Domain exploration complete. Here are your top opportunities — the strongest one is pre-selected. **Confirm or pick a different one, and we move into Phase 2: Understand the Market.**"
+         Note: Phase 1 (Setup Team) is skipped — it is only relevant for corporate ventures that need a formal team charter and mothership sponsor. For domain-entry ventures, we go straight to Phase 2.
+      6. Wait for user confirmation or selection.
+      7. Once confirmed: announce "Skipping Phase 1 (team setup — not needed here). Moving into **Phase 2: Understand the Market** with your domain research already loaded as baseline." Then route to [UM] Understand the Market.
     </instructions>
     <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-state.yaml">
-      Update: venture_name, entry_point: "domain", current_phase: "1-setup-team", completed_artifacts with all domain research files
+      Update: venture_name, entry_point: "domain", current_phase: "2-understand-market", completed_artifacts with all domain research files
     </state-update>
   </step>
 

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

@@ -63,7 +63,7 @@
       Prioritize: identify Top 3 Unfair Advantages. List assets to activate in next 30 days.
       Save to output folder. Update venture-state.yaml.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/mothership-asset-map.md">
+    <template-output file="{output_folder}/{venture_name}/setup-team/mothership-asset-map.md">
       Save completed Mothership Asset Map.
     </template-output>
   </step>

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

@@ -78,7 +78,7 @@
       Fill all sections. Review with user. Save to output folder.
       Update venture-state.yaml: mark team-charter as complete in category_progress.team.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/team-charter.md">
+    <template-output file="{output_folder}/{venture_name}/setup-team/team-charter.md">
       Save completed Team Charter.
     </template-output>
     <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">

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

@@ -29,7 +29,7 @@
       6. Flag: which competitors could pivot into our space if we find strong demand?
       Cite all sources. Apply research_depth setting.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/competitive-analysis.md">
+    <template-output file="{output_folder}/{venture_name}/understand-market/competitive-analysis.md">
       Save competitive landscape report with differentiation map.
     </template-output>
     <checkpoint>
@@ -57,7 +57,7 @@
 
       Flag if TAM &lt; $100M — significant risk signal.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/market-sizing.md">
+    <template-output file="{output_folder}/{venture_name}/understand-market/market-sizing.md">
       Save market sizing with both methodologies and all sources.
     </template-output>
   </step>
@@ -76,7 +76,7 @@
          - Economic shifts
       4. Assess: does the mothership have assets that lower key barriers?
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/market-landscape.md">
+    <template-output file="{output_folder}/{venture_name}/understand-market/market-landscape.md">
       Save full market landscape report including barriers and trends.
     </template-output>
   </step>

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

@@ -65,7 +65,7 @@
       5. Interview target: who to interview first, how many, what types
       Use the pain-hypothesis.md template.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/pain-hypothesis.md">
+    <template-output file="{output_folder}/{venture_name}/find-pain/pain-hypothesis.md">
       Save initial pain hypothesis with assumptions to test.
     </template-output>
   </step>
@@ -79,7 +79,7 @@
       Note which mothership relationships can be leveraged for access.
       Update venture-state.yaml with completed artifacts and guiding_questions.domain answers.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/stakeholder-map.md">
+    <template-output file="{output_folder}/{venture_name}/understand-market/stakeholder-map.md">
       Save completed Stakeholder Map.
     </template-output>
     <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">

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

@@ -36,7 +36,7 @@
       Score each option 1-5 on feasibility.
       Recommend a route (or hybrid approach).
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/solution-feasibility.md">
+    <template-output file="{output_folder}/{venture_name}/define-solution/solution-feasibility.md">
       Save feasibility analysis with all four routes evaluated.
     </template-output>
   </step>
@@ -55,7 +55,7 @@
 
       Use web search to identify technology players, platforms, and ecosystem participants.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/ecosystem-map.md">
+    <template-output file="{output_folder}/{venture_name}/define-solution/ecosystem-map.md">
       Save ecosystem map with partnership candidates.
     </template-output>
   </step>

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

@@ -35,7 +35,7 @@
       For each risk: likelihood (1-5), impact (1-5), risk score, priority, owner, mitigation action.
       Identify the Top 5 Venture Killer Risks and assign mitigation owners and deadlines.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/venture-killer-risks.md">
+    <template-output file="{output_folder}/{venture_name}/business-case/venture-killer-risks.md">
       Save completed risk registry.
     </template-output>
   </step>
@@ -55,7 +55,7 @@
 
       This plan feeds directly into the check-in pitch.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/experiment-plan.md">
+    <template-output file="{output_folder}/{venture_name}/business-case/experiment-plan.md">
       Save operating and experiment plan.
     </template-output>
   </step>

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

@@ -35,7 +35,7 @@
       - Revenue Streams, Key Resources, Key Activities, Key Partnerships, Cost Structure
       Include unit economics summary: ACV, Gross Margin, LTV, CAC, LTV:CAC ratio, Payback Period.
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/business-model-canvas.md">
+    <template-output file="{output_folder}/{venture_name}/business-case/business-model-canvas.md">
       Save Business Model Canvas.
     </template-output>
   </step>
@@ -52,7 +52,7 @@
       5. Design a pricing validation experiment (landing page A/B, customer interview, pilot pricing)
       6. Calculate revenue implications per tier
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/pricing-model.md">
+    <template-output file="{output_folder}/{venture_name}/business-case/pricing-model.md">
       Save pricing model with tiers and validation plan.
     </template-output>
   </step>
@@ -71,7 +71,7 @@
 
       Update venture-state.yaml: completed_artifacts, guiding_questions.design_business
     </instructions>
-    <template-output file="{output_folder}/{venture_name}/monetisation-plan.md">
+    <template-output file="{output_folder}/{venture_name}/business-case/monetisation-plan.md">
       Save monetisation plan.
     </template-output>
     <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">