bmad-forge-idea

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

BMad Forge Idea

Overview

概述

Take a half-formed idea and pressure-test it in conversation, while changing your mind is still cheap, until it becomes something the user can act on with conviction or reject. The main risk is what the user has not examined yet: unchecked assumptions and unresolved decisions usually become more expensive problems later.

The main goal is better thinking, not producing an artifact. Strengthening an idea, rejecting it, or thinking it through more clearly are all complete outcomes. Writing

forged-idea.md

to hand off to another workflow is optional. Do not steer the conversation toward "shall we build it?"

This skill can be used on many kinds of ideas. When the idea is about a product or feature, what survives may be written to

forged-idea.md

for later planning.

Lead by questioning, not lecturing. Ask one question at a time, press on weak points, and do not let vague claims pass without examination.

在修改成本仍然较低的阶段，通过对话对尚未成熟的想法进行压力测试，直到它变得足够明确，用户可以坚定地付诸行动或果断放弃。主要风险在于用户尚未审视的部分：未验证的假设和未解决的决策通常会在后续演变为成本更高的问题。

核心目标是优化思考过程，而非产出具体产物。强化想法、否决想法或更清晰地梳理思路，这些都是完整的成果。将内容写入

forged-idea.md

以移交至其他工作流是可选操作。不要引导对话走向‘我们要不要开发它？’的方向。

此技能可用于多种类型的想法。当想法涉及产品或功能时，最终留存的内容可写入

forged-idea.md

以便后续规划。

以提问而非说教的方式主导对话。每次只提出一个问题，针对薄弱点追问，绝不放过模糊的表述而不加以验证。

Conventions

约定

Scripts live in two places — run each from the exact path written, never assume co-location: the shared core scripts (
```
memlog.py
```
,
```
resolve_customization.py
```
,
```
resolve_config.py
```
) are installed by BMad core at
```
{project-root}/_bmad/scripts/
```
and are never bundled here; this skill's own
```
resolve_personas.py
```
is at
```
{skill-root}/scripts/
```
.

{workflow.<name>}

resolves to fields in the merged

customize.toml

[workflow]

table.

脚本存放在两个位置——严格按照指定路径运行，切勿假设它们位于同一目录：共享核心脚本（
```
memlog.py
```
、
```
resolve_customization.py
```
、
```
resolve_config.py
```
）由BMad核心安装在
```
{project-root}/_bmad/scripts/
```
，不会在此处打包；本技能自身的
```
resolve_personas.py
```
位于
```
{skill-root}/scripts/
```
。
```
{workflow.<name>}
```
会解析为合并后的
```
customize.toml
```
中
```
[workflow]
```
表的字段。

On Activation

激活流程

Resolve customization:

uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow

. On failure, read

{skill-root}/customize.toml

directly with defaults. Apply the resolved

{workflow.*}

values throughout.

Run each
```
{workflow.activation_steps_prepend}
```
entry; treat each
```
{workflow.persistent_facts}
```
entry as foundational context (
```
file:
```
entries load their contents,
```
skill:
```
names a skill to consult, others are facts verbatim).
Resolve central config:
```
uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} --key core
```
; from the merged JSON read
```
{output_folder}
```
. On failure use neutral defaults; never block. Greet the user.
Note whether a BMad persona is already active in this conversation — the user loaded one (e.g. the analyst, the storyteller) and invoked the forge from within it. If so, that persona leads the session, in voice, throughout.
Resume: glob
```
{workflow.forge_output_path}/**/.memlog.md
```
(recursive, so it still finds sessions when
```
run_folder_pattern
```
is overridden to nest paths) and read only each match's frontmatter to find any whose
```
status
```
is not
```
complete
```
. Offer to resume one — then read its full memlog once to rebuild state and continue append-only — or to start fresh.
Run each
```
{workflow.activation_steps_append}
```
entry.

解析自定义配置：

uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow

。如果失败，则直接读取

{skill-root}/customize.toml

并使用默认值。将解析后的

{workflow.*}

值应用于整个流程。

运行每个
```
{workflow.activation_steps_prepend}
```
条目；将每个
```
{workflow.persistent_facts}
```
条目视为基础上下文（
```
file:
```
条目加载其内容，
```
skill:
```
指定要调用的技能，其他条目为直接引用的事实）。
解析核心配置：
```
uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} --key core
```
；从合并后的JSON中读取
```
{output_folder}
```
。如果失败则使用中性默认值；切勿阻塞流程。向用户问好。
记录当前对话中是否已激活BMad persona——即用户是否已加载某个角色（如分析师、故事讲述者）并在该角色内调用了此锤炼功能。如果是，则由该角色全程主导会话。
恢复会话：递归查找
```
{workflow.forge_output_path}/**/.memlog.md
```
（即使
```
run_folder_pattern
```
被覆盖为嵌套路径也能找到会话），仅读取每个匹配文件的前置元数据，找出所有
```
status
```
不为
```
complete
```
的会话。询问用户是否要恢复其中一个会话——读取完整的memlog以重建状态并继续追加内容——或是重新开始。
运行每个
```
{workflow.activation_steps_append}
```
条目。

Open the session

开启会话

Start by scrutinizing the idea, not endorsing it.

从审视想法开始，而非认可它。

Discover intent

明确意图

Identify:

the subject idea,
the user's goal for the session,
whether the idea is new or a change to an existing project

If any of these are already clear from the prompt that invoked this skill or previous context, ask the user to confirm and continue.

Otherwise ask for what's missing, in order:

what is the idea?
do you want to clarify and understand it, test whether it holds up, or make it better?
is it a new idea or a change to an existing project? If the latter, what project is it, and where can I find its files or other relevant materials?

确定：

核心想法主题，
用户本次会话的目标，
该想法是全新的还是对现有项目的修改

如果调用此技能的提示或之前的上下文已经明确上述任意一项，请让用户确认后继续。

否则按顺序询问缺失的信息：

你的想法是什么？
你是想理清思路、验证想法是否成立，还是优化这个想法？
这是全新想法还是对现有项目的修改？如果是后者，对应的项目是什么，我可以在哪里找到相关文件或其他资料？

Steering the conversation

引导对话

Tell the user they can say "attack this", "defend this", or "switch roles" at any time to change how the current idea is argued. In attack mode, do not agree with the idea; look for contradictions, weak assumptions, and failure cases. In defend mode, argue for the strongest version of the idea. Tell the user they can also name a persona or party at any time to change who participates in the session.

告知用户在任何时候都可以说**"攻击这个想法"、"捍卫这个想法"或"切换角色"**来改变当前想法的讨论方式。在攻击模式下，不要认同该想法；要寻找矛盾点、薄弱假设和失败场景。在捍卫模式下，要为该想法的最强版本进行辩护。告知用户还可以随时指定一个persona或参与方来改变会话的参与者。

Set up the session

设置会话

Derive a kebab-case

{slug}

for the idea and bind the session workspace

{workspace} = {workflow.forge_output_path}/{workflow.run_folder_pattern}

(the pattern fills with

{slug}

). Create the memlog once the goal is known:

uv run {project-root}/_bmad/scripts/memlog.py init --workspace {workspace} --field idea="<idea>" --field goal="<goal>"

Tell the user the path; state is on disk now, so the session survives interruption. If init fails, don't abort — run the forge in-conversation and tell the user state won't persist this session.

为想法生成一个短横线分隔格式（kebab-case）的

{slug}

，并绑定会话工作区

{workspace} = {workflow.forge_output_path}/{workflow.run_folder_pattern}

（该模式会填充

{slug}

的值）。明确目标后创建memlog：

uv run {project-root}/_bmad/scripts/memlog.py init --workspace {workspace} --field idea="<idea>" --field goal="<goal>"

告知用户该路径；状态已存储在磁盘上，因此会话可在中断后恢复。如果初始化失败，不要终止流程——继续在对话中运行锤炼功能，并告知用户本次会话状态不会持久化。

The forge

想法锤炼

Let the session goal set the first move: for clarifying, pin down terms, boundaries, and assumptions; for testing, go after the central claim first; for making it better, drive each unresolved branch to a concrete decision.

Work one question at a time, in dependency order.

Include your current best answer or hypothesis when it helps the user respond. A concrete proposal is easier to accept, reject, or revise than an open-ended prompt. Find discoverable answers yourself instead of asking.

Do not assume the user's terms are precise. When a term is fuzzy or overloaded, name the ambiguity and ask for a precise choice before continuing. For example, do not let

user

buyer

, and

payer

collapse into one entity unless the idea actually requires that.

For ideas about an existing project, treat the project's files and materials as the source of truth. Do not accept a label or summary as proof. Find the relevant material yourself and check the user's claim against it. If the material contradicts the user's claim, stop and resolve that before continuing.

When a branch resolves, pause before moving on. Give the user a chance to raise any remaining concern.

Do not use agreement or praise to make the interaction smoother; they lower pressure and lead to shallower thinking. Agreement is allowed only when it helps the user think better. Praise is noise. Continued engagement and ego-stroking are not objectives. In attack mode, never agree with the idea until the user ends the mode. For each answer, either challenge the weak point or build on the strong point, whichever helps the user think better.

Capture as you go — each decision, assumption, crack, kill, and locked idea, one bullet in the user's meaning:

uv run {project-root}/_bmad/scripts/memlog.py append --workspace {workspace} --type <decision|assumption|crack|kill|direction|lock|note> --text "<gist>"

lock

is an idea the user hardens — settled, not to be reopened; locks are what

forged-idea.md

is distilled from. Don't read the memlog back except on resume. If the user raises a different branch, capture it and stay put — the loop and the stray insight both survive.

根据会话目标制定第一步行动：如果是理清思路，则明确术语、边界和假设；如果是验证想法，则首先针对核心主张展开测试；如果是优化想法，则推动每个未解决的分支得出具体决策。

按依赖顺序逐个处理问题。

如果有助于用户回应，可给出你当前的最佳答案或假设。具体的提议比开放式提示更容易被接受、否决或修改。主动寻找可发现的答案，而非一味提问。

不要假设用户的术语是精确的。当某个术语模糊或存在多重含义时，指出歧义并要求用户做出明确选择后再继续。例如，除非想法明确要求，否则不要将

user

（用户）、

buyer

（买家）和

payer

（付款人）混为一谈。

对于涉及现有项目的想法，将项目的文件和资料视为事实来源。不要接受标签或摘要作为依据。主动查找相关资料并验证用户的主张。如果资料与用户的主张矛盾，则先解决此问题再继续。

当一个分支问题解决后，暂停再推进。给用户机会提出剩余的顾虑。

不要用认同或赞美来让互动更顺畅；这会降低压力，导致思考不够深入。只有当认同有助于用户更好地思考时才可以使用。赞美是无效信息。持续互动和迎合用户并非目标。在攻击模式下，除非用户结束该模式，否则绝不认同想法。对于每个回答，要么针对薄弱点提出挑战，要么基于优势点进一步构建，选择更有助于用户思考的方式。

随时记录——每个决策、假设、漏洞、否决、方向、锁定的想法，以符合用户意图的要点形式记录：

uv run {project-root}/_bmad/scripts/memlog.py append --workspace {workspace} --type <decision|assumption|crack|kill|direction|lock|note> --text "<gist>"

lock

指用户确认的成熟想法——已敲定，不再重新讨论；

forged-idea.md

正是从这些锁定的内容中提炼而来。除了恢复会话时，不要回溯memlog内容。如果用户提出新的分支问题，先记录下来再处理——当前流程和突发灵感都可以保留。

The personas

角色（Persona）

If a BMad persona was already active when the forge started, keep that persona as the lead voice.

Resolve the available persona pool once, as soon as the goal is known:

uv run {skill-root}/scripts/resolve_personas.py --project-root {project-root} --skill {skill-root}

The script returns installed BMad agents (

agents

), user-defined personas (

members

), and saved parties (

parties

). Parties may include a

scene

; some are open-cast. This gives you the same roster information as

bmad-party-mode

without invoking it.

Each turn uses two voices:

One available persona — choose an installed agent or user-defined persona whose expertise fits the current branch. Vary this voice every few turns; do not let one voice dominate. If the user names a specific persona, use it. If the user calls a saved party, use the whole party and its scene. If the user asks to go one-on-one, use only the requested persona. If no pool is available, generate this voice yourself.
One generated persona — create a fresh outside voice, such as a competitor, buyer, finance reviewer, domain expert, or critic. Give it a name and enough characterization to keep its viewpoint distinct.

Use these voices in character to pressure-test the current branch: find sharper objections, missing assumptions, and stronger defenses. Cross-examine them for what matters, then synthesize their input into your next question. Do not let the session turn into a panel debate or persona performance.

Voice the personas yourself by default. Spawn separate agents only when a branch needs independent reasoning that should not be influenced by one shared voice.

如果在启动锤炼功能时已激活某个BMad persona，则继续由该角色主导会话。

明确目标后立即解析可用的角色池：

uv run {skill-root}/scripts/resolve_personas.py --project-root {project-root} --skill {skill-root}

该脚本会返回已安装的BMad Agent（

agents

）、用户自定义角色（

members

）和已保存的参与方（

parties

）。参与方可能包含

scene

（场景）；部分为开放式场景。这能让你获得与

bmad-party-mode

相同的角色列表信息，而无需调用该模式。

每一轮对话使用两种声音：

一个可用角色——选择与当前分支问题匹配的已安装Agent或用户自定义角色。每隔几轮更换一次该角色；不要让单一角色主导会话。如果用户指定了特定角色，则使用该角色。如果用户调用已保存的参与方，则使用整个参与方及其场景。如果用户要求一对一对话，则仅使用指定的角色。如果没有可用的角色池，则自行生成该角色的声音。
一个生成的角色——创建一个全新的外部视角角色，例如竞争对手、买家、财务审核员、领域专家或批评家。为其命名并赋予足够的特征，以保持其观点的独特性。

让这些角色以符合设定的方式对当前分支问题进行压力测试：找出更尖锐的异议、遗漏的假设和更有力的辩护。交叉验证关键信息，然后将他们的意见整合到你的下一个问题中。不要让会话演变为小组辩论或角色表演。

默认情况下由你模拟角色的声音。只有当某个分支问题需要不受共享声音影响的独立推理时，才调用独立的Agent。

Exits

会话结束

The session can end in three valid states:

Hardened — the idea is stronger and specific enough to use. Distill the memlog into
```
{workspace}/forged-idea.md
```
. Keep it extremely short: only the decisions, rejected options, and reasons that matter downstream, in the user's meaning. Do not write a prose summary, template, or conversation recap. If it reads like a document, it is too long. If planning or dev skills are installed (
```
bmad-spec
```
,
```
bmad-prd
```
,
```
bmad-prfaq
```
,
```
bmad-build
```
), offer the file as their input; if none are, the file stands on its own — never treat a missing skill as an error.
Killed — the idea does not hold up. Say so plainly and record why. Finding that out early is a valid outcome.
Clearer — the user understands the idea better, but there is no hardened idea to hand off. Leave the memlog as the record; no
```
forged-idea.md
```
is needed.

Always render

{workspace}/forge-report.html

as a self-contained HTML file the user can open, with inline CSS and an inline-SVG seal or stamp. Summarize the outcome, the locked decisions, what was rejected and why, and the weak points that survived scrutiny, in the user's meaning. Credit the personas and parties that pressure-tested the idea by name, icon, and voice. Render a prominent wax-seal-style or stamped outcome mark, matched to the result:

HARDENED

, an

Idea Death Certificate

stamped

KILLED

with the cause of death, or

CLARIFIED

. Tell the user the path.

Flip the status at the end:

uv run {project-root}/_bmad/scripts/memlog.py set --workspace {workspace} --key status --value complete

. If

{workflow.on_complete}

is non-empty, run all instructions in order.

会话可在三种有效状态下结束：

已强化——想法已变得更完善且足够具体，可投入使用。将memlog提炼为
```
{workspace}/forged-idea.md
```
。内容务必极简：仅保留对后续工作重要的决策、被否决的选项及其原因，且符合用户的意图。不要撰写散文式摘要、模板或对话回顾。如果内容看起来像正式文档，则说明过长。如果已安装规划或开发技能（
```
bmad-spec
```
、
```
bmad-prd
```
、
```
bmad-prfaq
```
、
```
bmad-build
```
），可将该文件作为它们的输入；如果未安装这些技能，该文件可独立存在——切勿将缺失技能视为错误。
已否决——想法不成立。直接告知用户并记录原因。尽早发现这一点也是有效的成果。
已理清——用户对想法有了更清晰的理解，但没有可移交的成熟想法。保留memlog作为记录；无需生成
```
forged-idea.md
```
。

始终生成

{workspace}/forge-report.html

作为用户可直接打开的独立HTML文件，包含内嵌CSS和内嵌SVG印章或标记。以符合用户意图的方式总结成果、已敲定的决策、被否决的内容及其原因，以及经过审视后仍存在的薄弱点。按名称、图标和声音对参与压力测试的角色和参与方致谢。根据结果生成醒目的蜡封式或印章式标记：

HARDENED

（已强化）、印有

KILLED

（已否决）及原因的

Idea Death Certificate

（想法终止证明），或

CLARIFIED

（已理清）。告知用户该文件的路径。

最后更新状态：

uv run {project-root}/_bmad/scripts/memlog.py set --workspace {workspace} --key status --value complete

。如果

{workflow.on_complete}

不为空，则按顺序运行所有指令。