Tooluck logoTooluck
SKILL.md

business-brainstorm

Agent skill fromcoreyhaines31/makerskills

When 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].\"

How to install business-brainstorm

install business-brainstorm
# install the makerskills pack with the skills CLI
npx skills add coreyhaines31/makerskills

# or add only this skill to Claude Code: copy the folder

skills/business-brainstorm/

# into

~/.claude/skills/business-brainstorm/ (all projects)

.claude/skills/business-brainstorm/ (one project)

skills/business-brainstorm/SKILL.md

MITFull file
1# /business-brainstorm — Pressure-test a business idea
2
3Takes a vague idea, runs it through the user's filter, and outputs a structured viability brief. Composes with `deep-research` (for market) and `/domain` (for naming).
4
5## Step 1 — Capture the idea
6
7Get from the user:
8- The idea in 1–2 sentences (the *what*)
9- The reason it's on their mind (the *why now*)
10- Any starting context (a chat where this came up, a tweet that inspired it, a problem they've hit)
11
12**Resume first.** Look in the archive dir (Step 7) for files whose first line starts with `<!-- in-progress`. If one matches this idea, offer to pick it up: read it, keep every settled score, and continue from the next unscored dimension.
13
14If they point at a past chat / doc, load it first. Memory has `project_*.md` files for in-flight projects — check there before assuming the idea is brand-new.
15
16If the idea is too vague to score, ask 1–2 clarifying questions and stop. Don't pad the brief with assumptions.
17
18Two more cases where scoring would be theater:
19- **Validation-seeking** ("just tell me it's good," "hype me up") — name it kindly: *"I'll run it, but a brief that can't say Pass is worthless. Still in?"* Proceed only on those terms.
20- **Already committed** (built, launched, money spent) — this isn't "should it exist" anymore. Offer `decide` for the next call (keep going / pivot / stop) instead.
21
22## Step 2 — Load the framework + personal overlay
23…

Excerpt shown under the repository's MIT license.

More skills in makerskills

Keep exploring

Similar skill repositories

Newsletter

Join the Community

Subscribe to our newsletter for the latest news and updates