ventureos 1.1.2 → 1.1.3
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.
- package/install.js +6 -4
- package/package.json +1 -1
- package/workflows/0-explore/domain-deep-dive/instructions.xml +1 -1
- package/workflows/0-explore/domain-deep-dive/workflow.yaml +4 -4
- package/workflows/1-setup-team/mothership-alignment/instructions.xml +1 -1
- package/workflows/1-setup-team/mothership-alignment/workflow.yaml +2 -2
- package/workflows/1-setup-team/team-formation/instructions.xml +1 -1
- package/workflows/1-setup-team/team-formation/workflow.yaml +2 -2
- package/workflows/2-understand-market/market-mapping/instructions.xml +1 -1
- package/workflows/2-understand-market/market-mapping/workflow.yaml +1 -1
- package/workflows/2-understand-market/stakeholder-identification/instructions.xml +1 -1
- package/workflows/2-understand-market/stakeholder-identification/workflow.yaml +2 -2
- package/workflows/3-find-pain/customer-pain-discovery/step-4-pain-atomization.md +1 -1
- package/workflows/3-find-pain/customer-pain-discovery/workflow.md +2 -2
- package/workflows/4-define-solution/feasibility-assessment/instructions.xml +1 -1
- package/workflows/4-define-solution/feasibility-assessment/workflow.yaml +2 -2
- package/workflows/4-define-solution/wedge-design/workflow.md +2 -2
- package/workflows/5-business-case/checkin-pitch/step-3-nvb-review.md +1 -1
- package/workflows/5-business-case/initial-business-case/instructions.xml +1 -1
- package/workflows/5-business-case/initial-business-case/workflow.yaml +2 -2
- package/workflows/6-design-business/business-model-design/instructions.xml +1 -1
- package/workflows/6-design-business/business-model-design/workflow.yaml +4 -4
- package/workflows/6-design-business/final-pitch/step-4-nvb-final-review.md +2 -2
- package/workflows/venture-status/instructions.xml +2 -2
package/install.js
CHANGED
|
@@ -252,8 +252,9 @@ output_folder: "_ventures"
|
|
|
252
252
|
# deep = exhaustive multi-source research with cross-validation
|
|
253
253
|
research_depth: "${researchDepth}"
|
|
254
254
|
|
|
255
|
-
# Your AI
|
|
256
|
-
#
|
|
255
|
+
# Your AI tool or provider
|
|
256
|
+
# IDE users: claude-code | cursor | windsurf | other
|
|
257
|
+
# API users: anthropic | openai | gemini
|
|
257
258
|
llm: "${llm}"
|
|
258
259
|
|
|
259
260
|
# Execution mode for workflows
|
|
@@ -303,7 +304,7 @@ async function runSetupWizard(rl, { forIDE = false } = {}) {
|
|
|
303
304
|
|
|
304
305
|
console.log('\n How should workflows run by default?\n');
|
|
305
306
|
console.log(' 1. Guided — pauses so you review each step (recommended)');
|
|
306
|
-
console.log(' 2.
|
|
307
|
+
console.log(' 2. Yolo — runs everything on its own\n');
|
|
307
308
|
const modeInput = await rl.question(' Select [1-2]: ');
|
|
308
309
|
const defaultMode = modeInput.trim() === '2' ? 'yolo' : 'guided';
|
|
309
310
|
|
|
@@ -502,7 +503,8 @@ async function main() {
|
|
|
502
503
|
console.log(' Installing...');
|
|
503
504
|
console.log(line() + '\n');
|
|
504
505
|
|
|
505
|
-
const
|
|
506
|
+
const ideLlm = chosenIDE.id === 'claude' ? 'claude-code' : (['cursor', 'windsurf'].includes(chosenIDE.id) ? chosenIDE.id : 'other');
|
|
507
|
+
const configYaml = generateConfig({ userName, researchDepth, llm: ideLlm, defaultMode });
|
|
506
508
|
installFiles(projectRoot, ventureOSDir, configYaml);
|
|
507
509
|
|
|
508
510
|
console.log('\n' + line());
|
package/package.json
CHANGED
|
@@ -129,7 +129,7 @@
|
|
|
129
129
|
<template-output file="{output_folder}/{venture_name}/venture-canvas.md">
|
|
130
130
|
Save venture canvas as starting artifact.
|
|
131
131
|
</template-output>
|
|
132
|
-
<state-update file="{project-root}/ventureOS/_memory/venture-
|
|
132
|
+
<state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
|
|
133
133
|
Update: venture_name, entry_point: "domain", current_phase: "1-setup-team", completed_artifacts with all domain research files
|
|
134
134
|
</state-update>
|
|
135
135
|
</step>
|
|
@@ -21,13 +21,13 @@ default_output_folder: "{output_folder}/{venture_name}/domain-research/"
|
|
|
21
21
|
|
|
22
22
|
# Templates used
|
|
23
23
|
templates:
|
|
24
|
-
- "{project-root}/ventureOS/
|
|
25
|
-
- "{project-root}/ventureOS/
|
|
26
|
-
- "{project-root}/ventureOS/
|
|
24
|
+
- "{project-root}/ventureOS/templates/venture-canvas.md"
|
|
25
|
+
- "{project-root}/ventureOS/templates/market-sizing.md"
|
|
26
|
+
- "{project-root}/ventureOS/templates/stakeholder-map.md"
|
|
27
27
|
|
|
28
28
|
# Data files
|
|
29
29
|
data:
|
|
30
|
-
brainstorming: "{project-root}/ventureOS/
|
|
30
|
+
brainstorming: "{project-root}/ventureOS/techniques/brainstorming-techniques.csv"
|
|
31
31
|
|
|
32
32
|
tags:
|
|
33
33
|
- exploration
|
|
@@ -81,7 +81,7 @@
|
|
|
81
81
|
Add Sponsor details to mothership-asset-map.md (Sponsor Alignment section).
|
|
82
82
|
Update venture-state.yaml: category_progress.mothership = "complete".
|
|
83
83
|
</instructions>
|
|
84
|
-
<state-update file="{project-root}/ventureOS/_memory/venture-
|
|
84
|
+
<state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
|
|
85
85
|
Update: completed_artifacts, category_progress.mothership, guiding_questions.setup answers for mothership questions
|
|
86
86
|
</state-update>
|
|
87
87
|
</step>
|
|
@@ -14,8 +14,8 @@ installed_path: "{project-root}/ventureOS/workflows/1-setup-team/mothership-alig
|
|
|
14
14
|
instructions: "{installed_path}/instructions.xml"
|
|
15
15
|
|
|
16
16
|
templates:
|
|
17
|
-
- "{project-root}/ventureOS/
|
|
18
|
-
- "{project-root}/ventureOS/
|
|
17
|
+
- "{project-root}/ventureOS/templates/mothership-asset-map.md"
|
|
18
|
+
- "{project-root}/ventureOS/templates/stakeholder-map.md"
|
|
19
19
|
|
|
20
20
|
tags:
|
|
21
21
|
- mothership
|
|
@@ -81,7 +81,7 @@
|
|
|
81
81
|
<template-output file="{output_folder}/{venture_name}/team-charter.md">
|
|
82
82
|
Save completed Team Charter.
|
|
83
83
|
</template-output>
|
|
84
|
-
<state-update file="{project-root}/ventureOS/_memory/venture-
|
|
84
|
+
<state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
|
|
85
85
|
Update: completed_artifacts, category_progress.team, guiding_questions.setup answers
|
|
86
86
|
</state-update>
|
|
87
87
|
</step>
|
|
@@ -16,8 +16,8 @@ instructions: "{installed_path}/instructions.xml"
|
|
|
16
16
|
default_output_folder: "{output_folder}/{venture_name}/"
|
|
17
17
|
|
|
18
18
|
templates:
|
|
19
|
-
- "{project-root}/ventureOS/
|
|
20
|
-
- "{project-root}/ventureOS/
|
|
19
|
+
- "{project-root}/ventureOS/templates/team-charter.md"
|
|
20
|
+
- "{project-root}/ventureOS/templates/venture-canvas.md"
|
|
21
21
|
|
|
22
22
|
tags:
|
|
23
23
|
- setup-team
|
|
@@ -93,7 +93,7 @@
|
|
|
93
93
|
5. Is this market large enough to support a venture? (≥$100M TAM?)
|
|
94
94
|
Update venture-state.yaml with completed artifacts and guiding_questions.domain answers.
|
|
95
95
|
</instructions>
|
|
96
|
-
<state-update file="{project-root}/ventureOS/_memory/venture-
|
|
96
|
+
<state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
|
|
97
97
|
Update: completed_artifacts (market-sizing, competitive-analysis, market-landscape), guiding_questions.domain
|
|
98
98
|
</state-update>
|
|
99
99
|
</step>
|
|
@@ -15,7 +15,7 @@ installed_path: "{project-root}/ventureOS/workflows/2-understand-market/market-m
|
|
|
15
15
|
instructions: "{installed_path}/instructions.xml"
|
|
16
16
|
|
|
17
17
|
templates:
|
|
18
|
-
- "{project-root}/ventureOS/
|
|
18
|
+
- "{project-root}/ventureOS/templates/market-sizing.md"
|
|
19
19
|
|
|
20
20
|
tags:
|
|
21
21
|
- market-mapping
|
|
@@ -82,7 +82,7 @@
|
|
|
82
82
|
<template-output file="{output_folder}/{venture_name}/stakeholder-map.md">
|
|
83
83
|
Save completed Stakeholder Map.
|
|
84
84
|
</template-output>
|
|
85
|
-
<state-update file="{project-root}/ventureOS/_memory/venture-
|
|
85
|
+
<state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
|
|
86
86
|
Update: completed_artifacts, hypotheses.customer, guiding_questions.domain
|
|
87
87
|
</state-update>
|
|
88
88
|
</step>
|
|
@@ -14,8 +14,8 @@ installed_path: "{project-root}/ventureOS/workflows/2-understand-market/stakehol
|
|
|
14
14
|
instructions: "{installed_path}/instructions.xml"
|
|
15
15
|
|
|
16
16
|
templates:
|
|
17
|
-
- "{project-root}/ventureOS/
|
|
18
|
-
- "{project-root}/ventureOS/
|
|
17
|
+
- "{project-root}/ventureOS/templates/stakeholder-map.md"
|
|
18
|
+
- "{project-root}/ventureOS/templates/pain-hypothesis.md"
|
|
19
19
|
|
|
20
20
|
tags:
|
|
21
21
|
- stakeholder-mapping
|
|
@@ -10,7 +10,7 @@ Decompose the validated broad pain into atomic, testable units. Score each unit
|
|
|
10
10
|
## 4.1 Load FIP Framework and Context
|
|
11
11
|
|
|
12
12
|
Load:
|
|
13
|
-
- `{project-root}/ventureOS/
|
|
13
|
+
- `{project-root}/ventureOS/scoring/pain-scoring.yaml` — FIP scoring framework
|
|
14
14
|
- `interview-synthesis.md` — all interview learnings
|
|
15
15
|
- `pain-hypothesis.md` — current pain hypothesis
|
|
16
16
|
|
|
@@ -24,10 +24,10 @@ Modes can be combined (e.g., run real interviews AND run synthetic simulations t
|
|
|
24
24
|
|
|
25
25
|
Before starting, the agent should:
|
|
26
26
|
1. Load `{project-root}/ventureOS/config.yaml`
|
|
27
|
-
2. Load `{project-root}/ventureOS/_memory/venture-
|
|
27
|
+
2. Load `{project-root}/ventureOS/_memory/venture-state.yaml`
|
|
28
28
|
3. Load `pain-hypothesis.md` if it exists (from Phase 2)
|
|
29
29
|
4. Load `stakeholder-map.md` if it exists (from Phase 2)
|
|
30
|
-
5. Load `{project-root}/ventureOS/
|
|
30
|
+
5. Load `{project-root}/ventureOS/scoring/pain-scoring.yaml` (FIP framework)
|
|
31
31
|
6. Confirm: discovery mode (T/S/I) and execution mode (Guided/Yolo)
|
|
32
32
|
|
|
33
33
|
---
|
|
@@ -73,7 +73,7 @@
|
|
|
73
73
|
|
|
74
74
|
Update venture-state.yaml: completed_artifacts, guiding_questions.solution (technical feasibility question)
|
|
75
75
|
</instructions>
|
|
76
|
-
<state-update file="{project-root}/ventureOS/_memory/venture-
|
|
76
|
+
<state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
|
|
77
77
|
Update: completed_artifacts (solution-feasibility, ecosystem-map), guiding_questions.solution
|
|
78
78
|
</state-update>
|
|
79
79
|
</step>
|
|
@@ -14,8 +14,8 @@ installed_path: "{project-root}/ventureOS/workflows/4-define-solution/feasibilit
|
|
|
14
14
|
instructions: "{installed_path}/instructions.xml"
|
|
15
15
|
|
|
16
16
|
templates:
|
|
17
|
-
- "{project-root}/ventureOS/
|
|
18
|
-
- "{project-root}/ventureOS/
|
|
17
|
+
- "{project-root}/ventureOS/templates/solution-feasibility.md"
|
|
18
|
+
- "{project-root}/ventureOS/templates/ecosystem-map.md"
|
|
19
19
|
|
|
20
20
|
tags:
|
|
21
21
|
- feasibility
|
|
@@ -24,8 +24,8 @@ Load from venture-state.yaml:
|
|
|
24
24
|
1. Primary pain hypothesis (hypotheses.problem)
|
|
25
25
|
2. ICP hypothesis (hypotheses.customer)
|
|
26
26
|
3. Load `pain-atomization.md`, `icp-profile.md`, `pain-journey-map.md`
|
|
27
|
-
4. Load `{project-root}/ventureOS/
|
|
28
|
-
5. Load `{project-root}/ventureOS/
|
|
27
|
+
4. Load `{project-root}/ventureOS/techniques/brainstorming-techniques.csv` for wedge-storm and value-prop-sprint techniques
|
|
28
|
+
5. Load `{project-root}/ventureOS/techniques/synthetic-tools.csv` for vibe-code-wedge and synthetic testing tools
|
|
29
29
|
|
|
30
30
|
---
|
|
31
31
|
|
|
@@ -12,7 +12,7 @@ Simulate the New Venture Board check-in review. The Venture Evaluator acts as th
|
|
|
12
12
|
Load:
|
|
13
13
|
- `pitch/checkin-pitch.md` (the deck)
|
|
14
14
|
- `checkin-evidence.md` (supporting evidence)
|
|
15
|
-
- `{project-root}/ventureOS/
|
|
15
|
+
- `{project-root}/ventureOS/scoring/gate-rubric.yaml` (rubric + checkin_gate focus criteria)
|
|
16
16
|
- All completed artifacts from venture-state.yaml
|
|
17
17
|
|
|
18
18
|
Note: For the check-in gate, focus evaluation on:
|
|
@@ -75,7 +75,7 @@
|
|
|
75
75
|
Save pilot pipeline to experiment-plan.md (Pilot section).
|
|
76
76
|
Update venture-state.yaml with guiding_questions.business_case answers.
|
|
77
77
|
</instructions>
|
|
78
|
-
<state-update file="{project-root}/ventureOS/_memory/venture-
|
|
78
|
+
<state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
|
|
79
79
|
Update: completed_artifacts, guiding_questions.business_case
|
|
80
80
|
</state-update>
|
|
81
81
|
</step>
|
|
@@ -14,8 +14,8 @@ installed_path: "{project-root}/ventureOS/workflows/5-business-case/initial-busi
|
|
|
14
14
|
instructions: "{installed_path}/instructions.xml"
|
|
15
15
|
|
|
16
16
|
templates:
|
|
17
|
-
- "{project-root}/ventureOS/
|
|
18
|
-
- "{project-root}/ventureOS/
|
|
17
|
+
- "{project-root}/ventureOS/templates/venture-killer-risks.md"
|
|
18
|
+
- "{project-root}/ventureOS/templates/experiment-plan.md"
|
|
19
19
|
|
|
20
20
|
tags:
|
|
21
21
|
- business-case
|
|
@@ -74,7 +74,7 @@
|
|
|
74
74
|
<template-output file="{output_folder}/{venture_name}/monetisation-plan.md">
|
|
75
75
|
Save monetisation plan.
|
|
76
76
|
</template-output>
|
|
77
|
-
<state-update file="{project-root}/ventureOS/_memory/venture-
|
|
77
|
+
<state-update file="{project-root}/ventureOS/_memory/venture-state.yaml">
|
|
78
78
|
Update: completed_artifacts (business-model-canvas, pricing-model, monetisation-plan), guiding_questions.design_business
|
|
79
79
|
</state-update>
|
|
80
80
|
</step>
|
|
@@ -14,12 +14,12 @@ installed_path: "{project-root}/ventureOS/workflows/6-design-business/business-m
|
|
|
14
14
|
instructions: "{installed_path}/instructions.xml"
|
|
15
15
|
|
|
16
16
|
templates:
|
|
17
|
-
- "{project-root}/ventureOS/
|
|
18
|
-
- "{project-root}/ventureOS/
|
|
19
|
-
- "{project-root}/ventureOS/
|
|
17
|
+
- "{project-root}/ventureOS/templates/business-model-canvas.md"
|
|
18
|
+
- "{project-root}/ventureOS/templates/pricing-model.md"
|
|
19
|
+
- "{project-root}/ventureOS/templates/monetisation-plan.md"
|
|
20
20
|
|
|
21
21
|
data:
|
|
22
|
-
brainstorming: "{project-root}/ventureOS/
|
|
22
|
+
brainstorming: "{project-root}/ventureOS/techniques/brainstorming-techniques.csv"
|
|
23
23
|
|
|
24
24
|
tags:
|
|
25
25
|
- business-model
|
|
@@ -12,8 +12,8 @@ Simulate the full NVB final gate review. The Venture Evaluator acts as the NVB p
|
|
|
12
12
|
Load:
|
|
13
13
|
- `pitch/pitch-deck.md` — the final deck
|
|
14
14
|
- ALL completed artifacts from venture-state.yaml
|
|
15
|
-
- `{project-root}/ventureOS/
|
|
16
|
-
- `{project-root}/ventureOS/
|
|
15
|
+
- `{project-root}/ventureOS/scoring/gate-rubric.yaml` — full rubric (all 7 criteria + weights)
|
|
16
|
+
- `{project-root}/ventureOS/scoring/pivot-triggers.yaml` — if pivot is needed
|
|
17
17
|
|
|
18
18
|
The Venture Evaluator simulates a 5-person NVB panel:
|
|
19
19
|
1. **NVB Chair** — overall investment thesis
|
|
@@ -9,8 +9,8 @@
|
|
|
9
9
|
<title>Load Venture State</title>
|
|
10
10
|
<instructions>
|
|
11
11
|
Load and parse:
|
|
12
|
-
1. {project-root}/ventureOS/_memory/venture-
|
|
13
|
-
2. {project-root}/ventureOS/_memory/
|
|
12
|
+
1. {project-root}/ventureOS/_memory/venture-state.yaml
|
|
13
|
+
2. {project-root}/ventureOS/_memory/pivot-history.yaml
|
|
14
14
|
3. {project-root}/ventureOS/config.yaml (for venture_name, user_name)
|
|
15
15
|
</instructions>
|
|
16
16
|
</step>
|