business-brainstorm

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

/business-brainstorm — Pressure-test a business idea

/business-brainstorm — 商业想法压力测试

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

接收模糊的想法，通过用户的评估标准进行分析，输出结构化的可行性简报。可与

deep-research

（用于市场调研）和

/domain

（用于命名）配合使用。

Step 1 — Capture the idea

步骤1 — 收集想法

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.

向用户获取：

用1-2句话描述想法（即「是什么」）
这个想法产生的缘由（即「为什么是现在」）
任何初始背景信息（比如产生这个想法的聊天记录、启发你的推文、你遇到的某个问题）

如果用户指向过往的聊天/文档，先加载该内容。记忆库中包含针对进行中项目的

project_*.md

文件——在假设想法是全新的之前，先检查这些文件。

如果想法过于模糊无法评分，提出1-2个澄清问题后停止。不要用假设内容填充简报。

Step 2 — Load the framework + personal overlay

步骤2 — 加载框架+个性化覆盖内容

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.

读取

references/framework.md

——这是用户的评估标准。按顺序应用每个维度。

同时尝试加载

${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/business-brainstorm/portfolio.local.md

（如果存在）——用户会在此文件中列出其实际运营中的业务、资产、受众和合作伙伴。若文件存在，在评估「业务组合适配」、「获客渠道」和「机会成本」维度时，使用该文件中的信息，而非让用户逐一说明。

Step 3 — Score each dimension

步骤3 — 为每个维度评分

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.

针对

framework.md

中的9个维度，给出1句话的评估结论+判定结果（✅ 优秀 / 🟡 合格 / ❌ 薄弱 / ❓ 未知 — 需要调研）。

不要对未知内容敷衍。标记为❓并在步骤4中转向深度调研。

Step 4 — Trigger research where needed (optional)

步骤4 — 按需触发调研（可选）

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.

如果有2个及以上维度标记为❓未知，向用户提议：「是否需要我针对[主题]运行
/deep-research
后再评分？」

有用的调研方向：

市场规模/付费信号 →
```
/last30days <space>
```
+
```
WebSearch
```
竞争格局 → 搜索「alternatives to X」、「X vs Y」相关页面
核心受众信号 → 受众聚集的论坛/Reddit/X平台
定价基准 → 查看竞品的定价页面

如果用户同意，运行

Skill({skill: "deep-research", args: "<topic>"})

并将调研简报纳入分析。

Step 5 — Check the .com

步骤5 — 检查.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.

始终针对备选名称运行

/domain

工具。一个完美的想法但域名要花费5万美元，不如一个B级想法但拥有免费的.com域名。

如果命名空间较大，通过

/domain

工具头脑风暴5-10个候选名称，并报告哪些可用。

Step 6 — Output the brief

步骤6 — 输出简报

Use this template:

markdown

undefined

使用以下模板：

markdown

undefined

Business brainstorm: <name or idea slug>

商业头脑风暴：<名称或想法缩写>

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

日期: <YYYY-MM-DD> 想法: <1-2句话> 为什么是现在: <1句话>

Verdict

判定结果

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

<2–3 sentence rationale>

打造 / 搁置 / 放弃 / 为[现有业务]借鉴某个切入点

<2-3句话的理由>

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	…	❌

维度	评估结论	判定结果
1. 问题	…	✅
2. 受众	…	🟡
3. 切入点	…	❓
4. 变现模式	…	✅
5. 护城河	…	❌
6. 业务组合适配	…	✅
7. 获客渠道	…	✅
8. 精力适配	…	🟡
9. 机会成本	…	❌

Domain

域名情况

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

<name>.com — 可用/已被注册/ aftermarket $<price> -（其他相关候选名称）

Research applied

已应用的调研内容

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

<若运行了调研，此处为~/.config/makerskills/deep-research/archive/中的深度调研简报链接>

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>

前100位客户: <获取方式>
切入点方案: <具体内容>
定价: <范围>
MVP范围: <1-3个功能>

If you don't build it

若决定放弃

Angle to steal for existing properties:
- Property A: …
- Property B: …
- Property C: …
- (etc., only where relevant)

undefined

可为现有业务借鉴的切入点:
- 业务A: …
- 业务B: …
- 业务C: … -（其他相关业务）

undefined

Step 7 — Archive

步骤7 — 归档

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>

归档文件存储在

${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/business-brainstorm/archive/

目录（若目录不存在则创建）。绝不要将归档文件写入技能自身的文件夹——技能安装和升级会从源端同步并清除该文件夹中的所有保存内容。迁移说明: 如果该技能文件夹中包含旧的

references/ideas-archive/

目录及用户条目，请先将这些文件移动到归档目录中。

写入文件至

<归档目录>/<YYYY-MM-DD>-<slug>.md

。并将内容追加至

<归档目录>/INDEX.md

（若不存在则创建）：

markdown

- 2026-06-16 — [<想法>](./<文件名>.md) — **<判定结果>** — <一句话理由>

Step 8 — Surface

步骤8 — 展示结果

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)

在聊天中展示简报。告知用户归档路径。提供以下选项：

「是否需要将其推送至Notion作为定位画布？」
「是否需要我搭建项目仓库/着陆页？」（若判定结果为「打造」）
「是否需要我在30天后重新评估？」（若判定结果为「搁置」）

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)

```
deep-research
```
— 当维度标记为❓时用于市场验证
```
/domain
```
— 用于.com域名可用性查询和命名头脑风暴
```
/last30days
```
— 用于获取受众/市场的近期信号（通过deep-research）
Memory (
```
project_*.md
```
) — 用于业务组合背景检查（不要提出已存在的想法）

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.

九个维度，而非单一关键指标。 即使其他维度得分很高，某个维度的隐性缺陷也会导致想法失败。必须对每个维度进行评分——不允许出现「之后再解决」的敷衍。
判定结果需明确：打造/搁置/放弃。 不能是「也许」。判定结果的模糊性会导致执行中的不确定性，而简报的存在就是为了避免这种情况。
业务组合背景检查必不可少。 在撰写简报前，搜索记忆库+知识库，查看是否与现有业务存在重叠。如果新想法与某个现有业务的重合度达80%，建议扩展现有业务而非创建新业务——这样的成本仅为新业务的1/4，复利效应更强。
归档所有简报，包括「放弃」的想法。 被放弃的想法可能会重新出现——带有理由的简报可避免重复评估。归档目录+INDEX.md让重新评估变得简单。
「借鉴切入点」部分可从「放弃」的想法中挖掘价值。 即使你不会打造某个想法，它通常也包含可改进现有业务的切入点。不要跳过这一部分——这是「放弃」判定结果中价值最高的输出。
对「搁置」的想法进行30天后重新评估。 设置日历提醒。未被重新评估的搁置想法会成为归档中的无效内容；重新评估的想法会在更完善的背景下重新浮现。