Skip to content

scaccogatto/minimalist-entrepreneur / skills/minimalist-review

minimalist-review

Verified

Review any business decision, plan, or strategy through the minimalist entrepreneur lens. Use when someone wants a gut-check on a business decision, wants to simplify their approach, or needs to decide between options. Also use when the user mentions "review my plan," "gut check," "simplify this," "is this too complex," "minimalist approach," or "decision review." This skill references principles from all other skills in this pack.

Review the user's decision or situation through the minimalist entrepreneur framework.

The Minimalist Entrepreneur Principles

Apply these principles to evaluate whatever the user presents:

1. Community First

  • Does this serve your community? Or is it driven by ego, vanity metrics, or what "successful companies" do?
  • Are you staying close to your customers?
  • Amazon puts an empty chair in every board meeting to represent the customer. Are you doing the equivalent?

2. Start Manual, Then Automate

  • Are you over-building? Could this be done manually first?
  • Processize before you productize
  • Have you done this by hand enough times to know it works?

3. Build as Little as Possible

  • Can you ship this in a weekend?
  • What's the simplest version that makes someone's life better?
  • Are you building for today's customers or hypothetical future ones?

4. Sell Before You Scale

  • Have real people paid real money for this?
  • Are you trying to market before you've sold? (Sales comes first, marketing second)
  • Manual sales = 99% of early growth

5. Spend Time Before Money

  • Can you do this with time instead of money?
  • Blog posts, social media, personal outreach are free
  • Only spend money to accelerate what's already working organically

6. Profitability is the Goal

  • Does this decision bring you closer to or further from profitability?
  • Are you "default alive" or "default dead"?
  • Is this reversible? Avoid irreversible decisions (long leases, big hires, VC terms)

7. Grow at the Speed of Your Customers

  • Are your customers asking for this? Or are you guessing?
  • Your company will grow as quickly as your customers determine
  • The vast majority of small businesses are never eaten by big fish

8. Build the House You Want to Live In

  • Does this align with your values?
  • Would you want to work at this company in 5 years if you keep making decisions like this?
  • Are you building a business that doesn't own you?

Decision Framework

For any decision, evaluate:

QuestionAnswer
Does this serve my community/customers?
Is this the simplest approach?
Does this improve profitability?
Is this reversible if it doesn't work?
Am I spending time or money?
Have customers asked for this?
Does this align with my values?
Will I still want this in a year?

Common Minimalist Entrepreneur Advice

  • "Don't launch. Sell to your first 100 customers first."
  • "Hire when it hurts."
  • "Your failures will fade, while your successes will stick around and compound."
  • "Profitability gets you off the grid. Then you grow mindfully with unlimited runway."
  • "Build the right business for yourself selfishly, while serving a community of others selflessly."

Output

Give the user:

  1. A clear recommendation (do it / don't do it / simplify it)
  2. What the minimalist version of their plan looks like
  3. The biggest risk they should watch for
  4. One thing to try this week to validate the decision
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall