{"id":"business-brainstorm","name":"business-brainstorm","summary":"新しいビジネスや製品、サイドプロジェクトを連続創業者のフィルターに照らしてプレッシャーテストしたい場合。","body":"# /business-brainstorm — Pressure-test a business idea\n\nTakes 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).\n\n## Step 1 — Capture the idea\n\nGet from the user:\n- The idea in 1–2 sentences (the *what*)\n- The reason it's on their mind (the *why now*)\n- Any starting context (a chat where this came up, a tweet that inspired it, a problem they've hit)\n\nIf 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.\n\nIf the idea is too vague to score, ask 1–2 clarifying questions and stop. Don't pad the brief with assumptions.\n\n## Step 2 — Load the framework + personal overlay\n\nRead `references/framework.md` — the user's filter. Apply each dimension in order.\n\nAlso 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.\n\n## Step 3 — Score each dimension\n\nFor each of the 9 dimensions in `framework.md`, give a 1-line take + a verdict (✅ strong / 🟡 OK / ❌ weak / ❓ unknown — needs research).\n\nDon't BS the unknowns. Mark them ❓ and route to deep-research in Step 4.\n\n## Step 4 — Trigger research where needed (optional)\n\nIf 2+ dimensions are ❓ unknown, offer the user: *\"Want me to run `/deep-research` on [topic] before scoring?\"*\n\nUseful research targets:\n- Market size / who pays signal → `/last30days <space>` + `WebSearch`\n- Competitive landscape → search for \"alternatives to X\", \"X vs Y\" pages\n- ICP signal → forums / Reddit / X where the audience hangs out\n- Pricing benchmarks → look at competitor pricing pages\n\nIf the user says yes, run `Skill({skill: \"deep-research\", args: \"<topic>\"})` and incorporate the brief.\n\n## Step 5 — Check the .com\n\nAlways 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.\n\nIf naming is wide open, brainstorm 5–10 candidate names through `/domain` and report which are available.\n\n## Step 6 — Output the brief\n\nUse this template:\n\n```markdown\n# Business brainstorm: <name or idea slug>\n\n**Date:** <YYYY-MM-DD>\n**Idea:** <1–2 sentences>\n**Why now:** <1 sentence>\n\n## Verdict\n**Build** / **Sleep on it** / **Pass** / **Steal an angle for [existing property]**\n\n<2–3 sentence rationale>\n\n## Score\n\n| Dimension | Take | Verdict |\n|---|---|---|\n| 1. Problem | … | ✅ |\n| 2. Audience | … | 🟡 |\n| 3. Wedge | … | ❓ |\n| 4. Monetization | … | ✅ |\n| 5. Moat | … | ❌ |\n| 6. Portfolio fit | … | ✅ |\n| 7. Distribution | … | ✅ |\n| 8. Energy fit | … | 🟡 |\n| 9. Opportunity cost | … | ❌ |\n\n## Domain\n- <name>.com — available / taken / aftermarket $<price>\n- (other candidates if relevant)\n\n## Research applied\n- <link to deep-research brief in ~/.config/makerskills/deep-research/archive/, if run>\n\n## Open questions\n- <what would change the verdict>\n\n## If you build it (sketch)\n- **First 100 customers:** <how>\n- **Wedge offer:** <what>\n- **Price:** <range>\n- **MVP scope:** <1–3 features>\n\n## If you don't build it\n- **Angle to steal for existing properties:**\n  - Property A: …\n  - Property B: …\n  - Property C: …\n  - (etc., only where relevant)\n```\n\n## Step 7 — Archive\n\nArchives 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.\n\nWrite to `<archive dir>/<YYYY-MM-DD>-<slug>.md`. Append to `<archive dir>/INDEX.md` (create if missing):\n\n```markdown\n- 2026-06-16 — [<idea>](./<filename>.md) — **<verdict>** — <one-line rationale>\n```\n\n## Step 8 — Surface\n\nShow the brief in chat. Tell the user the archive path. Offer:\n- *\"Want to push to Notion as a positioning canvas?\"*\n- *\"Want me to scaffold a project repo / landing page?\"* (if verdict = Build)\n- *\"Want me to revisit in 30 days?\"* (if verdict = Sleep on it)\n\n## Composes with\n\n- `deep-research` — for market validation when dimensions are ❓\n- `/domain` — for .com availability and naming brainstorm\n- `/last30days` — for audience/market recency signal (via deep-research)\n- Memory (`project_*.md`) — for portfolio context (don't pitch an idea that already exists)\n\n## Notes on quality\n\n- **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.\n- **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.\n- **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.\n- **Archive every brief, even Kills.** Killed ideas resurface — the brief with rationale prevents re-litigating. The archive dir + INDEX.md makes revisit trivial.\n- **\"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.\n- **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.","author":"@coreyhaines31","ownerProfile":null,"authorContacts":null,"sourceUrl":"https://github.com/coreyhaines31/makerskills/tree/main/skills/business-brainstorm","license":"MIT","category":"testing","lang":"en","tokens":1540,"stars":0,"calls30d":1,"claimed":false,"visibility":"public","origin":"crawler","version":"0.1.0","createdAt":"2026-08-22","updatedAt":"2026-08-22","files":[{"path":"references/framework.md","size":5103,"sha256":"a55be3666c7d2e3a7184c732e44ce3008f750a34bed60b9fe2e42b302aca598c"}],"requires":{"mcp":[],"tools":[]},"safety":{"flags":[],"scannedAt":"2026-08-22","hasScripts":false,"networkEndpoints":[]}}