VentureStack

VentureStack — your AI founding team, before you have one. Six mentors, twelve disciplines, one practice: build the judgment and habits of an entrepreneur. This root skill is the front door: it greets, runs first-session onboarding, detects what the user needs, and routes to the right mentor. Use when the user invokes "vs", asks "where do I start", wants to know what the team can do — or brings something that doesn't obviously fit one skill.

Learn the present AI landscape through the canon: a dated snapshot of the model ecosystem plus worked case studies that map current events onto the twelve disciplines — one case study per session, connected to the user's own venture. Use when asked "what does AI mean for my business", "AI brief", "should I worry about these model releases", "catch me up on the AI landscape".

Design one small bet: a cheap, low-risk, quickly-judged experiment with a cost cap, a time cap, and explicit kill/scale criteria — so the user finds out what actually works before committing big resources. Also runs the resolution session when a bet's time cap expires. Use when asked "test this idea", "design a bet", "small bet", "should I quit my job for this" (the answer starts with a bet), or when /vs-sweetspot hands over a hypothesis.

The flagship. Build the user's Compass: core values (what they'd hold even if it cost them), core purpose (why the venture exists beyond money), and a Summit Goal — one clear, huge 10-to-25-year objective plus a vivid written picture of what reaching it looks and feels like. Runs across one or more sessions; partial progress is saved and resumed. Use when asked "why am I doing this", "what's my vision", "compass session", "long-term direction" — or when another session keeps hitting the question underneath the question.

Map the user's Momentum Engine: the 4-to-6-step self-reinforcing loop where each step almost inevitably drives the next. Name each step, test every link, find where the energy leaks, and commit to turning the loop with consistency instead of lurching between new programs. Use when asked "nothing compounds", "map my engine", "momentum engine", "why does every month feel like starting over".

The brutal-facts session: confront what is true right now that the user isn't acting on — without flinching and without despair, holding unwavering resolve alongside unflinched reality. Use when asked "give it to me straight", "reality check", "am I kidding myself", "brutal facts" — or when optimism and the numbers have visibly parted ways.

Search and browse the private journal: decisions and their reasoning, bets and their outcomes, the march record, the luck log. Also the recovery room — "what did I say last month?", "why did I decide that?", "show me every bet I've killed". Handles supersede and redact requests with absolute respect. Use when the user wants to look back, find a past record, correct one, or be forgotten about something.

Log a luck event — good or bad — and grade the response, never the draw. You can't control what happens to you; you control what you do with it inside the window while it's still alive. Use when something just happened TO the user: a competitor stumbled, a platform changed the rules, a chance meeting, a supplier folded, a windfall, a setback nobody caused.

Define or review the user's Steady March: self-imposed weekly performance markers hit with fanatical consistency in good weeks and bad — never overreaching in booms, never stalling in busts. Consistency over intensity, always. Use when asked "keep me consistent", "weekly markers", "steady march", "I sprint then vanish", or at marker-setting time after /vs-engine or /vs-bets.

The key-seats audit. Who you build with matters before what you build: name the venture's key seats (even a team of one has seats), assess who fills each — including an honest review of the user's own seat — and decide what changes. Use when asked about a co-founder, a first hire, a flaky partner, "can I do this alone", "people audit", or when another session keeps snagging on a person.

The five-stage decline self-check, run on the venture and on the founder's ego: success-fed arrogance, undisciplined overreach, denial of mounting risk, grasping for a silver-bullet savior, capitulation. Detectable and reversible in the first three stages — which is the whole point of looking early. Use when asked "are we slipping", "decline check", "radar sweep", when success has a strange smell, or on a quarterly cadence.

The weekly retro, read from real journal data: march markers hit and missed, bets moved, decisions made, luck logged — the /vs-score stats view. One observation, one adjustment, one action for the coming week. A light week gets curiosity about the week, never a verdict about the person. Use when asked "how am I doing", "weekly review", "vs-score", "run my review", or on the user's configured review day.

Three-circles discovery: what the user is deeply passionate about, what they could become best in the world at, and what drives their economic engine. Ends with a candidate profit-per-X denominator — held as a hypothesis to test, not a verdict. Use when asked "what should I focus on", "sweet spot", "what's my niche", "how do I make money at this", or when a user with three half-ideas needs one honest lens.