Turn a Chat Into a Prompt — Start at the Result
The result you finally liked lives inside the chat. Distill the iterations into one prompt: corrections become requirements, the accepted version becomes the quality bar.
Overview
Every iterated conversation ends with a buried asset: the combination of corrections that finally worked. Re-running the chat to get it back wastes the iterations; remembering them by hand drops the one that mattered. The reusable prompt package extracts the asset — the "too generic" rejection becomes an avoid-rule, the "open with a concrete failure moment" correction becomes a requirement, the under-120-words constraint travels, and the "perfect, that works" moment becomes the quality bar. This setup loads a blog-intro iteration distilled into exactly that prompt.
Workflow
-
Paste the iteration
The corrections, rejections, and "keep this" moments are the raw material — the detector finds them.
-
Read the AVOID list
Rejected directions travel explicitly — the model cannot rediscover the paths you walked back.
-
Start at the result
Next time, the first output meets the standard the conversation took nine turns to reach.
Why This Works
- Corrections-as-requirements start the model where feedback ended
- The verbatim quality-bar quote anchors "good" to your actual reaction
- Last-decision-wins resolves the contradictions every iteration contains
Best for
- Anyone who iterates to good results and loses them
- Recurring tasks first solved conversationally
- Content work with hard-won tone decisions
Not for
- Continuing the same piece of work in a new chat — that's the Context Handoff Builder
- Polishing a prompt you already have — that's the Prompt Formatter
Use cases
- Bottling a converged writing session
- Reusing the result without re-running the chat
- Turning scattered corrections into one instruction set