This skill should be used when the user asks about "pitch deck", "fundraising story", "investor pitch", "VC narrative", "pitch narrative", "fundraising deck", "pitch structure", "Sequoia format", "why now slide", "market size slide", "TAM SAM SOM", "earned secret", "value hypothesis", "product-market fit"…
This skill should be used when the user asks about "investor update", "board deck", "board meeting", "investor communication", "monthly update", "quarterly update", "investor email", "bad news investors", "pivot communication", "crisis communication investors", "investor ask", "warm intro", "VC relationship"…
A rule of thumb that asks whether a small number of causes produce most of the results. The “80/20 rule” is an approximate pattern, not a fixed mathematical law.
A structured way to understand problems as connected systems rather than isolated events. It examines feedback loops, delays, and how changes in one part affect the whole.
Diagnoses the buyer/seller deadlock in any trade of information — the buyer cannot value what they cannot see, but once they see it they have it for free — and selects the disclosure mechanism (patent, NDA, staged disclosure, trusted intermediary + escrow, reputation, or proxy demonstration) that lets the buyer…
Activate when: user asks 'how do we stop competing on price?', 'what new market can we create?', 'is there a way to differentiate and cut costs at the same time?', describes an industry where all competitors look identical and margins are eroding, or a team is choosing a market entry angle to avoid head-to-head…
Activate when: scoping or quoting a new tax engagement; a client describes a transaction and you need to place it; building a document request list; sanity-checking that a return has the schedules its facts imply; user says 'what forms does this need', 'which schedule', 'what do I file for', 'is there a form for'…
First-principles assumption auditor. Deconstructs any decision or belief into irreducible premises, classifies each assumption (fact / convention / belief / interest-driven), ranks them by fragility × impact, and rebuilds conclusions from verified ground truth. Bilingual: responds in the user's language (Chinese or…
Use when approaching ANY task - bugs, features, refactoring, debugging, code review, architecture decisions. Enforces decomposition to fundamental truths before acting, prevents pattern-matching shortcuts and assumption-driven solutions.
Seven-stage Magnum Opus engineering workflow for project transformation. Alchemy applied to software: Calcinate, Dissolve, Separate, Conjoin, Ferment, Distill, Coagulate. Use for fundamental change (post-acquisition, major version cuts, strategic pivots), not for routine refactoring.