# business-brainstorm

Adopt this skill: https://proskills.md/skills/other/coreyhaines31-makerskills-skills-business-brainstorm

Page: https://proskills.md/skills/other/coreyhaines31-makerskills-skills-business-brainstorm
This document is the public skill bundle for that page. It contains SKILL.md and every helper file the catalog carries. No login is required.

## File: skills/business-brainstorm/SKILL.md
size: 7017
upstream: https://github.com/coreyhaines31/makerskills/blob/main/skills/business-brainstorm/SKILL.md

````text
---
name: business-brainstorm
description: "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].\""
metadata:
  version: 0.2.0
---

# /business-brainstorm — Pressure-test a business idea

Takes 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).

## Step 1 — Capture the idea

Get from the user:
- The idea in 1–2 sentences (the *what*)
- The reason it's on their mind (the *why now*)
- Any starting context (a chat where this came up, a tweet that inspired it, a problem they've hit)

If 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.

If the idea is too vague to score, ask 1–2 clarifying questions and stop. Don't pad the brief with assumptions.

## Step 2 — Load the framework + personal overlay

Read `references/framework.md` — the user's filter. Apply each dimension in order.

Also try to load `${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/business-brainstorm/portfolio.local.md` if it exists — this is where the user lists their real in-flight businesses, properties, audiences, and partners. When present, use it for the "portfolio fit," "distribution," and "opportunity cost" dimensions instead of asking the user to name each one.

## Step 3 — Score each dimension

For each of the 9 dimensions in `framework.md`, give a 1-line take + a verdict (✅ strong / 🟡 OK / ❌ weak / ❓ unknown — needs research).

Don't BS the unknowns. Mark them ❓ and route to deep-research in Step 4.

## Step 4 — Trigger research where needed (optional)

If 2+ dimensions are ❓ unknown, offer the user: *"Want me to run `/deep-research` on [topic] before scoring?"*

Useful research targets:
- Market size / who pays signal → `/last30days <space>` + `WebSearch`
- Competitive landscape → search for "alternatives to X", "X vs Y" pages
- ICP signal → forums / Reddit / X where the audience hangs out
- Pricing benchmarks → look at competitor pricing pages

If the user says yes, run `Skill({skill: "deep-research", args: "<topic>"})` and incorporate the brief.

## Step 5 — Check the .com

Always run `/domain` on the working name(s). A perfect idea with a $50k domain is a worse idea than a B+ idea with a free .com.

If naming is wide open, brainstorm 5–10 candidate names through `/domain` and report which are available.

## Step 6 — Output the brief

Use this template:

```markdown
# Business brainstorm: <name or idea slug>

**Date:** <YYYY-MM-DD>
**Idea:** <1–2 sentences>
**Why now:** <1 sentence>

## Verdict
**Build** / **Sleep on it** / **Pass** / **Steal an angle for [existing property]**

<2–3 sentence rationale>

## Score

| Dimension | Take | Verdict |
|---|---|---|
| 1. Problem | … | ✅ |
| 2. Audience | … | 🟡 |
| 3. Wedge | … | ❓ |
| 4. Monetization | … | ✅ |
| 5. Moat | … | ❌ |
| 6. Portfolio fit | … | ✅ |
| 7. Distribution | … | ✅ |
| 8. Energy fit | … | 🟡 |
| 9. Opportunity cost | … | ❌ |

## Domain
- <name>.com — available / taken / aftermarket $<price>
- (other candidates if relevant)

## Research applied
- <link to deep-research brief in ~/.config/makerskills/deep-research/archive/, if run>

## Open questions
- <what would change the verdict>

## If you build it (sketch)
- **First 100 customers:** <how>
- **Wedge offer:** <what>
- **Price:** <range>
- **MVP scope:** <1–3 features>

## If you don't build it
- **Angle to steal for existing properties:**
  - Property A: …
  - Property B: …
  - Property C: …
  - (etc., only where relevant)
```

## Step 7 — Archive

Archives live in `${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/business-brainstorm/archive/` (create the directory if missing). Never write archives inside the skill's own folder — skill installs and upgrades re-sync from source and wipe anything saved there. **Migration:** if this skill's folder contains an old `references/ideas-archive/` with user entries, move those files into the archive directory first.

Write to `<archive dir>/<YYYY-MM-DD>-<slug>.md`. Append to `<archive dir>/INDEX.md` (create if missing):

```markdown
- 2026-06-16 — [<idea>](./<filename>.md) — **<verdict>** — <one-line rationale>
```

## Step 8 — Surface

Show the brief in chat. Tell the user the archive path. Offer:
- *"Want to push to Notion as a positioning canvas?"*
- *"Want me to scaffold a project repo / landing page?"* (if verdict = Build)
- *"Want me to revisit in 30 days?"* (if verdict = Sleep on it)

## Composes with

- `deep-research` — for market validation when dimensions are ❓
- `/domain` — for .com availability and naming brainstorm
- `/last30days` — for audience/market recency signal (via deep-research)
- Memory (`project_*.md`) — for portfolio context (don't pitch an idea that already exists)

## Notes on quality

- **Nine dimensions, not one hero metric.** Ideas fail because one dimension quietly rots even when the rest score high. Force each dimension to be scored — no "we'll figure that out later" cop-outs.
- **Verdict discipline: Ship / Sleep on it / Kill.** Not "maybe." Ambiguity in the verdict compounds into ambiguity in the commit; the brief exists to prevent that.
- **Portfolio-context check is non-negotiable.** Before writing, grep memory + wiki for existing property overlap. If the new idea is 80% one of your existing properties, propose extending the existing property instead of forking a new one — 4x cheaper to compound.
- **Archive every brief, even Kills.** Killed ideas resurface — the brief with rationale prevents re-litigating. The archive dir + INDEX.md makes revisit trivial.
- **"Angle to steal" section forces value from Kills.** Even ideas you won't build often have an angle that improves an existing property. Don't skip this section — it's the highest-leverage output of a Kill verdict.
- **30-day revisit for "Sleep on it."** Set the calendar reminder. Sleep-on-it ideas that never get revisited become dead weight in the archive; ideas that get revisited resurface with better context.
````

## File: README.md
upstream: https://github.com/coreyhaines31/makerskills/blob/main/README.md

````text
# makerskills

[![Stars](https://img.shields.io/github/stars/coreyhaines31/makerskills?style=flat-square&label=stars&color=000)](https://github.com/coreyhaines31/makerskills/stargazers) [![Release](https://img.shields.io/github/v/release/coreyhaines31/makerskills?style=flat-square&color=000)](https://github.com/coreyhaines31/makerskills/releases) [![License](https://img.shields.io/badge/license-MIT-000?style=flat-square)](./LICENSE)

**AI agent skills for the personal operator's craft.** Decisions, research, second-brain workflows, content rotation, scenario modeling, CFO cadence, domain hunts, and the meta-skills to author more.

Built for founders and indie operators. Works with [Claude Code](https://claude.ai/code), Codex, Cursor, and other Agent Skills hosts.

**Site:** [maker-skills.com](https://maker-skills.com)

---

## Install

```bash
# In Claude Code
/plugin marketplace add coreyhaines31/makerskills
/plugin install makerskills@makerskills
```

Or symlink for local dev:

```bash
git clone https://github.com/coreyhaines31/makerskills ~/code/makerskills
ln -s ~/code/makerskills ~/.claude/plugins/makerskills
```

See [INSTALL.md](./INSTALL.md) for env vars, personal-config setup, and runtime dependencies.

---

## Getting started — 5-minute path

New to the plugin? Do these in order. Everything else can wait until you need it.

**1. Install the plugin** (above), then set the base env var in `~/.zshenv`:

```bash
export MAKERSKILLS_CONFIG="$HOME/.config/makerskills"
```

Reload your shell.

**2. Run your first skill — start with `decide`.** No config required:

```
/decide
```

It'll ask what decision you're facing, pick the right questions from the 37signals framework, and archive the result with a revisit date. **That's the first-touch experience**: any skill in this plugin. Structured input → structured output → written to disk.

**3. Read one SKILL.md** to see the pattern:

```bash
open ~/code/makerskills/skills/decide/SKILL.md
```

Each skill is a workflow doc — you can invoke via `/decide` OR read the SKILL.md and run the steps by hand. The plugin is documentation-first; the automation is a side effect.

**4. Try one more skill** that involves personal config, so you understand the pattern:

```
/paste twitter
```

It'll read your clipboard, strip formatting, warn if over 280 chars, and copy back the cleaned output. First invocation may prompt you to install `pbcopy`-adjacent deps if missing. No config file needed — this is a pure utility.

**5. Now branch out.** Skim [The 25 skills](#the-25-skills) below and pick one that maps to a workflow you're already doing manually. That's the highest-leverage adoption path.

---

## Which skill do I invoke when?

Routing table for common operator jobs. Match your intent → skill.

| I want to... | Skill |
|---|---|
| Think through a decision with a real fork | [`decide`](./skills/decide/SKILL.md) |
| Break through a wall ("this seems impossible") | [`unstuck`](./skills/unstuck/SKILL.md) |
| Get a board of famous founders to weigh in | [`maker-council`](./skills/maker-council/SKILL.md) |
| Pressure-test a new business or product idea | [`business-brainstorm`](./skills/business-brainstorm/SKILL.md) |
| Research a topic with citations | [`deep-research`](./skills/deep-research/SKILL.md) |
| Find an available `.com` for a new project | [`domain`](./skills/domain/SKILL.md) |
| Watch known sources daily and feed the good stuff into my brain | [`radar`](./skills/radar/SKILL.md) |
| Capture / query / lint my personal knowledge base | [`second-brain`](./skills/second-brain/SKILL.md) |
| Same but for a team-shared knowledge base | [`company-brain`](./skills/company-brain/SKILL.md) |
| Extract notes / highlights / summaries from a book | [`read-book`](./skills/read-book/SKILL.md) |
| Extract a transcript or key moments from a video | [`watch-video`](./skills/watch-video/SKILL.md) |
| Turn a call transcript or client message into issues + reply | [`ingest`](./skills/ingest/SKILL.md) |
| Hand a task to Codex / Gemini / another model, or get second opinions from several | [`castmate`](./skills/castmate/SKILL.md) |
| Fetch any social post by URL as structured data | [`social-fetch`](./skills/social-fetch/SKILL.md) |
| Plan / draft social content rotation across a portfolio | [`jab-hook`](./skills/jab-hook/SKILL.md) |
| Draft, update, convert, or export a slide deck | [`slide-deck`](./skills/slide-deck/SKILL.md) |
| Clean terminal output for Slack / LinkedIn / X / Notion etc. | [`paste`](./skills/paste/SKILL.md) |
| Manage projects across businesses (kanban) | [`project-manager`](./skills/project-manager/SKILL.md) |
| Model personal financial scenarios (house, cash flow, etc.) | [`personal-cfo`](./skills/personal-cfo/SKILL.md) |
| Run monthly / weekly CFO for a company or agency | [`company-cfo`](./skills/company-cfo/SKILL.md) |
| Plan, build, check, or audit an app (incl. after a new model ships) | [`product-manager`](./skills/product-manager/SKILL.md) |
| Cut GitHub Actions minutes and CI wait time | [`ci-audit`](./skills/ci-audit/SKILL.md) |
| Create, adapt, or update a skill | [`skillify`](./skills/skillify/SKILL.md) |
| Wire up an integration / API / MCP into a project | [`toolify`](./skills/toolify/SKILL.md) |
| Set up an agent loop or scheduled task | [`loopify`](./skills/loopify/SKILL.md) |

Not sure between two? The **skill's SKILL.md description** always includes trigger phrases and disambiguation from adjacent skills.

---

## The 25 skills

### Meta — extend Claude Code (the `-ify` trifecta)
| Skill | What |
|---|---|
| [`skillify`](./skills/skillify/SKILL.md) | Create, adapt, or update a skill in any sibling repo. Three modes: CREATE (from-chat / from-video / from-dump / from-scratch), ADAPT (port external skill with license check + attribution), UPDATE (improve existing skills with cross-skill propagation + semver discipline), TEST (role-play users through a skill and judge transcripts against a rubric). |
| [`toolify`](./skills/toolify/SKILL.md) | Wire up an integration, API, MCP server, or third-party service into a Next.js or Rails project. Interactive wizard for auth, env vars, client wrapper, webhook handling, and smoke-test. |
| [`loopify`](./skills/loopify/SKILL.md) | Set up an agent loop, cron-scheduled task, or recurring workflow. Judgment layer on top of `ScheduleWakeup` / `CronCreate` / `/loop` — picks pattern (dynamic / cron / one-shot), tunes delay for cache windows, enforces idempotency + bail-out conditions. |

### Decision & strategy
| Skill | What |
|---|---|
| [`decide`](./skills/decide/SKILL.md) | 37signals decision framework (38 questions + house additions like Q39 opportunity cost, triaged to 6–8 per decision). Archives with revisit dates. |
| [`business-brainstorm`](./skills/business-brainstorm/SKILL.md) | Pressure-test a new business or product on 9 dimensions. Composes with `deep-research` + `domain`. |
| [`domain`](./skills/domain/SKILL.md) | 11-step .com domain hunt on Laura Roeder's "availability-first, never fall in love with a name" methodology. Multi-tool ensemble: Vercel CLI + whois (per-TLD) + Domainr API + Namecheap API + `rdap.org` (modern TLDs) + `agent-browser` for USPTO trademark screening + aftermarket click-throughs (HugeDomains / Afternic / Sedo / Dan). Handles bare-word + prefix/suffix brainstorming, budget filtering, negotiation guidance, and social handle checks. |
| [`deep-research`](./skills/deep-research/SKILL.md) | Multi-source research with citations + archive. WebSearch, WebFetch, `agent-browser`, `/last30days`, memory. |
| [`unstuck`](./skills/unstuck/SKILL.md) | The roadblock antidote. Classifies what kind of "no" you hit (assumption / framing / gatekeeper / tool / resource / physics), runs targeted lateral-thinking techniques from a 10-technique inventory, 10-angle minimum before evaluating. Agents run it on themselves before reporting any dead end. Upstream of `decide`. |
| [`maker-council`](./skills/maker-council/SKILL.md) | Simulated personal boa
````
