ideakit

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

ideakit

Ideakit

Keep one ideas repo, one folder per idea, and think about exactly one of them at a time. ideakit captures an idea the moment it arrives, runs the discussion sessions, reports where every idea stands, dispatches the research and validation work to the kits that own it, and folds an answer back into that idea's own log when the user asks to keep it.

An idea is a subject someone wants to think about, not a project they have committed to building. Some ideas become products. Most stay notes, and that is the design.

Six modes.

capture

writes an idea down and stops.

session

is the mode that thinks.

status

reports and writes nothing.

research

and

validate

send a question out and bring the answer back.

close

records a verdict.

capture
and
close
write on their own. Every other mode offers its writes and takes no for an answer. See Saving is a demand, not a default.

维护一个创意仓库（ideas repo），每个创意对应一个文件夹，一次仅专注处理其中一个创意。Ideakit会在创意产生的瞬间记录下来，主持讨论会话，汇报每个创意的进展，将调研与验证工作分派给对应的工具包（kits），并在用户要求保存时将结果整合到该创意的专属日志中。

创意指的是某人想要思考的主题，而非已承诺要开发的项目。部分创意会转化为产品，但大多数仅作为笔记留存，这正是本工具的设计初衷。

六种模式。

capture

模式用于记录创意并停止操作。

session

是用于深度思考的模式。

status

模式仅汇报进展，不写入任何内容。

research

和

validate

模式会向外发送问题并带回答案。

close

模式用于记录最终结论。

capture
和
close
模式会自动写入内容。其余所有模式都会先展示拟写入的内容，用户可以选择拒绝保存。详见保存是主动需求，而非默认行为。

Mode selection

模式选择

Resolve on intent, not on phrasing.

"I have an idea", "capture this", "write this down" get
```
capture
```
. It records and stops.
"Let's think about X", "brainstorm X", "pick up the X idea" get
```
session
```
.
"Where do my ideas stand", "what should I think about next", "where was I on X" get
```
status
```
.
"Who else builds this", "which library would this need", "what does this category cost" get
```
research
```
.
"Is this a business", "would anyone pay for this", "should I build this" get
```
validate
```
.
"I'm dropping this", "I'm building this", "park this one" get
```
close
```
.

An ask that names no idea is
status
or
session
, never a guess between them.

status

reports every idea;

session

asks which one to open. When the ask wants a picture, run

status

. When the ask wants to think, run

session

and ask for the idea.

When the ask is genuinely ambiguous between

capture

and

session

, run

capture

first. A captured idea can always get a session next; a session on an unrecorded idea leaves nothing behind.

根据用户意图而非措辞来选择模式。

当用户说“我有一个创意”“记录这个”“写下来”时，触发
```
capture
```
模式，仅记录创意并停止操作。
当用户说“我们来思考X”“头脑风暴X”“继续X创意的讨论”时，触发
```
session
```
模式。
当用户说“我的创意进展如何”“接下来我该思考什么”“我之前在X创意上进展到哪了”时，触发
```
status
```
模式。
当用户说“还有谁在做这个”“这个需要用哪个库”“这类产品的成本是多少”时，触发
```
research
```
模式。
当用户说“这能做成一门生意吗”“有人会为此付费吗”“我应该开发这个吗”时，触发
```
validate
```
模式。
当用户说“我放弃这个创意”“我要开发这个”“先搁置这个创意”时，触发
```
close
```
模式。

若用户未指定具体创意，则触发
status
或
session
模式，绝不随意猜测。

status

模式会汇报所有创意的情况；

session

模式会询问用户要打开哪个创意。当用户想要了解整体情况时，触发

status

模式；当用户想要深入思考时，触发

session

模式并询问具体创意。

若用户的请求在

capture

和

session

模式之间存在歧义，优先触发

capture

模式。已记录的创意后续随时可以开启

session

模式；而针对未记录的创意开启

session

模式，结束后不会留下任何内容。

The ideas repo

创意仓库

All state lives in one repo outside the user's work repos, at

~/ideas

unless

$IDEAKIT_HOME

names somewhere else.

~/ideas/                            ← one git repo; $IDEAKIT_HOME overrides
  INDEX.md                          ← the router
  topics/<slug>/
    IDEA.md                         ← a stable head plus an ## Open block
    NOTES.md                        ← the dated log, append-only
    SOURCES.md                      ← collected links, created lazily
    docs/plans/                     ← a plan skill writes here
    docs/research/                  ← research answers, kept on request
    docs/validation/                ← validation write-ups, kept on request
    docs/sessions/                  ← full session records, on request only
    docs/adr/                       ← decision records
    assets/                         ← diagrams and screenshots

Resolve
$IDEAKIT_HOME
first and write absolute paths. No mode changes the working directory. A mode fired from a work repo touches no file in that repo, so the host repo's own conventions never apply to what ideakit writes. That is what lets an idea arriving mid-task go straight into the ideas repo.

Create the repo on first use and run

git init

in it. Never commit automatically. Offer a commit at the end of a session and take no for an answer.

所有状态都存储在用户工作仓库之外的一个独立仓库中，默认路径为

~/ideas

，若设置了

$IDEAKIT_HOME

环境变量则以该路径为准。

~/ideas/                            ← 一个git仓库；$IDEAKIT_HOME可覆盖默认路径
  INDEX.md                          ← 路由表
  topics/<slug>/
    IDEA.md                         ← 稳定的核心内容加上 ## Open 区块
    NOTES.md                        ← 按日期记录的日志，仅允许追加内容
    SOURCES.md                      ← 收集的链接，仅在首次需要时创建
    docs/plans/                     ← 计划类工具包会在此写入内容
    docs/research/                  ← 调研答案，仅在用户要求时留存
    docs/validation/                ← 验证报告，仅在用户要求时留存
    docs/sessions/                  ← 完整会话记录，仅在用户要求时生成
    docs/adr/                       ← 决策记录
    assets/                         ← 图表与截图

优先解析
$IDEAKIT_HOME
并使用绝对路径。任何模式都不会更改工作目录。从工作仓库触发的模式不会修改该仓库中的任何文件，因此宿主仓库的约定永远不会影响Ideakit的写入内容。这确保了在任务进行中产生的创意可以直接存入创意仓库。

首次使用时会自动创建仓库并在其中运行

git init

。绝不自动提交。 会话结束时会询问用户是否提交，用户可以选择拒绝。

The router

路由表

INDEX.md

carries one row per idea, with aliases, so a loose ask routes without opening anything:

markdown

| Idea | Slug | Also called | Summary | Open question | Status | Last touched |
|------|------|-------------|---------|---------------|--------|--------------|
| Agent memory substrate | `agent-memory` | memory layer, agent recall, context store | A shared store an agent writes facts to and reads back across sessions | Does retrieval beat a bigger window | active | 2026-08-19 |

Status is

active

building

parked

, or

closed

building

means implementation runs in another repo, and its cell carries that repo:

`building` · owner/repo

parked

means the user stopped.

closed

means a verdict is written in that idea's

NOTES.md

The router cell bound:
Summary
and
Open question
are one line each. Each states what the idea is and what is open. Neither carries a reason, a position, or a half-formed argument. A Markdown table gets read whole, so the isolation guard below cannot be kept by reading the router selectively; it is kept by bounding what the router is allowed to hold. Ten ideas then cost ten lines to route and nothing to contaminate.

INDEX.md

每行对应一个创意，包含别名，这样模糊的请求无需打开任何内容即可完成路由：

markdown

| Idea | Slug | Also called | Summary | Open question | Status | Last touched |
|------|------|-------------|---------|---------------|--------|--------------|
| Agent memory substrate | `agent-memory` | memory layer, agent recall, context store | A shared store an agent writes facts to and reads back across sessions | Does retrieval beat a bigger window | active | 2026-08-19 |

状态分为

active

（活跃）、

building

（开发中）、

parked

（已搁置）或

closed

（已关闭）。

building

意味着该创意的开发工作在另一个仓库中进行，对应单元格会显示该仓库路径：

`building` · owner/repo

。

parked

表示用户已停止推进该创意。

closed

表示该创意的最终结论已写入其

NOTES.md

文件。

路由表单元格限制：
Summary
和
Open question
均为单行内容。分别说明创意是什么，以及当前待解决的问题。两者均不得包含理由、立场或未成型的论点。Markdown表格会被整体读取，因此不能通过选择性读取路由表来遵守隔离规则，而是通过限制路由表允许存储的内容来实现。这样即使有10个创意，也仅需10行路由表内容，且不会产生内容污染。

Read one idea folder, never two

仅读取一个创意文件夹，绝不读取两个

This is the load-bearing rule. Read

INDEX.md

. Resolve the ask to exactly one slug. Then read only

topics/<slug>/

. Never glob across

topics/

, and never grep the repo for context. Listing

topics/

is fine, because listing a directory is not reading it.

Two reasons hold it up. Ideas contaminate each other: half-formed thinking about one subject bleeds into the next when both sit in the same window, and the second idea inherits the first one's framing without anyone noticing. And the cost grows the wrong way, because thirty ideas cost about thirty router lines to route and tens of thousands of tokens to open.

One bounded exception. Open a second topic folder only when the user names that idea in the ask ("does this connect to the agent memory idea?"). That folder is read-only for the session, and the connection is written into the primary idea's

NOTES.md

alone. One session, one owner of the log. When a link looks obvious and the user has not asked, say the link in one sentence and leave the folder shut.

这是核心规则。 读取

INDEX.md

，将用户请求解析为唯一的slug。然后仅读取

topics/<slug>/

目录下的内容。绝不遍历

topics/

目录，也绝不搜索仓库中的上下文内容。列出

topics/

目录是允许的，因为列出目录不属于读取操作。

这条规则有两个原因。创意之间会相互干扰：当两个主题同时出现在同一个窗口时，针对一个主题的未成型思考会渗透到另一个主题中，第二个主题会在不知不觉中继承第一个主题的框架。此外，若不遵守该规则，成本会不合理增长——30个创意仅需30行路由表内容，但如果全部打开则需要数万个token的处理量。

唯一的有限例外。 仅当用户在请求中明确提及另一个创意时（例如“这个创意和Agent memory创意有关联吗？”），才可以打开第二个主题文件夹。该文件夹在会话中为只读，关联内容仅写入主创意的

NOTES.md

文件中。一次会话仅能有一个日志所有者。当发现明显的关联但用户未提及，仅用一句话说明该关联即可，无需打开对应的文件夹。

The three topic files

三个主题文件

IDEA.md
is the living statement, in two parts. The head says what the idea is, who it is for, and what has to be true for it to matter. An

## Open

block below it lists the open questions and the possible next moves.

Rewrite the head when a session changed what the idea is. Draft a refreshed

## Open

block every session without exception, and save it with the entry it matches. That split gives a checkable bound: the
## Open
block matches the last
NOTES.md
entry. It also stops an inconclusive session churning the head for no change.

NOTES.md
is the log, and it is append-only. One

## YYYY-MM-DD

heading per saved session, recording what was decided, what was rejected and why, and the open question the session stopped on. Leave earlier entries alone; a change of mind gets a new dated entry. The log is the record and

IDEA.md

is a cache of it, so rewrite

IDEA.md

from

NOTES.md

when the two disagree.

SOURCES.md
collects links, one row per link with the date read and one line on what it settles. Create it on first use, not at capture. Check it before searching.

IDEA.md
是动态的创意说明文档，分为两部分。头部说明创意是什么、面向谁，以及创意成立的必要条件。下方的

## Open

区块列出当前待解决的问题和可能的下一步行动。

当会话改变了创意的核心定义时，重写头部内容。每次会话都必须重新起草

## Open

区块，并与对应的日志条目一起保存。这种拆分方式提供了可验证的边界：## Open
区块必须与最新的
NOTES.md
条目匹配。这也避免了无结论的会话无意义地修改头部内容。

NOTES.md
是日志文件，仅允许追加内容。每个已保存的会话对应一个

## YYYY-MM-DD

标题，记录已做出的决策、已拒绝的选项及原因，以及会话结束时待解决的问题。不得修改早期条目；想法变更需添加新的日期条目。日志是权威记录，

IDEA.md

是日志的缓存，因此当两者不一致时，需根据

NOTES.md

重写

IDEA.md

。

SOURCES.md
用于收集链接，每行对应一个链接，包含读取日期和一行关于该链接解决了什么问题的说明。仅在首次需要时创建该文件，而非在记录创意时创建。搜索前先检查该文件。

The router is a cache, so repair it

路由表是缓存，因此需要维护

Repair runs at two levels, and each mode repairs only what it can see.

Offer a topic's router row rewrite whenever a mode has that folder open and changed it, in the same save offer as the entry that changed it.
```
capture
```
and
```
close
```
write their row without asking.
Report an unregistered folder rather than opening it. A folder missing from the router needs five fields that live inside it, and reading it would break the guard for a bookkeeping errand. So
```
status
```
names the folder and says to run
```
session
```
on it to register it.

维护分为两个层面，每个模式仅维护其可见的内容。

当某个模式打开并修改了主题文件夹时，主动提出更新该主题的路由表行，与修改内容的保存请求一并提出。
```
capture
```
和
```
close
```
模式会直接写入路由表行，无需询问。
若发现未在路由表中注册的文件夹，仅汇报该文件夹，不打开它。 路由表中缺失的文件夹需要五个内部字段的信息，读取该文件夹会违反隔离规则，仅为了记账操作而这么做不值得。因此
```
status
```
模式会提及该文件夹，并提示用户运行
```
session
```
模式来注册它。

The slug is permanent

Slug 是永久不变的

A slug is short, lowercase, kebab-case, and taken from the idea's core noun. capture
proposes it and confirms it with the user before creating anything, because no mode renames a folder afterwards. The cost lands once at creation instead of in rename machinery for a rare event. The router's

Idea

column carries the current human name and stays free to change.

Slug 是简短的小写短横线分隔格式，取自创意的核心名词。capture
模式会先提出slug建议，在创建任何内容前需得到用户确认，因为后续任何模式都无法重命名文件夹。这样成本仅在创建时产生一次，无需为罕见的重命名操作开发复杂的机制。路由表的

Idea

列显示当前的人性化名称，可以随时修改。

Artifacts land inside the topic folder

产物存储在主题文件夹内

The artifact root is the topic folder, not the repo root. A skill that documents a path under

docs/

writes it under

topics/<slug>/docs/

instead, keeping its own subpath and filename convention intact.

docs/plans/plan-sso-2026-07-23.md

becomes

topics/<slug>/docs/plans/plan-sso-2026-07-23.md

This is a root swap, so it holds for every skill, including one added after this file was written. The repo root has no

docs/

directory and does not gain one.

Filenames follow

<type>-<slug>-YYYY-MM-DD.md

, with the artifact's creation date at the end. Keep that date stable when the file is edited later.

产物的根目录是主题文件夹，而非仓库根目录。 若某个工具包需要在

docs/

路径下生成文档，则写入

topics/<slug>/docs/

路径下，保留其原有的子路径和文件名约定。例如

docs/plans/plan-sso-2026-07-23.md

会变为

topics/<slug>/docs/plans/plan-sso-2026-07-23.md

。

这是根路径替换，因此适用于所有工具包，包括本文档编写后新增的工具包。仓库根目录没有

docs/

文件名遵循

<type>-<slug>-YYYY-MM-DD.md

格式，末尾为产物的创建日期。后续编辑文件时该日期保持不变。

Saving is a demand, not a default

保存是主动需求，而非默认行为

The discussion is the deliverable. A file is what the user asks for when the discussion earned one. Most sessions explore and stop there, and a repo of entries nobody wanted is worse than a thin one, because a later

status

run reads every row as something the user meant.

So every write runs through one gate:

Compose the write anyway. Draft the
```
NOTES.md
```
entry, the
```
## Open
```
block, and the router row in full.
Print the draft as a code block, under the absolute path it would land at.
Ask save, edit, or drop. Take a no for an answer, and write nothing.

Composing first is what makes the yes cheap. An offer that asks "want me to save this?" with nothing attached gets declined for the wrong reason.

The gate covers every file, the router row included.

INDEX.md

holds a summary and an open question, which are thinking rather than bookkeeping, so the row goes with the entry it describes. A session the user did not save did not touch the idea, so

Last touched

stays where it was.

capture
and
close
are exempt, because in each the ask is the write. "Write this down" and "I'm dropping this" are demands already made, and the file is the whole output of the mode. Turning either into an offer asks the user to confirm the thing they just requested.

The user can say "save that" at any point. Write the entry then, and carry on. Offer a save unprompted only once mid-session, when the discussion settles something that would cost real work to reconstruct.

The cost, stated plainly.

session

opens on a status report, and

status

crowns the coldest idea carrying an open question. Both read

NOTES.md

. Unsaved sessions leave those reads behind what the user actually thinks. The hand-off says so on every run that writes nothing, so a thin log never passes for a quiet month.

讨论本身就是成果。仅当讨论有价值时，用户才会要求保存文件。 大多数会话仅用于探索，结束后无需保存内容。如果仓库中充满了用户不需要的条目，反而比内容少的仓库更糟，因为后续运行

status

模式时会将每一行都视为用户认可的内容。

因此所有写入操作都需遵循以下流程：

先撰写拟写入的内容。 完整起草
```
NOTES.md
```
条目、
```
## Open
```
区块和路由表行。
将草稿作为代码块打印出来，并标注其绝对路径。
询问用户是否保存、编辑或丢弃。 尊重用户的拒绝选择，不写入任何内容。

先撰写内容可以降低用户同意保存的门槛。如果仅询问“是否要保存？”而不展示内容，用户可能会因不确定而拒绝。

该流程适用于所有文件，包括路由表行。

INDEX.md

包含摘要和待解决问题，这些属于思考内容而非记账信息，因此路由表行需与其对应的条目一同处理。若用户拒绝保存会话，则表示该会话未修改创意，因此

Last touched

字段保持不变。

capture
和
close
模式例外，因为用户的请求本身就是写入指令。 “写下来”和“我要放弃这个创意”本身就是明确的需求，文件是这些模式的全部输出。若将其变为询问，相当于让用户确认他们刚刚提出的请求。

用户可以随时说“保存这个”。 此时立即写入条目，然后继续会话。仅当讨论得出了需要大量工作才能重建的结论时，才主动询问是否保存一次。

明确说明成本。

session

模式会从状态汇报开始，

status

模式会优先选择带有待解决问题的最久未处理创意。两者都会读取

NOTES.md

。未保存的会话会导致这些读取内容与用户实际想法不符。因此每次未写入内容的运行都会在交接时说明这一点，确保内容较少的日志不会被误认为是用户近期没有思考。

Mode:

capture

模式：

capture

Write the idea down and stop. It does not discuss, does not research, and offers a session once at most.

记录创意并停止操作。该模式不进行讨论、不开展调研，最多仅主动提出开启一次会话。

1. Match before you create

1. 创建前先匹配

Read

INDEX.md

. Match the ask against every slug, every alias, and every summary. When anything is close, show the candidate row and ask whether this belongs on that idea or starts a new one. Read only the router here, so the guard holds.

Two folders for one idea splits the log, and the guard means a later session opens one of them with nothing signalling the other exists.

读取

INDEX.md

，将用户请求与每个slug、别名和摘要进行匹配。若发现匹配度较高的内容，展示候选行并询问该创意是否属于已有主题，还是需要创建新主题。此处仅读取路由表，以遵守隔离规则。

同一个创意对应两个文件夹会导致日志拆分，而隔离规则意味着后续会话打开其中一个文件夹时，不会有任何提示表明另一个文件夹存在。

2. Confirm the slug, then create

2. 确认slug后再创建

On a new idea, propose a slug and confirm it before writing anything, because it is permanent. Then create

topics/<slug>/

, write

IDEA.md

from the user's own words, and write the first dated

NOTES.md

entry.

When the mode fires from another repo, record that repo in the first entry. Where an idea arrived from is usually part of the idea.

若为新创意，先提出slug建议并在写入任何内容前得到用户确认，因为slug是永久不变的。然后创建

topics/<slug>/

目录，根据用户的描述写入

IDEA.md

，并写入第一条带日期的

NOTES.md

条目。

若该模式从其他仓库触发，需在第一条条目中记录该仓库信息。 创意的来源通常是创意的一部分。

3. Write the router row

3. 写入路由表行

Add the row with two or three aliases the user would plausibly say later, the one-line summary, and the open question when one is obvious. Status is

active

On an append instead of a create, add the dated

NOTES.md

entry, refresh the

## Open

block, and rewrite the router row.

Done when the router row exists and

IDEA.md

states the idea in the user's own words. Then go to Hand off.

添加路由表行，包含两到三个用户后续可能会用到的别名、单行摘要，以及明显的待解决问题（若存在）。状态设置为

active

。

若为追加到已有创意，添加带日期的

NOTES.md

条目，更新

## Open

区块，并重写路由表行。

完成标志：路由表行已存在，且

IDEA.md

用用户自己的语言说明了创意。然后进入交接环节。

Mode:

session

模式：

session

The mode that thinks.

用于深度思考的模式。

1. Route to exactly one idea

1. 解析为唯一的创意

Read

INDEX.md

and resolve one slug. On an unknown slug, run

capture

first, then continue here.

With no idea named, ask. Offer the ideas by last touched, plus "a new idea". Use

AskUserQuestion

when four or fewer candidates fit, and a numbered list otherwise. Never guess the idea, and never fall through to

status

读取

INDEX.md

并解析为唯一的slug。若slug未知，先触发

capture

模式，然后继续本流程。

若未指定创意，询问用户。 按最后修改时间排序展示创意，同时提供“新创意”选项。若候选创意不超过4个，使用

AskUserQuestion

交互；否则使用编号列表展示。绝不猜测创意，也绝不直接触发

status

模式。

2. Read only that folder

2. 仅读取该文件夹

Read

IDEA.md

, then

NOTES.md

, then only the artifacts those two name. Open nothing else.

读取

IDEA.md

，然后读取

NOTES.md

，仅读取这两个文件中提及的产物。不打开任何其他内容。

3. Open with the status report

3. 以状态汇报开启会话

Print the single-idea report from

status

as the first thing the user sees. The session then starts from where the last one stopped rather than from a cold restatement.

首先打印

status

模式中的单个创意汇报内容，让用户了解会话从上次结束的地方继续，而非从头开始。

4. Discuss

4. 讨论

The posture: state the strongest version of the idea, then name what would kill it. Build the case first, because an idea argued down before it is stated properly never gets a fair test. Then say the one condition that would end it.

When the user says they are thinking out loud, build only and skip the stress pass. Record the kill condition as the open question either way, so an expansive night still costs the log nothing.

原则：先阐述创意最有力的版本，再指出可能推翻它的因素。 先构建完整的论证，因为如果创意在被清晰阐述前就被反驳，永远无法得到公平的检验。然后说出可能终结该创意的核心条件。

当用户表示只是在随口思考时，仅构建论证，跳过反驳环节。 无论如何都要将推翻条件记录为待解决问题，这样即使是一次发散的思考也不会给日志带来额外负担。

5. Close the session

5. 结束会话

Compose three writes, then offer them as one save:

The dated
```
NOTES.md
```
entry, three to six lines minimum, naming a decision, a rejection, or an open question. That entry is the spine the next session reads.
A refreshed
```
## Open
```
block for
```
IDEA.md
```
, plus a rewritten head when the idea itself changed.
The router row, including
```
Last touched
```
.

Print all three under their paths and ask save, edit, or drop, as Saving is a demand, not a default sets out. On a yes, write them in the order above. On a no, write nothing, and say so in the hand-off.

A full session record goes to

topics/<slug>/docs/sessions/

only when the user asks for one. Do not offer it.

parked

closed

idea that gets a saved session returns to

active

under a new dated entry.

Done when the user has seen the composed entry and answered. On a save, the entry names a decision, a rejection, or an open question, the

## Open

block matches that entry, and the router row matches both. On a drop, nothing in the folder changed. Then go to Hand off.

撰写三份拟写入的内容，然后作为一个整体询问用户是否保存：

带日期的
```
NOTES.md
```
条目，至少3-6行，记录已做出的决策、已拒绝的选项或待解决的问题。该条目是下一次会话读取的核心内容。
为
```
IDEA.md
```
更新
```
## Open
```
区块，若创意本身发生变化则重写头部内容。
路由表行，包含
```
Last touched
```
字段。

按照保存是主动需求，而非默认行为的流程，打印所有内容及其路径，询问用户是否保存、编辑或丢弃。若用户同意，按上述顺序写入内容；若用户拒绝，则不写入任何内容，并在交接环节说明这一点。

完整的会话记录仅在用户明确要求时才会存入

topics/<slug>/docs/sessions/

。不主动提供该选项。

若已被标记为

parked

或

closed

的创意开启了已保存的会话，则会在新的日期条目下恢复为

active

状态。

完成标志：用户已查看拟写入的内容并给出答复。若保存成功，条目记录了决策、拒绝选项或待解决问题，

## Open

区块与条目匹配，路由表行与两者一致；若丢弃，文件夹内容未发生变化。然后进入交接环节。

Mode:

status

模式：

status

Reports, and writes nothing at all.

仅汇报进展，不写入任何内容。

Cross-idea scope, no idea named

多创意范围，未指定创意

Read

INDEX.md

and list

topics/

. Open no topic folder. Print one table sorted by last touched, grouped by status, with each row's age in days (

untouched 94 days

). Name any folder the router does not list, and say to run

session

on it to register it.

There is no stale marker. A tag most rows would wear inside a year is a verdict on a repo whose whole point is that ideas sit, and the crown below already promotes the cold ones.

Then crown one move:

#	State	Move →
1	an `active` idea carries a recorded open question	`session` on the coldest such idea, naming its age
2	an `active` idea carries no open question	`session` on it, to find one
3	a `building` idea carries an open question	`session` on it
4	every idea is `parked` or `closed` , or none exists	say there is no next move, and offer `capture`

Within rule 1 the crown goes to the coldest idea, not the warmest. Cold plus an open question means the user stopped mid-thought, which is the recoverable case, and it is the row a table sorted by recency buries. Ranking on recency would make the crown restate row one.

No ideas repo, or an empty one? Say so in one line, offer

capture

, and print no empty table.

读取

INDEX.md

并列出

topics/

目录。不打开任何主题文件夹。 打印一个按最后修改时间排序、按状态分组的表格，每行显示创意未被处理的天数（例如“已94天未处理”）。提及所有未在路由表中列出的文件夹，并提示用户运行

session

模式来注册它们。

没有“过期”标记。若在一年内大多数创意都带有该标记，反而违背了创意仓库的初衷——创意本就可以被搁置，而下方的“优先行动”已经会推荐最久未处理的创意。

然后推荐一个优先行动：

#	状态	推荐行动 →
1	`active` 创意带有已记录的待解决问题	对最久未处理的该创意运行 `session` 模式，说明其未处理天数
2	`active` 创意没有待解决问题	对该创意运行 `session` 模式，找出待解决问题
3	`building` 创意带有待解决问题	对该创意运行 `session` 模式
4	所有创意均为 `parked` 或 `closed` ，或无任何创意	说明没有下一步行动，并提供 `capture` 模式选项

在规则1中，优先选择最久未处理的创意，而非最新的。 长时间未处理且带有待解决问题意味着用户中途停止了思考，这是可以恢复的情况，而按最近修改时间排序的表格会将该创意排在后面。若按最近修改时间排序，推荐的行动会与表格第一行重复。

若创意仓库不存在或为空？ 用一句话说明情况，提供

capture

模式选项，不打印空表格。

Single-idea scope, one idea named

单创意范围，指定了一个创意

Read

IDEA.md

, the last two or three

NOTES.md

entries, and a listing of

docs/

without reading the artifacts. Print what the idea is, where it stands, and the open questions. Then crown one move:

#	State	Move →
1	an open question blocks the others	`session` on that question
2	the idea rests on an unresearched external fact	`research`
3	the idea is a business and has no verdict	`validate`
4	the idea is settled enough to shape work	plan it in the project repo
5	nothing is open and no next question exists	`close` , naming which verdict fits

Done when the printed state matches the files read and exactly one move is crowned. Then go to Hand off.

读取

IDEA.md

、最近两到三条

NOTES.md

条目，以及

docs/

目录的列表（不读取产物内容）。打印创意的定义、当前进展和待解决问题。然后推荐一个优先行动：

#	状态	推荐行动 →
1	存在阻碍其他问题的待解决问题	针对该问题运行 `session` 模式
2	创意依赖未调研的外部事实	运行 `research` 模式
3	创意是商业项目且无最终结论	运行 `validate` 模式
4	创意已足够成熟可指导工作	在项目仓库中使用计划工具包（安装后使用 plankit）进行规划
5	无待解决问题且无下一步问题	运行 `close` 模式，说明适用的结论类型

完成标志：打印的状态与读取的文件内容一致，且仅推荐一个行动。然后进入交接环节。

The dispatch contract

分派协议

research

and

validate

both send a question to a sibling skill. Four rules govern every dispatch:

Let the sibling answer inline. researchkit and validatekit both default to answering in the conversation and saving nothing, and that default is ideakit's too. Do not answer their save prompt on the user's behalf.
Suppress the sibling's hand-off and print ideakit's own. The dispatch is a sub-step, and two competing next-step lines help nobody.
Offer the artifact after the answer, never before. Ask once whether to keep it. On a yes, write the file yourself from the sibling's inline answer, at
```
topics/<slug>/docs/…
```
, keeping the sibling's own subpath and filename convention. Re-running the sibling to save would land the file in the working directory, because a sibling skill documents its own root and defers to no host. Asking before the dispatch asks before the user knows whether the answer was worth keeping.
Fold back only what gets saved. On a yes, offer the dated
```
NOTES.md
```
entry naming the question, the answer, and the artifact path, together with the
```
IDEA.md
```
and router updates. On a no, the answer stays in the conversation and the log stays as it was.

The idea's own log holds one authoritative thread of everything the user kept, so a later session reads one file and finds every saved answer.

research

和

validate

模式都会将问题发送给兄弟工具包。四条规则管理所有分派操作：

让兄弟工具包直接在对话中回复。 researchkit 和 validatekit 默认在对话中回复且不保存内容，这也是Ideakit的默认行为。不得代表用户回答它们的保存提示。
屏蔽兄弟工具包的交接信息，仅展示Ideakit的交接信息。 分派是一个子步骤，两条相互竞争的下一步行动说明对用户毫无帮助。
仅在得到答案后询问是否保存产物。 仅询问一次是否留存产物。若用户同意，根据兄弟工具包的对话回复自行写入文件，路径为
```
topics/<slug>/docs/…
```
，保留兄弟工具包的子路径和文件名约定。若重新运行兄弟工具包来保存，文件会被写入工作目录，因为兄弟工具包以自身为根目录，不依赖宿主工具包。在分派前询问保存相当于在用户知道答案是否有价值前就做出请求。
仅整合已保存的内容。 若用户同意保存，提供带日期的
```
NOTES.md
```
条目，记录问题、答案和产物路径，同时更新
```
IDEA.md
```
和路由表；若用户拒绝，答案仅留在对话中，日志保持不变。

创意的专属日志记录了用户留存的所有权威内容，因此后续会话仅需读取一个文件即可找到所有已保存的答案。

Mode:

research

模式：

research

Route to one slug first, then classify the question before acting.

A tool, library, framework, or architecture question goes to a research skill (researchkit when installed), answering inline. Offer to keep it at
```
topics/<slug>/docs/research/
```
afterwards.
A build-or-drop question is not research. Redirect it to
```
validate
```
.
A market, competitor, category, or customer-signal question has no sibling owner, so ideakit runs it directly: who else does this, what the category is called, how incumbents price it, and what users publicly complain about. Give every claim a source and a date. Offer the result at
```
topics/<slug>/docs/research/research-<slug>-YYYY-MM-DD.md
```
.

Without a research skill installed, run the comparison against primary sources directly and say plainly that it is the short version.

Done when the user has seen the answer and answered the save offer. On a yes, the artifact exists, the

NOTES.md

entry names the question and the answer, and

IDEA.md

and the router row match. On a no, the folder is untouched. Then go to Hand off.

先解析为唯一的slug，然后对问题进行分类后再行动。

工具、库、框架或架构相关问题 发送给调研工具包（安装后使用 researchkit），在对话中回复。之后询问是否将结果留存到
```
topics/<slug>/docs/research/
```
。
开发或放弃的决策问题 不属于调研范畴，重定向到
```
validate
```
模式。
市场、竞争对手、品类或客户信号相关问题 没有对应的兄弟工具包，因此由Ideakit直接处理：包括还有谁在做这个、该品类的名称是什么、现有厂商的定价如何、用户公开抱怨的问题是什么。每个结论都需附带来源和日期。 询问是否将结果留存到
```
topics/<slug>/docs/research/research-<slug>-YYYY-MM-DD.md
```
。

若未安装调研工具包，直接通过原始来源进行对比，并明确说明这是简化版本。

完成标志：用户已查看答案并答复保存请求。若保存成功，产物已存在，

NOTES.md

条目记录了问题和答案，

IDEA.md

和路由表行匹配；若拒绝，文件夹内容未发生变化。然后进入交接环节。

Mode:

validate

模式：

validate

Route to one slug, then hand the idea to a validation skill (validatekit when installed), answering inline. Offer to keep the write-up at

topics/<slug>/docs/validation/

afterwards.

Honor the sibling's side-project off-ramp rather than working around it. It will fire often here, because most ideas in a personal ideas repo are not businesses, and an honest "this is a side project, not a company" is a real answer worth offering to write down.

Offer the verdict, the wedge, and the assignment as one

NOTES.md

entry, with the router status change when the verdict moves it.

Without a validation skill installed, run a short forcing-question set and a graded verdict, and say plainly that it is the short version.

Done when the user has seen the verdict and answered the save offer. On a yes, the verdict, the wedge, and the assignment are in

NOTES.md

, and the router status matches the verdict. On a no, the folder is untouched. Then go to Hand off.

解析为唯一的slug，然后将创意交给验证工具包（安装后使用 validatekit），在对话中回复。之后询问是否将验证报告留存到

topics/<slug>/docs/validation/

。

尊重兄弟工具包的副业分流机制，而非绕过它。 这种情况在个人创意仓库中很常见，因为大多数创意并非商业项目，而诚实的结论“这是副业，不是公司项目”是值得记录的答案。

将最终结论、切入点和任务分配作为一个

NOTES.md

条目提供，若结论导致状态变化则更新路由表状态。

若未安装验证工具包，运行简短的强制问题集并给出分级结论，并明确说明这是简化版本。

完成标志：用户已查看结论并答复保存请求。若保存成功，结论、切入点和任务分配已写入

NOTES.md

，路由表状态与结论匹配；若拒绝，文件夹内容未发生变化。然后进入交接环节。

Mode:

close

模式：

close

Route to one slug. Ask which verdict applies:

building

parked

, or

closed

. Require the reason, and refuse to write a verdict without one.

Then write, without a save offer. The verdict and its reason are the demand, and the reason question already gave the user a place to stop.

Write a dated verdict entry into
```
NOTES.md
```
, recording what was decided, what evidence decided it, and what would reopen it.
Rewrite
```
IDEA.md
```
so the verdict sits at the top of its head.
Update the router row.
On
```
building
```
, record the implementation repo in the status cell and in the entry.

A closed idea keeps its folder. This mode never deletes a topic folder, never moves a file out of one, and never migrates anything to another repo. An idea that gets built runs its implementation in a separate repo, and the folder stays open for future thinking about the same subject.

Done when the verdict entry,

IDEA.md

, and the router row agree, and nothing else in the folder changed. Then go to Hand off.

解析为唯一的slug。询问用户适用的结论类型：

building

、

parked

或

closed

。要求用户提供理由，无理由则拒绝写入结论。

然后直接写入内容，无需询问保存。结论及其理由是用户明确的需求，而理由询问环节已让用户完成了思考。

在
```
NOTES.md
```
中写入带日期的结论条目，记录决策内容、决策依据以及重新开启该创意的条件。
重写
```
IDEA.md
```
，将结论放在头部最上方。
更新路由表行。
若为
```
building
```
状态，在状态单元格和条目中记录实现仓库的路径。

已关闭的创意保留其文件夹。 该模式绝不会删除主题文件夹，绝不会将文件移出文件夹，也绝不会将任何内容迁移到其他仓库。若创意进入开发阶段，开发工作在独立的项目仓库中进行，原文件夹仍保留，用于未来对同一主题的思考。

完成标志：结论条目、

IDEA.md

和路由表行内容一致，文件夹中其他内容未发生变化。然后进入交接环节。

Hand off

交接

Write this section in the procedural register: one instruction per sentence, active voice, present tense, no metaphor.

What changed. Name the entry written, the artifact saved, and the status set. Name what did not change too: a save the user declined, a folder you reported and did not open, a dispatch that ran the short version, a verdict you refused to write without a reason.

Say when a run wrote nothing. State it in one line: this session leaves no record in the repo. Do not soften it, and do not imply the discussion was saved. Offer the save once more only if the user asks.

Where it landed. Give the topic folder path. Give the artifact path when a mode wrote one. Give the repo path when this run created the repo.

Next. Crown one move, chosen by state:

The session stopped on an open question → run
```
session
```
again on that question.
The open question needs an external fact → run
```
research
```
.
The idea is a business with no verdict → run
```
validate
```
.
The idea is settled enough to shape work → plan it in the project repo, with a plan skill (plankit when installed).
Nothing is open → run
```
close
```
, and name which verdict fits.
The idea just closed → say there is no next step. Do not invent a follow-up.

Then offer a commit of the ideas repo. Never run it without a yes. Skip the commit offer on a run that wrote nothing.

A
status
run closes differently. Its whole output is a hand-off, and the dashboard already crowns the move. State that nothing changed. Do not print the move twice, and do not offer a commit.

本节采用流程化表述：每句一条指令，主动语态，现在时，无隐喻。

变更内容。 说明已写入的条目、已保存的产物以及已设置的状态。同时说明未变更的内容：用户拒绝的保存请求、已汇报但未打开的文件夹、运行简化版本的分派操作、因无理由而拒绝写入的结论。

说明本次运行是否未写入任何内容。 用一句话明确说明：本次会话未在仓库中留下任何记录。不得含糊其辞，不得暗示讨论内容已被保存。仅当用户询问时才再次提供保存选项。

存储路径。 给出主题文件夹的路径。若模式写入了产物，给出产物的路径。若本次运行创建了仓库，给出仓库的路径。

下一步行动。 根据当前状态推荐一个行动：

会话在待解决问题处结束 → 针对该问题再次运行
```
session
```
模式。
待解决问题需要外部事实 → 运行
```
research
```
模式。
创意是商业项目且无最终结论 → 运行
```
validate
```
模式。
创意已足够成熟可指导工作 → 在项目仓库中使用计划工具包（安装后使用 plankit）进行规划。
无待解决问题 → 运行
```
close
```
模式，说明适用的结论类型。
创意刚被关闭 → 说明没有下一步行动，不得编造后续任务。

然后询问用户是否提交创意仓库的变更。未得到用户同意绝不运行提交操作。若本次运行未写入任何内容，跳过提交询问。

status
模式的交接方式不同。其全部输出就是交接信息，且仪表盘已推荐了行动。说明未发生任何变更。不得重复打印行动，也不得询问提交。

Notes

注意事项

The isolation guard beats every other rule here. Resolve one slug, open one folder.
```
status
```
reports on every idea and opens none of them, which is the guard working rather than an exception to it.
The user decides what gets kept. Compose the write, show it, and wait.
```
capture
```
and
```
close
```
are the two exemptions, and there are no others.
capture
stops. Its job is to lose nothing when an idea arrives at a bad moment. Turning it into a session is how the idea gets dropped instead.
Never rename a slug. Confirm it at creation and leave it alone. The router's
```
Idea
```
column is where a changed name goes.
This repo ships no code. ideakit never writes application code and never opens issues. An idea that becomes real work moves to a project repo and gets issues there.
Never commit the ideas repo on its own.
No writable filesystem (a browser-based agent)? The save offer becomes a print. Say so plainly, print the
```
NOTES.md
```
entry and any artifact as code blocks for the user to save, and give the paths they belong at. Do not report a write that did not happen.
```
status
```
still runs when the filesystem is readable.

隔离规则优先于其他所有规则。 解析为唯一的slug，打开一个文件夹。
```
status
```
模式汇报所有创意但不打开任何文件夹，这是隔离规则的体现而非例外。
用户决定留存内容。 撰写拟写入的内容，展示给用户，等待答复。
```
capture
```
和
```
close
```
模式是仅有的两个例外，无其他例外情况。
capture
模式会停止操作。其职责是在创意产生的不利时刻避免内容丢失。若将其转为会话模式，反而会导致创意被遗忘。
绝不重命名slug。 创建时确认slug，之后不再修改。路由表的
```
Idea
```
列用于显示变更后的名称。
本仓库不包含代码。 Ideakit绝不会写入应用代码，也绝不会创建Issue。若创意转化为实际工作，需迁移到项目仓库并在其中创建Issue。
绝不自动提交创意仓库。
若无可写入的文件系统（如基于浏览器的Agent）？保存请求转为打印操作。明确说明情况，将
```
NOTES.md
```
条目和任何产物作为代码块打印出来供用户自行保存，并给出对应的存储路径。不得汇报未实际发生的写入操作。若文件系统可读，
```
status
```
模式仍可正常运行。

ideakit

Original

Translation

ideakit

Ideakit

Mode selection

模式选择

The ideas repo

创意仓库

The router

路由表

Read one idea folder, never two

仅读取一个创意文件夹，绝不读取两个

The three topic files

三个主题文件

The router is a cache, so repair it

路由表是缓存，因此需要维护

The slug is permanent

Slug 是永久不变的

Artifacts land inside the topic folder

产物存储在主题文件夹内

Saving is a demand, not a default

保存是主动需求，而非默认行为

Mode: capture

模式：capture

1. Match before you create

1. 创建前先匹配

2. Confirm the slug, then create

2. 确认slug后再创建

3. Write the router row

3. 写入路由表行

Mode: session

模式：session

1. Route to exactly one idea

1. 解析为唯一的创意

2. Read only that folder

2. 仅读取该文件夹

3. Open with the status report

3. 以状态汇报开启会话

4. Discuss

4. 讨论

5. Close the session

5. 结束会话

Mode: status

模式：status

Cross-idea scope, no idea named

多创意范围，未指定创意

Single-idea scope, one idea named

单创意范围，指定了一个创意

The dispatch contract

分派协议

Mode: research

模式：research

Mode: validate

模式：validate

Mode: close

模式：close

Hand off

交接

Notes

注意事项

Mode:
`capture`

模式：
`capture`

Mode:
`session`

模式：
`session`

Mode:
`status`

模式：
`status`

Mode:
`research`

模式：
`research`

Mode:
`validate`

模式：
`validate`

Mode:
`close`

模式：
`close`