Back to Details

figure-it-out

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Figure it out

Figure it out

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.
当任务不匹配任何现有执行手册时，就设计一个。在编写任何代码前，交付物是工作流本身：一系列阶段，其严谨度应与任务规模相称，采用科学方法，并留下可供人类在离开后回来审计的决策轨迹。

Start

开始

Open a todolist whose first item is to read the Principles section of the boring-mode skill. Then add the phases below as todos.
打开一个 todolist，第一项应是阅读 boring-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".
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.
先基于事实澄清，再作出决定。在能够明确以下事项前，不要开始执行：
  • 以可证伪的判定谓词（predicate）表示完成定义（prove-it-works principle skill）。
  • 量化范围：大致的工作单元和所需投入，以及事实梳理所暴露的阻塞项。
  • 严谨度等级，并倾向于设得较高。单向门决策和影响范围较大的事项应获得更高严谨度；可逆且低风险的步骤则应降低严谨度。严谨度体现为门禁和产物，而不是“更用力尝试”。
在决定启动长时间执行前，展示框架及其权衡。可逆工作应继续推进（never-block-on-the-human principle skill），但持续数小时的执行应设置一个检查点。

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).
  • 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.
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.
将任务拆分为原子化、可独立落地的单元。按“风险最高且未知最多”的顺序排列。脚手架和验证应先于功能开发（foundational-thinking principle skill）。
  • 在开展工作前构建验证框架（harness），并从变更前状态捕获基线，使检查结果呈现为“旧值 vs 新值”。
  • 对于单向门设计决策，运行 architect skill（它会运行 arena）。如果只是结构已经明确的机械性工作，则可跳过。对已经确定的设计再运行一次 arena 属于过度设计（laziness-protocol principle skill）。
  • 确定哪些工作可以向外分派。只在边界清晰的接缝处并行化，并为每个 worker 分配独立的 worktree 或 branch（separate-before-serializing-shared-state principle skill）。不要过度并行化。
  • 将设计好的阶段列表写下来。这份列表就是供人类审查的内容。
随后执行该设计。将其中的步骤作为具体条目添加到 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.
  • 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. 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.
每个单元都是一次实验。提出假设，进行最小改动，在真实产物上依据谓词进行测量；如果改动带来进展，则予以保留，否则予以回退。应用 sequence-verifiable-units principle skill，在开始下一个单元前验证当前单元，而不是把检查批量留到最后。
  • 必须通过检查产物来验证，绝不能依赖自我报告。当某项验证过于轻易通过时，应先怀疑观察方法，再怀疑系统。
  • 为每项委派工作搭配一个 judge。如果 worker 钻门禁的空子，应重置任务并强化 contract。如果门禁本身有问题，应通过独立变更修复门禁，而不是绕过门禁。
  • 结论只能是 VERIFIED、NOT VERIFIED 或 INCONCLUSIVE。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 处理的工作通常足够复杂，因此应将审计轨迹提交到版本控制中，让审查者能够在 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).
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.
使用 Phase A 的谓词检查整体结果；检查对象必须是真实产品，而不只是 harness。将任何反复出现且需要纠正的问题编码为门禁、lint 规则、检查或脚本（encode-lessons-in-structure principle skill）。
**回复：**你设计出的执行手册、严谨度等级及其理由、决策轨迹路径、已依据谓词验证的内容，以及仍未解决的问题。