Save the method, not just the result

说明与用途

开发者保存方法而非仅结果，以便重用验证过的流程并降低对昂贵模型的依赖。

问题

Agents often lose the reasoning process after a successful run, retaining only the final result, which limits reuse and model efficiency.

结果

Agents that retain written methods can reuse proven workflows, reduce reliance on expensive models, and build a historical record of what works, improving efficiency and reliability over time.

工作流

• 1. Run the best available model on a task to produce a successful outcome.
• 2. Extract and document the step‑by‑step method that led to the result.
• 3. Store the method as text in a library (Playbook).
• 4. For subsequent batches, load the method and run a cheaper model to follow the procedure.
• 5. Record each run’s model, pass/fail status, and any human confirmation as evidence.
• 6. Track version changes to the method and correlate with run outcomes.
• 7. Use the accumulated evidence to select the cheapest model that still passes on your examples.

证据

The next time the task shows up, you rerun the expensive model and hope it reasons the same way twice.

来源

Once the procedure exists as text, you no longer need the strongest model for every repeat.

来源

This is the idea behind Playbooks, which I added to Sirro last week.

来源