Extract a Reusable Prompt — From Thread to Standing Asset
A converged email thread becomes a standing asset: the usage-anchored subject pattern, the value-before-discount rule, the five-sentence cap — extracted, not retyped.
Overview
Extraction is the difference between solving a task once and owning the solution. A renewal-email thread that converged on a usage-anchored subject line, a value-recap-first rule, and a five-sentence cap contains a reusable asset — but only if it leaves the thread. The package extracts it: the salesy rejection travels as AVOID, the "use this style for all the renewal emails" declaration becomes a standing rule, and the result is a prompt the whole recurring task runs on. This setup loads exactly that thread.
Workflow
-
Find the declaration
"Use this style for all the renewal emails" — the conversation itself declares the asset.
-
Extract, don't retype
The rules travel verbatim from the thread; memory adds nothing and loses plenty.
-
Run the task on it
The recurring task now starts from the extracted prompt — iteration paid once.
Why This Works
- Declared standing rules are the strongest reuse signal a chat produces
- Extraction preserves the exact wording compliance depends on
- One-time iteration cost amortizes across every future run
Best for
- Recurring communication tasks
- Teams standardizing converged styles
- Threads ending with use-this-going-forward moments
Not for
- Carrying the thread's remaining TODO list forward — that's the Context Handoff Builder
- Cleaning redundancy from the extracted prompt — that's the Prompt Cleaner, afterwards
Use cases
- Owning recurring email and outreach tasks
- Converting a one-time convergence into a standing asset
- Capturing "use this style from now on" declarations