ventureos 1.1.26 → 1.1.27

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (9) hide show
  1. package/package.json +1 -1
  2. package/workflows/0-explore/domain-deep-dive/instructions.xml +3 -2
  3. package/workflows/1-setup-team/mothership-alignment/instructions.xml +1 -1
  4. package/workflows/1-setup-team/team-formation/instructions.xml +1 -1
  5. package/workflows/2-understand-market/market-mapping/instructions.xml +3 -3
  6. package/workflows/2-understand-market/stakeholder-identification/instructions.xml +2 -2
  7. package/workflows/4-define-solution/feasibility-assessment/instructions.xml +2 -2
  8. package/workflows/5-business-case/initial-business-case/instructions.xml +2 -2
  9. package/workflows/6-design-business/business-model-design/instructions.xml +3 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ventureos",
3
- "version": "1.1.26",
3
+ "version": "1.1.27",
4
4
  "description": "VentureOS — AI-powered venture building framework. From raw idea to validated venture — 12 weeks of structured ideation and incubation.",
5
5
  "type": "module",
6
6
  "bin": {
package/workflows/0-explore/domain-deep-dive/instructions.xml CHANGED
@@ -124,9 +124,10 @@
124
124
  2. Fill in: venture name/codename, challenge statement, market forces, starting hypotheses
125
125
  3. Set entry_point: "domain" in venture-state.yaml
126
126
  4. Initialize venture-state.yaml with the new venture details
127
- 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 straight into Phase 1: Understand the Market.**"
127
+ 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.**"
128
+ 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.
128
129
  6. Wait for user confirmation or selection.
129
- 7. Once confirmed: announce "Moving into Phase 1. Your domain research is loaded as the baseline — no need to repeat it." Then route to [UM] Understand the Market.
130
+ 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.
130
131
  </instructions>
131
132
  <template-output file="{output_folder}/{venture_name}/venture-canvas.md">
132
133
  Save venture canvas as starting artifact.
package/workflows/1-setup-team/mothership-alignment/instructions.xml CHANGED
@@ -63,7 +63,7 @@
63
63
  Prioritize: identify Top 3 Unfair Advantages. List assets to activate in next 30 days.
64
64
  Save to output folder. Update venture-state.yaml.
65
65
  </instructions>
66
- <template-output file="{output_folder}/{venture_name}/mothership-asset-map.md">
66
+ <template-output file="{output_folder}/{venture_name}/setup-team/mothership-asset-map.md">
67
67
  Save completed Mothership Asset Map.
68
68
  </template-output>
69
69
  </step>
package/workflows/1-setup-team/team-formation/instructions.xml CHANGED
@@ -78,7 +78,7 @@
78
78
  Fill all sections. Review with user. Save to output folder.
79
79
  Update venture-state.yaml: mark team-charter as complete in category_progress.team.
80
80
  </instructions>
81
- <template-output file="{output_folder}/{venture_name}/team-charter.md">
81
+ <template-output file="{output_folder}/{venture_name}/setup-team/team-charter.md">
82
82
  Save completed Team Charter.
83
83
  </template-output>
84
84
  <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
package/workflows/2-understand-market/market-mapping/instructions.xml CHANGED
@@ -29,7 +29,7 @@
29
29
  6. Flag: which competitors could pivot into our space if we find strong demand?
30
30
  Cite all sources. Apply research_depth setting.
31
31
  </instructions>
32
- <template-output file="{output_folder}/{venture_name}/competitive-analysis.md">
32
+ <template-output file="{output_folder}/{venture_name}/understand-market/competitive-analysis.md">
33
33
  Save competitive landscape report with differentiation map.
34
34
  </template-output>
35
35
  <checkpoint>
@@ -57,7 +57,7 @@
57
57
 
58
58
  Flag if TAM &lt; $100M — significant risk signal.
59
59
  </instructions>
60
- <template-output file="{output_folder}/{venture_name}/market-sizing.md">
60
+ <template-output file="{output_folder}/{venture_name}/understand-market/market-sizing.md">
61
61
  Save market sizing with both methodologies and all sources.
62
62
  </template-output>
63
63
  </step>
@@ -76,7 +76,7 @@
76
76
  - Economic shifts
77
77
  4. Assess: does the mothership have assets that lower key barriers?
78
78
  </instructions>
79
- <template-output file="{output_folder}/{venture_name}/market-landscape.md">
79
+ <template-output file="{output_folder}/{venture_name}/understand-market/market-landscape.md">
80
80
  Save full market landscape report including barriers and trends.
81
81
  </template-output>
82
82
  </step>
package/workflows/2-understand-market/stakeholder-identification/instructions.xml CHANGED
@@ -65,7 +65,7 @@
65
65
  5. Interview target: who to interview first, how many, what types
66
66
  Use the pain-hypothesis.md template.
67
67
  </instructions>
68
- <template-output file="{output_folder}/{venture_name}/pain-hypothesis.md">
68
+ <template-output file="{output_folder}/{venture_name}/find-pain/pain-hypothesis.md">
69
69
  Save initial pain hypothesis with assumptions to test.
70
70
  </template-output>
71
71
  </step>
@@ -79,7 +79,7 @@
79
79
  Note which mothership relationships can be leveraged for access.
80
80
  Update venture-state.yaml with completed artifacts and guiding_questions.domain answers.
81
81
  </instructions>
82
- <template-output file="{output_folder}/{venture_name}/stakeholder-map.md">
82
+ <template-output file="{output_folder}/{venture_name}/understand-market/stakeholder-map.md">
83
83
  Save completed Stakeholder Map.
84
84
  </template-output>
85
85
  <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
package/workflows/4-define-solution/feasibility-assessment/instructions.xml CHANGED
@@ -36,7 +36,7 @@
36
36
  Score each option 1-5 on feasibility.
37
37
  Recommend a route (or hybrid approach).
38
38
  </instructions>
39
- <template-output file="{output_folder}/{venture_name}/solution-feasibility.md">
39
+ <template-output file="{output_folder}/{venture_name}/define-solution/solution-feasibility.md">
40
40
  Save feasibility analysis with all four routes evaluated.
41
41
  </template-output>
42
42
  </step>
@@ -55,7 +55,7 @@
55
55
 
56
56
  Use web search to identify technology players, platforms, and ecosystem participants.
57
57
  </instructions>
58
- <template-output file="{output_folder}/{venture_name}/ecosystem-map.md">
58
+ <template-output file="{output_folder}/{venture_name}/define-solution/ecosystem-map.md">
59
59
  Save ecosystem map with partnership candidates.
60
60
  </template-output>
61
61
  </step>
package/workflows/5-business-case/initial-business-case/instructions.xml CHANGED
@@ -35,7 +35,7 @@
35
35
  For each risk: likelihood (1-5), impact (1-5), risk score, priority, owner, mitigation action.
36
36
  Identify the Top 5 Venture Killer Risks and assign mitigation owners and deadlines.
37
37
  </instructions>
38
- <template-output file="{output_folder}/{venture_name}/venture-killer-risks.md">
38
+ <template-output file="{output_folder}/{venture_name}/business-case/venture-killer-risks.md">
39
39
  Save completed risk registry.
40
40
  </template-output>
41
41
  </step>
@@ -55,7 +55,7 @@
55
55
 
56
56
  This plan feeds directly into the check-in pitch.
57
57
  </instructions>
58
- <template-output file="{output_folder}/{venture_name}/experiment-plan.md">
58
+ <template-output file="{output_folder}/{venture_name}/business-case/experiment-plan.md">
59
59
  Save operating and experiment plan.
60
60
  </template-output>
61
61
  </step>
package/workflows/6-design-business/business-model-design/instructions.xml CHANGED
@@ -35,7 +35,7 @@
35
35
  - Revenue Streams, Key Resources, Key Activities, Key Partnerships, Cost Structure
36
36
  Include unit economics summary: ACV, Gross Margin, LTV, CAC, LTV:CAC ratio, Payback Period.
37
37
  </instructions>
38
- <template-output file="{output_folder}/{venture_name}/business-model-canvas.md">
38
+ <template-output file="{output_folder}/{venture_name}/business-case/business-model-canvas.md">
39
39
  Save Business Model Canvas.
40
40
  </template-output>
41
41
  </step>
@@ -52,7 +52,7 @@
52
52
  5. Design a pricing validation experiment (landing page A/B, customer interview, pilot pricing)
53
53
  6. Calculate revenue implications per tier
54
54
  </instructions>
55
- <template-output file="{output_folder}/{venture_name}/pricing-model.md">
55
+ <template-output file="{output_folder}/{venture_name}/business-case/pricing-model.md">
56
56
  Save pricing model with tiers and validation plan.
57
57
  </template-output>
58
58
  </step>
@@ -71,7 +71,7 @@
71
71
 
72
72
  Update venture-state.yaml: completed_artifacts, guiding_questions.design_business
73
73
  </instructions>
74
- <template-output file="{output_folder}/{venture_name}/monetisation-plan.md">
74
+ <template-output file="{output_folder}/{venture_name}/business-case/monetisation-plan.md">
75
75
  Save monetisation plan.
76
76
  </template-output>
77
77
  <state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">