re0-plan

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Open

.re0/iteration/<version>-<workname>/

and write into it in the same motion, before a single line of

re0-loop

's cycle runs.

打开

.re0/iteration/<version>-<workname>/

并在同一操作中写入内容，在

re0-loop

的循环执行任何代码之前完成。

Goal

目标

A cycle without a written thesis, gate list, and step plan drifts to whatever framing comes first — and a folder opened with nothing in it tells a resumed session nothing at all.

re0-plan

closes both gaps at once: the folder is never empty from the moment it's created, regardless of which weight the cycle turns out to be. It assumes the full paperthin package installed and names its sibling skills directly. It pairs with

re0-release

, which retires the folder, and

re0-memo

, which extends whatever this skill seeded instead of restarting fresh. It is not a portable planning method — the shape it writes is this repo's own convention.

没有书面主旨、检查清单和步骤计划的周期会随最先出现的框架而偏离方向——而打开一个空文件夹对恢复的会话毫无意义。

re0-plan

可同时解决这两个问题：无论最终周期的量级如何，文件夹从创建那一刻起就绝不会是空的。它假设已安装完整的paperthin包，并直接引用其兄弟skill。它与

re0-release

（用于归档文件夹）和

re0-memo

（用于扩展本skill初始化的内容而非重新创建）配合使用。这不是一种可移植的规划方法——它写入的结构是本仓库特有的约定。

Workflow

工作流程

Classify the cycle's weight: a fix or hardening pass with no real design surface is lightweight; a cycle with a direction genuinely worth arguing through is full.
Create
```
.re0/iteration/<version>-<workname>/
```
and, in the same step, write its first file — the weight decides which:
- lightweight →
```
RETRO.local.md
```
  : one paragraph naming the task and why it's lightweight.
```
re0-memo
```
  extends this same file at the end; it never starts a fresh one. Stop here.
- full →
```
DESIGN.local.md
```
  : thesis, scope, and quality gates — the same content
```
re0-loop
```
  's FRAME turn expects, and enough on its own to survive a session break. When the change touches shippable surface, those gates always include a CLAUDE.md/README reflection gate (see Rules). Confirm the read with
```
readchk
```
  , size the tier with
```
modelchk
```
  ; reach for
```
macrothink
```
  or another judgment skill only when the direction is genuinely contestable.
(full only) Write
```
WORKFLOW.local.md
```
: the numbered steps this specific cycle runs through
```
re0-loop
```
's turn order — specific to this build, not a restatement of
```
re0-loop
```
's generic stages.
(full only) Write
```
EVIDENCE.local.md
```
: the gates from
```
DESIGN.local.md
```
, listed as proof surface still to fill — the bar, not results.
Keep reference material flat as
```
REF-<topic>.local.md
```
; promote to a
```
refs/
```
subfolder only once it multiplies past a couple of files.
Hand off to
```
re0-loop
```
. Do not invoke
```
re0-work
```
here — a from-scratch restart is
```
re0-loop
```
's own mid-cycle call, surfaced by
```
nba
```
when warranted, never a setup step.

分类周期量级：没有实际设计层面的修复或强化迭代为轻量级；有值得深入探讨方向的周期为全量。
创建
```
.re0/iteration/<version>-<workname>/
```
，并在同一步骤中写入第一个文件——量级决定文件类型：
- 轻量级 →
```
RETRO.local.md
```
  ：一段文字说明任务内容及其为轻量级的原因。
```
re0-memo
```
  会在末尾扩展该文件，绝不会新建文件。到此为止。
- 全量 →
```
DESIGN.local.md
```
  ：主旨、范围和质量检查标准——与
```
re0-loop
```
  的FRAME阶段预期内容一致，仅凭这些内容即可在会话中断后继续工作。当变更涉及可交付内容时，这些检查标准必须包含CLAUDE.md/README反思检查项（参见规则）。用
```
readchk
```
  确认可读性，用
```
modelchk
```
  确定层级；仅当方向存在真正争议时，才使用
```
macrothink
```
  或其他判断类skill。
（仅全量）写入
```
WORKFLOW.local.md
```
：本周期通过
```
re0-loop
```
阶段顺序执行的具体编号步骤——针对本次构建，而非
```
re0-loop
```
通用阶段的重述。
（仅全量）写入
```
EVIDENCE.local.md
```
：列出
```
DESIGN.local.md
```
中的检查标准，作为仍需填充的验证依据——仅列要求，不列结果。
参考资料以
```
REF-<topic>.local.md
```
的形式平铺存储；仅当文件数量超过几个时，才将其移至
```
refs/
```
子文件夹。
移交至
```
re0-loop
```
。请勿在此调用
```
re0-work
```
——从零重启是
```
re0-loop
```
的周期中调用操作，仅在必要时由
```
nba
```
触发，绝非初始化步骤。

Rules

规则

The folder is never empty at creation. Every path, lightweight or full, writes real content in the same motion the folder is made, so a session break at any point still leaves something to resume from.
Not portable, by design. Names other paperthin skills directly and assumes the full package installed — the opposite of the self-contained default every other skill here follows. It exists only to pair with
```
re0-release
```
and
```
re0-memo
```
, not to travel alone.
No padding. Lightweight gets no
```
DESIGN
```
/
```
WORKFLOW
```
/
```
EVIDENCE
```
, and its
```
RETRO.local.md
```
seed stays one paragraph — a task note, not a
```
WORKFLOW.local.md
```
in disguise. A judgment skill or
```
re0-work
```
never gets forced in "just in case."
The folder's
<version>
is provisional. Apply the same minor/patch discriminator
```
re0-release
```
uses — kind not size: is the change, against the artifact's own prior spec, a fix (patch) or a new capability a user newly reaches for (minor)? — and keep it contingent on any unresolved fork the cycle opens. Never pre-commit a firm bump the cycle hasn't earned; a fork that could add a skill leaves the bump undecided until it resolves.
Docs stay aligned, like
re0-release
at ship time. When the cycle's change touches shippable surface, its quality gates always include a CLAUDE.md/README reflection gate, assigning each reflection to its register per CLAUDE.md's docs-role split: internal mechanism/rules/anatomy → CLAUDE.md (LLM + human, injected as instructions), user-facing catalog/experience → README (human-only, never injected). Never dump agent-instruction mechanism into README, and never skip README for a user-facing change. This is the plan-time complement to
```
re0-release
```
's ship-time README step.
negatives-as-corpus — nothing this skill or the cycle it opens produces gets deleted; a cycle that goes wrong is retired by
```
re0-release
```
, not discarded.
Every
```
EVIDENCE.local.md
```
gate traces back to a line in
```
DESIGN.local.md
```
; don't invent proof surface
```
DESIGN
```
never asked for.

文件夹创建时绝不留空。无论走轻量级还是全量路径，文件夹创建的同时都会写入真实内容，因此无论何时会话中断，都有内容可恢复。
设计上不可移植。直接引用其他paperthin skill，并假设已安装完整包——与本仓库中其他skill遵循的独立默认设计相反。它仅用于与
```
re0-release
```
和
```
re0-memo
```
配合，不可单独使用。
无冗余内容。轻量级路径不包含
```
DESIGN
```
/
```
WORKFLOW
```
/
```
EVIDENCE
```
文件，其
```
RETRO.local.md
```
初始内容仅为一段文字——任务说明，而非伪装成
```
WORKFLOW.local.md
```
的内容。绝不因“以防万一”而强制引入判断类skill或
```
re0-work
```
。
文件夹的
<version>
为临时版本。采用与
```
re0-release
```
相同的次要版本/补丁版本区分规则：依据变更类型而非规模，即相对于制品之前的规格，变更是修复（补丁版本）还是用户可使用的新功能（次要版本）——且需保留周期中未解决分支的变更可能性。绝不要预先确定尚未达成的版本升级；若分支可能新增skill，则需待分支确定后再决定版本升级。
文档保持一致，如同
re0-release
在发布时的操作。当周期变更涉及可交付内容时，其质量检查标准必须包含CLAUDE.md/README反思检查项，根据CLAUDE.md的文档角色划分将每个反思内容分配至对应文档：内部机制/规则/结构 → CLAUDE.md（LLM + 人工，作为指令注入），面向用户的目录/体验 → README（仅人工编写，绝不注入）。绝不要将agent指令机制写入README，也绝不要在涉及用户体验的变更中跳过README。这是
```
re0-release
```
发布时README步骤在规划阶段的对应操作。
negatives-as-corpus — 本skill或其开启的周期所产生的任何内容都不会被删除；失败的周期由
```
re0-release
```
归档，而非丢弃。
每个
```
EVIDENCE.local.md
```
中的检查标准都可追溯至
```
DESIGN.local.md
```
中的内容；不要创建
```
DESIGN
```
未要求的验证依据。

Verification

验证

Before finishing:

The folder has real content from the moment it exists — no empty directory, on either path.
Full path:
```
DESIGN.local.md
```
states a thesis, scope, and gates;
```
WORKFLOW.local.md
```
's steps are specific to this cycle; every
```
EVIDENCE.local.md
```
gate traces to
```
DESIGN.local.md
```
.
Lightweight path:
```
RETRO.local.md
```
is seeded with the task and reason, one paragraph.
Reference material stayed flat unless it earned a
```
refs/
```
subfolder.
Report which path was taken and why.

完成前需确认：

文件夹从创建那一刻起就有真实内容——无论走哪条路径，都不会是空目录。
全量路径：
```
DESIGN.local.md
```
明确了主旨、范围和检查标准；
```
WORKFLOW.local.md
```
的步骤针对本周期；每个
```
EVIDENCE.local.md
```
中的检查标准都可追溯至
```
DESIGN.local.md
```
。
轻量级路径：
```
RETRO.local.md
```
已初始化任务内容及原因，仅一段文字。
参考资料保持平铺存储，除非数量足够多需使用
```
refs/
```
子文件夹。
报告所选择的路径及原因。