figure-it-out

没有现成 playbook 就自己设计一份

When the task matches no playbook, design one. The deliverable before any code is the workflow itself: a sequence of phases that scales rigor to the task, runs the scientific method, and leaves a decision trail a human can audit after stepping away.

任务对不上任何 playbook 时，自己设计一份。写任何代码前的交付物就是工作流本身：一系列阶段，严谨度按任务缩放，跑科学方法，留下人走开后还能审计的决策轨迹。

Start

开始

Open a todolist whose first item is to read the Principles section of the poteto-mode skill. Then add the phases below as todos.

打开 todolist，第一项是读 poteto-mode skill 的 Principles 小节。再把下面各阶段加为 todo。

Phase A: Frame

Phase A: 定框

Ground first, then commit. Don’t start the run until you can state:

先摸底，再承诺。能说出以下内容之前，别开始长跑：

• The definition of done as a falsifiable predicate (the prove-it-works principle skill).

• Scope, quantified: rough units and effort, plus the blockers grounding surfaced.

• The rigor level, biased high. One-way doors and high blast radius get more. Reversible low-stakes steps get less. Rigor is gates and artifacts, not “try harder”.

• 可证伪谓词形式的完成定义（prove-it-works principle skill）。

• 量化后的范围：粗略单元与工作量，以及摸底暴露的阻塞。

• 严谨度偏高。单向门、高 blast radius 加码；可逆低风险步骤减码。严谨度是门禁和产物，不是「再努力点」。

Present the framing and tradeoffs before committing to a long run. Reversible work proceeds (the never-block-on-the-human principle skill), but a multi-hour run earns one checkpoint.

承诺长跑前亮出定框和取舍。可逆工作继续推进（never-block-on-the-human），但数小时级长跑值得一个卡点。

Phase B: Design the workflow

Phase B: 设计工作流

Decompose into atomic, independently-landable units. Sequence riskiest-unknown-first. Scaffold and verification come before features (the foundational-thinking principle skill).

拆成原子、可独立落地的单元。最冒险的未知优先排序。脚手架和验证先于功能（foundational-thinking）。

• Build the verification harness before the work, with the baseline captured from the pre-change state, so the check reads as “old value vs new value”.

• For one-way-door design decisions, run the architect skill (it runs arena). Skip it for mechanical work whose shape is already concrete. A second arena over a settled design is over-engineering (the laziness-protocol principle skill).

• Decide what fans out. Parallelize only across seams, and give each worker its own worktree or branch (the separate-before-serializing-shared-state principle skill). Don’t over-fan.

• Write the designed phase list down. That list is what the human reviews.

• 干活前先建 verification harness，并从改前状态抓 baseline，让检查读成「旧值 vs 新值」。

• 单向门设计决策跑 architect（它会跑 arena）。形状已具体的机械活跳过。已定型设计再开第二轮 arena 是过度工程（laziness-protocol）。

• 决定什么扇出。只在接缝处并行，给每个 worker 自己的 worktree 或 branch（separate-before-serializing-shared-state）。别过度扇出。

• 把设计好的阶段列表写下来。人审的就是这份列表。

Then execute the design. Add its steps to the todolist as concrete items, after the Phase C entry and before Phase D. Run each under the Phase C loop discipline, and weave the Phase D log through them, a row as each step lands, rather than saving the whole trail for the end.

然后执行设计。把步骤作为具体项加入 todolist，放在 Phase C 条目之后、Phase D 之前。每步按 Phase C 闭环纪律跑；Phase D 日志穿插写入——一步落地一行，别把整条轨迹留到最后。

Phase C: Run the loop

Phase C: 跑闭环

Each unit is an experiment. State the hypothesis, make the smallest change, measure against the predicate on the real artifact, keep it if it advanced, revert it if it didn’t. Apply the sequence-verifiable-units principle skill, verifying each unit before starting the next instead of batching checks at the end.

每个单元是一次实验。陈述假设，做最小改动，在真实产物上对照谓词测量；推进了就留，没推进就回滚。 按 sequence-verifiable-units：验证完一个再开下一个，别把检查堆到最后。

• Verify by inspecting the artifact, never a self-report. When something passes too easily, suspect the observation method before the system.

• Pair delegated work with a judge and audit the delegates’ artifacts yourself before trusting them. If a worker games the gate, reset and harden the contract. If the gate itself is wrong, fix the gate in its own change rather than routing around it.

• A verdict is VERIFIED, NOT VERIFIED, or INCONCLUSIVE. Inconclusive is not a pass. Don’t hide a negative.

• 靠检查产物验证，绝不靠自报。太容易过关时，先怀疑观察方法，再怀疑系统。

• 委派工作配对 judge，亲自审计委托产物再信任。worker 钻门禁就重置并硬化契约。门禁本身错了，单独改门禁，别绕过去。

• 裁决是 VERIFIED、NOT VERIFIED 或 INCONCLUSIVE。不确定不算过。别藏阴性结果。

Phase D: Keep the audit trail

Phase D: 保留审计轨迹

Log the run via the show-me-your-work skill. figure-it-out’s work is usually ambitious enough to commit the trail so the reviewer can read it in the PR. The trail plus the diff is what lets the human come back and trust the work.

用 show-me-your-work skill 记录这次跑。figure-it-out 的活通常够野心，值得把轨迹 commit 进 PR 给审阅者看。轨迹加 diff，才让人回来后信得过。

Phase E: Verify and hand back

Phase E: 验证并交回

Check the whole against the Phase A predicate on the real product, not just the harness. Encode any recurring correction as a gate, a lint rule, a check, or a script (the encode-lessons-in-structure principle skill).

在真实产品上对照 Phase A 谓词检查整体，不只 harness。把反复出现的纠正编码成门禁、lint、检查或脚本（encode-lessons-in-structure）。

Reply: the playbook you designed, the rigor level and why, the decision-trail path, what’s verified against the predicate, and what’s still open.

回复： 你设计的 playbook、严谨度及理由、决策轨迹路径、相对谓词已验证什么、还有什么 open。