社区实战：先写 Runbook，再用高质量模型做二次校验
解决复杂任务中“中途跑偏、返工烧 token”的问题。前置：任务超过 2-3 步且可定义完成标准。步骤：先产出 runbook（目标/边界/回滚/验收）→再用高质量模型审校→按清单执行。关键点：每一步都保留日志与检查点。验证：任务中断后可按 runbook 从断点恢复。风险：若 runbook 不维护版本，后续会与实际环境脱节。
REDDITDiscovered 2026-02-14Author u/pjburnhill
Prerequisites
- Task scope is clear enough to define success metrics and failure boundaries.
- At least one high-quality review model/session is available for second-pass checks.
Steps
- Draft runbook with objective, step order, rollback path, smoke tests, and logging plan.
- Send runbook to a stronger reviewer model and capture corrections.
- Apply corrections and freeze an execution checklist version.
- Execute strictly by checklist and record checkpoint state after each major step.
Commands
git statusgit log --oneline -n 5openclaw statusVerify
When interrupted mid-run, another session can resume from documented checkpoint without re-planning from scratch.
Caveats
- Runbooks add upfront cost; reserve this pattern for medium/high-complexity tasks.
- Community post is anecdotal; quantify token savings in your own environment（需验证）.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗