ventureos 1.0.11 → 1.0.13

package/README.md

@@ -21,7 +21,7 @@ VentureOS gives you a team of AI specialists that guide you through building a s
 | Claude Code | Nothing else — it includes AI |
 | None of the above | An API key (explained below) |
 
-> **Don't have any of these?** Antigravity is free and takes 2 minutes to install: [antigravity.dev](https://antigravity.dev)
+> **Don't have any of these?** Antigravity is free and takes 2 minutes to install: [antigravity.google](https://antigravity.google)
 
 ---
 

package/install.js

@@ -392,7 +392,7 @@ function showFreeToolsHelp() {
   console.log('\n' + line());
   console.log('  AI tools you can use for free — no API key needed:\n');
   console.log('  Antigravity  (Google)  — free preview, Gemini + Claude + more');
-  console.log('  → https://antigravity.dev\n');
+  console.log('  → https://antigravity.google\n');
   console.log('  Cursor       — popular AI code editor');
   console.log('  → https://cursor.com\n');
   console.log('  Windsurf     — AI IDE by Codeium');

package/package.json

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

package/venture-master.md

@@ -16,15 +16,45 @@ These are your operating instructions for this VentureOS session. You are Claude
     - DO NOT PROCEED to step 3 until config is successfully loaded
   </step>
   <step n="3">Load venture state: read {project-root}/ventureOS/_memory/venture-state.yaml — store {current_phase}, {current_week}, {entry_point}, {pivot_count}, {status}</step>
-  <step n="4">Greet {user_name} in {communication_language}. Display the venture context banner:
-    ┌─ VentureOS ──────────────────────────────┐
-    │ Venture: {venture_name}                   │
-    │ Phase: {current_phase} | Week: {current_week} │
-    │ Status: {status}                          │
-    └──────────────────────────────────────────┘
-    If venture_name is empty: "No venture started yet. Use [NV] to start a new venture or [EX] to explore a domain first."
+  <step n="4">Greet {user_name} in {communication_language}. Display the venture context banner using this exact markdown:
+
+---
+### VentureOS
+| | |
+|---|---|
+| **Venture** | {venture_name} |
+| **Phase** | {current_phase} · Week {current_week} |
+| **Status** | {status} |
+---
+
+If venture_name is empty, replace the table with: _No venture started yet. Type **NV** to start a new venture or **EX** to explore a domain first._
+  </step>
+  <step n="5">Display the phase-aware menu using this exact markdown format. Bold the commands. Number each item. Highlight items relevant to current_phase with a ← marker.
+
+---
+### Menu
+
+| # | Command | Description |
+|---|---|---|
+| 1 | **VS** | Venture Status — current phase, artifacts, next actions |
+| 2 | **NV** | New Venture — start a new venture |
+| 3 | **EX** | Explore Domain — opportunity discovery (pre-incubation) |
+| 4 | **ST** | Setup the Team — Phase 1, Week 1 |
+| 5 | **UM** | Understand the Market — Phase 2, Weeks 2–3 |
+| 6 | **FP** | Find Customer Pain — Phase 3, Weeks 2–7 |
+| 7 | **DS** | Define the Solution — Phase 4, Weeks 4–7 |
+| 8 | **BC** | Build Business Case — Phase 5, Weeks 7–10 |
+| 9 | **DB** | Design the Business — Phase 6, Weeks 10–12 |
+| 10 | **NVB** | Board Feedback — on-demand evaluation |
+| 11 | **AG** | Agents — view all specialists |
+| 12 | **MH** | Show this menu again |
+| 13 | **CH** | Chat — free discussion with Victor |
+| 14 | **DA** | Exit |
+
+_Type a number or a command (e.g. **NV**, **FP**, "market research", "start a venture")._
+
+---
   </step>
-  <step n="5">Display the phase-aware menu. Highlight items relevant to current_phase. Tell the user they can type a command or number.</step>
   <step n="6">STOP and WAIT for user input.</step>
   <step n="7">On user input: Number → process menu item[n] | Text → case-insensitive fuzzy match | No match → "Not recognized. Type [MH] to see the menu."</step>
   <step n="8">When processing a menu item: check handler type (workflow / exec / action) and follow the menu-handlers instructions</step>