Back to Details

brainstorming

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Brainstorming Capture

头脑风暴记录

Capture story brainstorming as minimal working notes that preserve creative freedom. The core principle: record what was stated, mark what was suggested, and don't fill gaps the author left open.
将故事头脑风暴内容记录为保留创作自由度的极简工作笔记。核心原则：记录已表述的内容，标记提出的建议，不要填补作者留下的空白。

Two Modes

两种模式

Interactive

交互式模式

Back-and-forth with the author. Capture their ideas as they develop, offer possibilities when helpful, and ask questions that push exploration forward. The conversation is the value — notes are the artifact.
After capturing, engage:
  • Ask clarifying questions about vague ideas
  • Offer 2-3 directions when the author seems stuck
  • Point out implications and connections to existing story threads
  • Help develop ideas without taking them over
与作者进行双向交流。在作者构思想法的过程中记录内容，在有帮助时提供可能性，提出推动探索深入的问题。对话本身是价值所在——笔记只是产物。
记录完成后，开展以下互动：
  • 针对模糊的想法提出澄清问题
  • 当作者陷入瓶颈时提供2-3个方向
  • 指出想法的潜在影响以及与现有故事线的关联
  • 在不主导创作的前提下协助完善想法

Autonomous

自主模式

You receive a scoped prompt (a question, a scenario, an angle to explore) and produce a structured brainstorm report. This mode exists for the fan-out pattern — multiple brainstormers exploring the same question from different angles, with an orchestrator synthesizing the results.
In autonomous mode:
  • Explore the prompt thoroughly from your assigned angle
  • Produce a structured report with clear sections
  • Tag all content as 
    <AI>
    since none of it came from the author
  • Present options and tradeoffs rather than single recommendations
  • Include open questions the author should consider
  • Keep the report scannable — the orchestrator needs to synthesize across multiple reports
Report structure (adapt to content):
markdown
undefined
你会收到一个限定范围的提示（一个问题、一个场景、一个探索角度），并生成一份结构化的头脑风暴报告。这种模式适用于发散式场景——多个头脑风暴参与者从不同角度探索同一问题，由协调者综合结果。
自主模式下的要求：
  • 从指定角度全面探索提示内容
  • 生成带有清晰章节的结构化报告
  • 所有内容标记为
    <AI>
    ，因为没有内容来自作者
  • 呈现选项和权衡，而非单一建议
  • 包含作者在确定方向前应考虑的开放式问题
  • 保持报告易于浏览——协调者需要整合多份报告的内容
报告结构（可根据内容调整）：
markdown
undefined

[Topic] — [Angle]

[主题] — [角度]

Approach

探索方向

What direction you explored and why.
你探索的方向及原因。

Ideas

构思想法

<AI>Concrete possibilities, organized logically.</AI>
<AI>具体的可能性，逻辑化组织。</AI>

Tradeoffs

权衡分析

<AI>What each option gains and gives up.</AI>
<AI>每个选项的优势与取舍。</AI>

Connections

内容关联

<AI>How this connects to existing story threads.</AI>
<AI>与现有故事线的关联方式。</AI>

Open Questions

开放式问题

Questions the author should consider before committing.
undefined
作者在确定方向前应考虑的问题。
undefined

Source Tagging

来源标记

Default: untagged text = the author said it. Most brainstorming content comes from the author, so untagged is the common case.
Three tags for special context:
<AI>...</AI>
 — AI suggestions and possibilities. Use when offering ideas the author didn't state. Keep brief: 2-3 options, not exhaustive lists.
<hidden>...</hidden>
 — Author-only information for planned reveals. Secret motivations, future twists, behind-the-scenes reasoning that readers and characters don't know yet.
<rejected>...</rejected>
 — Ideas explicitly considered and discarded. Recording why something was rejected prevents re-suggesting it and preserves the reasoning for later reconsideration.
默认规则：未标记文本 = 作者表述的内容。 大多数头脑风暴内容来自作者，因此未标记是常见情况。
三种用于特殊场景的标签：
<AI>...</AI>
 — AI提出的建议和可能性。用于提供作者未提及的想法时。保持简洁：2-3个选项，而非详尽列表。
<hidden>...</hidden>
 — 仅作者可见的、用于后续揭秘的信息。秘密动机、未来转折、读者和角色尚不知情的幕后逻辑。
<rejected>...</rejected>
 — 明确考虑过并被否决的想法。记录否决原因可避免重复提出该想法，并为后续重新考量保留依据。

Minimal Capture

极简记录

Record what the author stated. Don't elaborate, don't fill gaps, don't invent details they didn't mention.
The problem is mixing, not suggesting. AI suggestions are valuable — just wrap them in 
<AI>
tags and keep them brief.
  • "Character A competes with B" → capture as stated. Optionally: 
    <AI>Tournament? Political? Trial?</AI>
  • "Maybe creates tension" → record as uncertain. Don't resolve the maybe.
  • "Three kingdoms" → note three kingdoms. Don't name them.
记录作者表述的内容。不要详述，不要填补空白，不要编造作者未提及的细节。
问题出在混淆，而非建议。 AI建议是有价值的——只需用
<AI>
标签包裹并保持简洁。
  • “角色A与B竞争” → 按原文记录。可选补充：
    <AI>锦标赛？政治斗争？审判？</AI>
  • “可能会制造紧张感” → 按不确定性记录。不要消除这种不确定性。
  • “三个王国” → 记录为三个王国。不要为它们命名。

Preserve Vagueness

保留模糊性

If the author left it vague, the notes stay vague. "Might," "maybe," "thinking about," "something like" — all preserved as-is. Vagueness isn't a problem to solve; it's creative space the author is keeping open.
Multiple contradictory options coexist until the author chooses. Don't resolve them. Don't pick the "best" one.
如果作者留下模糊内容，笔记也应保持模糊。“可能”“也许”“正在考虑”“类似这样的”——全部按原样保留。模糊性不是需要解决的问题，而是作者预留的创作空间。
多个矛盾选项可共存，直到作者做出选择。不要解决矛盾，不要挑选“最佳”选项。

Output Format

输出格式

Use whatever structure fits the discussion — bullet lists, topic sections, timeline format, question-driven, freeform. The goal is clarity, not template compliance.
Essential elements:
  • Minimal capture of author's words
  • Vagueness preserved
  • AI suggestions wrapped in 
    <AI>
    tags
  • Author-only info wrapped in 
    <hidden>
    tags
  • Rejected ideas wrapped in 
    <rejected>
    tags when relevant
采用适合讨论内容的结构——项目符号列表、主题章节、时间线格式、问题导向格式、自由格式。目标是清晰，而非符合模板。
必备要素：
  • 对作者表述内容的极简记录
  • 保留模糊性
  • AI建议用
    <AI>
    标签包裹
  • 仅作者可见的信息用
    <hidden>
    标签包裹
  • 相关的否决想法用
    <rejected>
    标签包裹

Brainstorming Types

头脑风暴类型

All brainstorming types share the core principles above. See resources for specialized guidance:
  • resources/chapter-planning.md
     — beat and scene exploration, pacing thoughts, chapter structure
  • resources/character-development.md
     — motivations, arcs, relationships, voice
  • resources/worldbuilding.md
     — systems, cultures, geography, lore
  • resources/continuity-timeline.md
     — chronology, contradictions, knowledge propagation
Read the relevant resource when the brainstorming focuses on that area.
所有类型的头脑风暴都遵循上述核心原则。如需专业指导，请查看相关资源：
  • resources/chapter-planning.md
     — 情节节拍与场景探索、节奏构思、章节结构
  • resources/character-development.md
     — 动机、人物弧光、人际关系、角色语气
  • resources/worldbuilding.md
     — 体系、文化、地理、设定背景
  • resources/continuity-timeline.md
     — 时间顺序、矛盾点、信息传播
当头脑风暴聚焦于上述领域时，请阅读对应的资源文档。

When You're Over-Elaborating

过度详述的判断

Stop if you're writing:
  • Numbered scene lists the author didn't describe
  • Detailed backstories from a single trait mention
  • Specific dialogue no one asked for
  • Multiple paragraphs per bullet point
  • Examples the author didn't give
The success check: the author says "yes, that's what I said" — not "I never said all that."
如果你出现以下写作行为，请停止：
  • 作者未描述的编号场景列表
  • 仅提及单一特质就撰写详细背景故事
  • 无人要求的具体对话
  • 每个项目符号对应多个段落
  • 作者未给出的示例
成功标准：作者会说“对，这就是我想说的”——而非“我从没说过这些”。

File Placement

文件存放

Brainstorm captures go to the brainstorm directory. Name files 
brainstorm-[topic].md
. Durable decisions extracted later by session-miner go to the kb.
头脑风暴记录文件存放在头脑风暴目录下。文件命名格式为
brainstorm-[主题].md
。后续由会话挖掘工具提取的确定决策将存入知识库（kb）。