THREADKEEP / FIELD GUIDE
What to keep when your AI project moves to a new chat
A practical handoff keeps the goal, decisions and next task visible without carrying every message forward.
By Interesting Concepts LLC · Published
Start with the current state
A useful handoff answers three questions: what are we trying to finish, what has actually been completed, and what should happen next? Separate finished work from suggestions that have not been implemented. A confident sentence in a conversation is not evidence that a file was saved or a change was deployed.
For a website project, record the pages that exist, the copy already approved and the next review task. Include the relevant file or source references so the next session can check the current state. Avoid copying a long discussion when a short, checked decision is enough.
Preserve constraints and uncertainty
Write down the things the next session must preserve: approved wording, interfaces, budget constraints or a requirement to review before publishing. Label unresolved questions explicitly. If the previous conversation proposed two approaches, do not let the summary present either as a settled decision.
Review any AI-generated pack against the source conversation and the actual work. Remove passwords, credentials and unrelated private information before sending it to another tool. A context pack is something you maintain, not independent verification of the project.
Give the next session a bounded task
Finish with one concrete next step and a way to recognize completion. “Check the contact form on mobile and report failures” is easier to act on than “finish the website.” Name any approval needed before the next external action.
Try the handoff in a new conversation. If you still need to explain a missing decision, add it to the pack. Threadkeep supports manual editing and export on both plans; Pro is useful when ongoing work needs more saved projects and repeated AI updates.
