Turn Iteration Into a Prompt — the One-Number Opening
A status-report iteration that converged on "lead with the decision-relevant number" becomes a prompt that produces that report every week without the Monday rewrite.
Overview
Recurring deliverables are where iteration pays the highest dividend — and loses the most when it stays in the chat. A leadership report iterated to its converged form (one-number opening, three sections, one page, never "various changes") is a weekly task solved permanently — IF the convergence escapes the conversation. This setup loads that iteration: the generic-opening rejection, the one-number correction, the three-section format, the one-page constraint, and the "this is the final version" declaration, distilled into the prompt the next Monday starts from.
Workflow
-
Converge once
The iteration happens a single time — rejections and corrections doing the design.
-
Distill the convention
Three sections, one page, one-number opening — conventions become prompt rules.
-
Run it weekly
Each Monday starts at the converged format; the iteration never repeats.
Why This Works
- Recurring tasks multiply the value of a single distillation
- Structural conventions translate directly into prompt requirements
- The final-version declaration marks exactly what to bottle
Best for
- Status reports, summaries, recurring documents
- Deliverables with structural conventions
- Anyone re-teaching the same format weekly
Not for
- Designing the report structure from scratch — the Markdown Output Builder owns document structure
- Summarizing the metrics themselves — the Structured Summary Prompt
Use cases
- Weekly reports that converged once and run forever
- Recurring deliverables with hard structural rules
- Killing the every-Monday re-iteration