coreyhaines31/makerskills / skills/business-brainstorm
business-brainstorm
VerifiedWhen you want to pressure-test a potential new business, product, or side project against the serial-founder filter. Not "marketing ideas for a product" (that's marketing-skills:marketing-ideas) β this is "should this business exist + can you win it." Runs the idea through a structured framework (problem, audience, wedge, monetization, moat, portfolio fit, distribution, energy fit, opportunity cost), checks domain availability via /domain, optionally triggers /deep-research for market validation, and outputs a viability brief: build / sleep on it / pass. Archives every idea to ~/.config/makerskills/business-brainstorm/archive/ so past work is searchable. Triggers on "/business-brainstorm," "/brainstorm," "new business idea," "should I build X," "pressure test this idea," "validate this idea," "is X a good business," "what about a [type] for [audience]."
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.8 KB |
| references/framework.md | markdown | 6.6 KB |
references/framework.md
View on GitHub# Business brainstorm framework
the user's serial-founder filter. Run an idea through each dimension. Verdict per dimension: β
strong / π‘ OK / β weak / β unknown β needs research.
---
## 1. Problem
Is the pain real, frequent, and acute?
- **β
Strong:** People are already paying for half-solutions, building workarounds, or complaining publicly. Quantifiable cost (time / money / risk).
- **π‘ OK:** Real pain, but mild or rare.
- **β Weak:** "It would be nice ifβ¦" β vitamin, not painkiller.
---
## 2. Audience
Who has this problem, and can the user reach them?
- **β
Strong:** Audience the user already talks to (SaaS founders, technical marketers, agency owners) OR a tight niche they can break into cheaply.
- **π‘ OK:** Adjacent audience β would take work but feasible.
- **β Weak:** Cold audience with no existing access (e.g., enterprise CIOs).
Check: is this audience already in one of your existing property reaches? If yes, distribution is half-solved.
---
## 3. Wedge
How do you get the first 100 customers?
- **β
Strong:** Clear, concrete first-customer playbook. "I'd email 50 founders I know," "I'd post on r/SaaS," "I'd add this to my newsletter thank-you page."
- **π‘ OK:** Plausible path but needs a few experiments.
- **β Weak:** "We'll do paid ads" / "We'll do SEO" β too vague, too long-tail.
---
## 4. Monetization
Who pays, how much, how often?
- **β
Strong:** Clear price band ($20 / $50 / $200 / $2k MRR), known willingness to pay (proven by competitors charging similar), recurring or repeated revenue.
- **π‘ OK:** Reasonable price assumption but unproven.
- **β Weak:** Free-with-ads, or "we'll figure out monetization later."
---
## 5. Moat
Why is this hard to copy? Why won't bigger players crush it?
Assume code costs close to nothing: a competitor reaches feature parity in months, and a customer can have an agent build the three features they actually use. Check which moats could hold, each with its test question:
- **Buyers know and trust you:** who would build a business or career around recommending this?
- **System of record:** what couldn't a leaving customer take with them?
- **Allowed to act:** does it move the money or send the message, or only advise?
- **Nobody checks your work:** would customers trust the output without verifying it?
- **Someone official said yes:** what license or certification would a newcomer have to wait for?
- **Everyone's already in it:** would a competitor have to move a whole team or community at once?
- **Every customer makes it smarter:** does one customer's usage improve the product for the rest?
- **Hard to keep running:** what ops burden would a copycat refuse to carry?
Also check the demand side: will AI shrink the buyers (their own business replaced, fewer seats, an agent doing the user's job)?
- **β
Strong:** Distribution advantage (the user's audience), brand-as-moat (their name), or one of the moats above with a credible path to it in year one.
- **π‘ OK:** Some defensibility from a real choice a funded copycat wouldn't make (one narrow niche, shipping speed over polish, taste that visibly shows in the output β not just "good taste").
- **β Weak:** Pure execution play any well-funded team, or the customer's own agent, could replicate in months. Unique features, clever code and a long integrations list don't count anymore.
Note: the user's moats are usually *audience + voice + speed*, not tech. Whatever is easy for them to enter is easy for everyone, so the realistic play is stacking: audience to enter a niche, then system of record, then a learning loop. Honest scoring. Sources: Rob Walling's "The Only SaaS Moats Left in 2026" (MicroConf) and Idea Browser's Fable 5.2 moats post. For an app's product-level moat plan, see **product-manager** (`references/defensibility.md`).
---
## 6. Portfolio fit
Does this complement or cannibalize the existing 6 properties?
- **β
Complements:** Audience overlap that boosts existing properties (e.g., a tool for one of your existing audiences that drives newsletter subs).
- **π‘ Neutral:** Different audience, no interference.
- **β Cannibalizes:** Competes with an existing property for attention, splits the audience, or muddies positioning. Or it's so similar to an existing property it should be a feature, not a standalone.
Check memory's `project_*.md` files β does this idea overlap with any in-flight projects? If yes, ask: should this be a feature of one of those?
---
## 7. Distribution
Which of the user's audience assets can launch this?
- **β
Strong:** Direct fit with your existing newsletter, blog, podcast, product users, or social following.
- **π‘ OK:** Adjacent audience β could launch with partner collabs or paid push.
- **β Weak:** Requires building a new audience from zero. (Possible but slow β usually means it should wait until an existing property reaches it.)
---
## 8. Energy fit
Does the user actually want to build and run this for 2+ years?
- **β
Strong:** Genuinely interested, plays to strengths (writing, marketing, design taste, audience), and isn't already burned out on the space.
- **π‘ OK:** Interesting but not exciting. Probably needs a co-founder or strong operator.
- **β Weak:** Interesting on paper, dread in the gut. Pass.
INTJ honesty: if it requires constant context-switching, heavy sales motion, or babysitting customers β flag the energy cost.
---
## 9. Opportunity cost
What does the user NOT do if they do this?
- **β
Strong:** Marginal capacity used (e.g., 4 hrs/week of the user + Claude). Doesn't crowd out existing businesses or in-flight builds.
- **π‘ OK:** Real time investment but bounded.
- **β Weak:** Would require pulling focus from an existing business, slowing a live property, or pausing other in-flight projects.
The honest test: would adding this make the user *less* effective on the things that are already working? If yes, the bar is much higher.
---
## Scoring rubric β Verdict
Sum the verdicts:
- **5+ β
and no β on Problem / Audience / Distribution / Energy** β **Build** (those four are non-negotiable)
- **3β4 β
with 1β2 β** β **Sleep on it** (revisit in 30 days; sometimes ideas mature)
- **β on Problem OR Energy** β **Pass** (no point fighting these)
- **β on Portfolio fit (cannibalizes)** β **Steal an angle for the existing property** instead of building new
- **3+ β (unknowns)** β run `/deep-research` first, then re-score
## Iterate me
This filter is a starting point. Refine the weights and add dimensions as the user learns what actually predicted their own wins/losses. Especially: revisit after the next 2β3 brainstorms to see if any dimension was a load-bearing miss.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |