Keep the reasoning behind a project alive across months, so the agent can spot when a new plan repeats a rejected idea or ignores a settled constraint.
You get: A dated decision map with rationales, changed assumptions, open loops and a next-step briefOriginal prompt · Not run-tested
Replace the [brackets] with your details, then paste this into your assistant.
Become the continuity partner for [project]. Read only [approved notes, files and threads]. Save the project record in [editable location]. My current aim is [aim], and the next decision is [decision].
Create a dated decision map: what we chose, why we chose it, what we rejected, the evidence and constraints at the time, and what would reopen the question. Separate my stated preference from your inference. Mark uncertain memories and links that no longer open. Keep a short list of unresolved decisions and the one next action each needs. Do not silently replace old reasoning with a new conclusion.
When I propose a new direction, compare it with the map. Tell me if it conflicts with a settled constraint or revives a rejected option, and ask whether the underlying facts changed. Update the record only from new evidence or my correction. Give me a concise brief I can understand after weeks away, with links back to the original decisions. If you cannot retain context or save the note, return a portable document I can bring back. Do not schedule check-ins unless I request a cadence and you verify the saved task.
Automatic copying is unavailable. Select the prompt text above and copy it.
What the result could look like
Illustrative: why the community site stayed small
Months later, a new feature proposal triggers a note: the earlier version was rejected because it needed manual moderation. The agent asks whether that constraint has changed. This is illustrative, not a recorded run.
Illustrative example. This is not an observed result or a verified recommendation.
The real-world spark
Inspired by a reported use
Wang describes active memory across longer periods; Ben Parr reports needing to repeat workflow context less often.
Memory quality and this decision-map workflow were not independently tested. The proposed durable rationale record is an original extension. The prompt above is our original extension, not the author's exact prompt or a tested result.
Make it more you
Use a separate record for a home renovation, writing project or career move; keep sensitive third-party details out unless necessary and authorized.
A few relevant discoveries, properly sourced, in one email. Set your interests or career-upgrade criteria and get new research or job opportunities worth your attention.
You get: A concise sourced email with only new matchesGet the promptCommunity-inspired idea