← ClaudeAtlas

business-reasoninglisted

Structured business judgment distilled from twelve canonical business books (The Lean Startup, Zero to One, Good to Great, The E-Myth Revisited, The 1-Page Marketing Plan, Blue Ocean Strategy, $100M Offers, The $100 Startup, The Psychology of Money, Atomic Habits, Rich Dad Poor Dad, Think and Grow Rich). Use this whenever the user asks anything about starting, validating, pricing, positioning, marketing, monetizing, scaling, systematizing, or rescuing a business, product, side project, SaaS, app or freelance practice — including casual phrasings like "is this a good idea", "would anyone pay for this", "how do I get users", "how should I price this", "why is nobody buying", "should I build X or Y", "which of my projects should I focus on", "should I quit my job for this", or "how do I turn this into a business". Trigger it even when no framework is named, even when the question sounds like a request for a quick opinion, and even when it arrives inside a coding task.
pavlelausevic/business-reasoning · ★ 0 · AI & Automation · score 67
Install: claude install-skill pavlelausevic/business-reasoning
# Business Reasoning A diagnostic operating system for business questions, distilled from twelve widely-read business books. It is independent synthesis and commentary — the frameworks are named and attributed, never reproduced. Point users to the originals for the full argument. ## Why this exists The default failure mode when an AI is asked a business question is to produce a fluent, comprehensive, agreeable plan: market overview, target personas, revenue streams, a marketing funnel, a 12-month roadmap. It reads like value. It is almost always worthless, because nothing in it can be wrong. Every claim is unfalsifiable, every number invented, every risk hedged. This replaces "produce a plan" with **"produce a decision"**. A decision has: a fact base, an explicitly named riskiest assumption, a cheap test that could kill it, and a stated criterion for what would change your mind. ## Operating rules **1. Fact base before advice.** Before recommending anything, sort what you have into three buckets and show them: - **KNOWN** — things the user has stated or that are verifiable - **ASSUMED** — things you or the user are treating as true without evidence (the dangerous bucket; label every one) - **UNKNOWN** — things nobody in the conversation knows and that matter If the ASSUMED bucket carries the whole recommendation, say so before giving the recommendation. **2. Name the riskiest assumption, then the cheapest test that could falsify it.** Not the most important assumptio