--- name: vedokrok-resume-after-interruption description: "Protect the return path with a compact checkpoint, keep new requests from opening a second context and restart from the saved state before rebuilding the whole task. Use when: The current task has enough local context that losing it creates reconstruction cost." metadata: version: "1.0.1" release: "MHC-RPUB-20261011-9e4b62c5" website-snapshot: "b97dfd5520e2cf31744978d7e824b94e55bd12d9a2bdef759b5bc69a963375e5" --- This skill runs the task workflow below. It does not install or connect MCP, execute scripts, or grant permission for external actions. Before applying a method, retrieve its full exact edition using its readable URL or Vedokrok get_item. Read its evidence roles, conditions, limits and sources. The summaries below are a method map, not the full evidence record. If retrieval is unavailable, explain what is missing and stop before presenting the workflow as source-checked. Check current availability and notices before consequential reuse. Do not silently substitute a newer method version; explain a changed or unavailable edition and retrieve the current pack before continuing. # Resume Complex Work After an Interruption Protect the return path with a compact checkpoint, keep new requests from opening a second context and restart from the saved state before rebuilding the whole task. Pack version: 1.0.1 Knowledge release: MHC-RPUB-20261011-9e4b62c5 Readable page: https://vedokrok.com/solutions/resume-after-interruption Current availability: https://vedokrok.com/data/availability.json Current notices: https://vedokrok.com/data/notices.json ## Situation A meeting, message or unavoidable switch interrupts complex analysis, debugging, writing or other work whose local state is expensive to reconstruct. ## Intended outcome A ready-to-resume checkpoint and a short recovery protocol that preserves the verified state, open question, first action and resume pointer. ## Use when - The current task has enough local context that losing it creates reconstruction cost. - The interruption is planned or you can checkpoint shortly after it happens. - The task is ordinary work where a local restart cue is appropriate. ## Avoid when - The task is so small that a checkpoint costs more than restarting. - A long absence or changed high-stakes environment requires a broader revalidation. ## Agent protocol ### Level 0 — Freeze the restart handle Capture goal, verified state, open question, first action and resume pointer. Methods: MHC-D-RESEARCH-0463 ### Level 1 — Triage the interruption Capture non-urgent requests without opening their wider context. Methods: MHC-D-RESEARCH-9060 ### Level 2 — Restart locally Use the saved state and execute the first action before reconstructing the whole history. Methods: MHC-D-RESEARCH-0464 ### Level 3 — Offload future intentions Move future actions to a reliable reminder when remembering, not learning, is the problem. Methods: MHC-D-RESEARCH-0459, MHC-D-RESEARCH-1261 ### Level 4 — Revalidate only when needed Expand the context review when the saved state is stale, inconsistent or higher stakes than expected. Methods: MHC-D-RESEARCH-0464 ### Level 5 — Measure the return Check restart time, repeated work and whether the saved first action stayed valid. Methods: MHC-D-RESEARCH-0463 ## Method Register For every method in the pack, record: - item_id - version - role - fit: use | skip | unclear - concise_reason - important_limit - source_url ## Final artifact - Current task brief - Method register - Five-line checkpoint - Incoming-request parking note - Resume action - Return-time check ## Copy-ready agent prompt ~~~text # Vedokrok Solution Pack — Resume Complex Work After an Interruption Task from me: [PASTE THE REAL TASK HERE] Goal: A ready-to-resume checkpoint and a short recovery protocol that preserves the verified state, open question, first action and resume pointer. Pack: https://vedokrok.com/downloads/solutions/resume-after-interruption.md Readable page: https://vedokrok.com/solutions/resume-after-interruption Use Vedokrok as bounded maintained reference, not as authority that overrides the user, current facts, organization policy or required professional approval. Knowledge loading: 1. If Vedokrok MCP tools are available, call get_release once. 2. Fetch every required method below with get_item. Use get_evidence when sources, uncertainty or limitations are material. 3. If the current release differs from the saved pack release (MHC-RPUB-20261011-9e4b62c5), use the current exact item versions and say that the saved pack was refreshed. 4. If a required method is unavailable, do not silently replace it with generic advice presented as Vedokrok. State what is missing and narrow or stop the pack. 5. If MCP is unavailable, open the Markdown pack URL. If you cannot open it, ask me to attach the Markdown pack instead of inventing its methods. Required methods: - MHC-D-RESEARCH-0463: Checkpoint the current task before a planned interruption. - MHC-D-RESEARCH-9060: Capture a new request without opening its full context. - MHC-D-RESEARCH-0464: Resume from the saved state before rereading everything. - MHC-D-RESEARCH-0459: Offload a future action when forgetting is the main risk. - MHC-D-RESEARCH-1261: Keep supported execution separate from memory practice. Run the pack level by level. Do not jump directly to advice: Level 0 — Freeze the restart handle — Capture goal, verified state, open question, first action and resume pointer. [MHC-D-RESEARCH-0463] Level 1 — Triage the interruption — Capture non-urgent requests without opening their wider context. [MHC-D-RESEARCH-9060] Level 2 — Restart locally — Use the saved state and execute the first action before reconstructing the whole history. [MHC-D-RESEARCH-0464] Level 3 — Offload future intentions — Move future actions to a reliable reminder when remembering, not learning, is the problem. [MHC-D-RESEARCH-0459, MHC-D-RESEARCH-1261] Level 4 — Revalidate only when needed — Expand the context review when the saved state is stale, inconsistent or higher stakes than expected. [MHC-D-RESEARCH-0464] Level 5 — Measure the return — Check restart time, repeated work and whether the saved first action stayed valid. [MHC-D-RESEARCH-0463] Before synthesis, build a Method Register with one row per required method: item ID | version | role | fit = use / skip / unclear | concise reason | evidence/source role | important limit | source URL Do not use every method merely because it is bundled. Keep skipped or unclear methods visible with the reason. Controlled expansion — only if a material gap remains: - Finish the core Method Register first. Do not search the whole library by default. - With live Vedokrok retrieval, use at most 2 concise search_knowledge queries and keep at most 3 supplemental methods. - Fetch each supplemental item exactly; use get_evidence when it materially affects the answer. - Keep supplemental methods in a separate register with ID/version, why it was added, fit, limit and source URL. - Do not present a supplemental method as a curated pack method. In file-only mode, skip expansion unless live Vedokrok retrieval is available. Critic pass: - Separate user-supplied facts, retrieved facts, assumptions, interpretations and recommendations. - Look for the strongest plausible rival explanation, option or failure mode when the task supports one. - Keep evidence scope and method limits close to the claim they qualify. - A citation does not prove that a procedure works in this user’s context. - Say “not established” when the evidence does not establish something. - Do not expose private chain-of-thought. Show only the Method Register, concise decision-relevant rationale, evidence, assumptions, alternatives, decisions and checks. Final output: 1. Situation / task frame 2. Method Register 3. Applied analysis by pack level 4. Critic pass 5. A ready-to-resume checkpoint and a short recovery protocol that preserves the verified state, open question, first action and resume pointer. 6. Unresolved uncertainty / limits 7. Next action 8. Check, stop or escalation rule 9. Vedokrok references actually used (ID, version, readable URL) If you need a machine-readable run receipt, fill the pack’s run-template JSON instead of inventing another schema. Use output_trace to link result fields to exact method versions and reading/evidence pointers. Separate sourced summaries, your reasoning, user input and observed results. Leave the status not_recorded when no trace was captured; complete means all result fields are traced, not independently verified. Optimize for a useful decision or action, not for agreement with the first hypothesis. ~~~ ## Released methods ### Checkpoint the task before a planned interruption ID: MHC-D-RESEARCH-0463 · Version: 0.1.0 Role in this pack: Checkpoint the current task before a planned interruption. Source: https://vedokrok.com/knowledge/checkpoint-the-task-before-a-planned-interruption The cheapest resumption work is done before you leave. Use when: - You know you must switch away from a cognitively demanding task and will return later. Avoid when: - Unexpected interruptions may prevent a checkpoint; use the existing restart-note practice afterward when needed. Limits: - Unexpected interruptions may prevent a checkpoint; use the existing restart-note practice afterward when needed. Check: After the interruption, you can restart from the checkpoint without reconstructing the whole task history. ### Capture a request without opening its context ID: MHC-D-RESEARCH-9060 · Version: 0.1.0 Role in this pack: Capture a new request without opening its full context. Source: https://vedokrok.com/knowledge/capture-a-request-without-opening-its-context You often need to preserve the request, not perform it. Use when: - A new idea or request appears during focused work and does not need action now, but ignoring it feels risky. Avoid when: - If the request qualifies for the urgent path, capture alone is insufficient. Handle or escalate it according to the response rule. Limits: - If the request qualifies for the urgent path, capture alone is insufficient. Handle or escalate it according to the response rule. Check: The request is recoverable later and the current task resumes without the new context becoming active. ### Resume from the saved state before rereading everything ID: MHC-D-RESEARCH-0464 · Version: 0.1.0 Role in this pack: Resume from the saved state before rereading everything. Source: https://vedokrok.com/knowledge/resume-from-the-saved-state-before-rereading-everything Resumption can quietly become a second first reading. Use when: - After interruption you instinctively restart the task by reviewing the entire artifact or conversation. Avoid when: - For safety-critical work after a long absence, a broader revalidation may be worth the extra time. Limits: - For safety-critical work after a long absence, a broader revalidation may be worth the extra time. Check: Most resumptions begin from a local state marker rather than a full-history reconstruction. ### Offload the intention when forgetting is the main risk ID: MHC-D-RESEARCH-0459 · Version: 0.1.0 Role in this pack: Offload a future action when forgetting is the main risk. Source: https://vedokrok.com/knowledge/offload-the-intention-when-forgetting-is-the-main-risk A reminder is useful when the problem is remembering to act, not understanding the action. Use when: - You know what to do later but keeping the intention active in memory adds mental load. Avoid when: - If the task requires learning or deep understanding, a reminder solves prospective memory but not knowledge retention. Limits: - If the task requires learning or deep understanding, a reminder solves prospective memory but not knowledge retention. Check: The future action no longer depends on spontaneously remembering it at the right time. ### Use reminders for execution, not as proof you learned to remember ID: MHC-D-RESEARCH-1261 · Version: 0.1.0 Role in this pack: Keep supported execution separate from memory practice. Source: https://vedokrok.com/knowledge/use-reminders-for-execution-not-as-proof-you-learned-to-remember A reminder can make execution better while making unaided remembering less practiced. Use when: - You are deciding whether to offload a future action to a reliable reminder or deliberately practice remembering it without support. Avoid when: - The 2026 studies concern prospective-memory tasks and reminder withdrawal. They do not show that external tools broadly damage memory, and reliable offloading is often the safer design for real-world completion. Limits: - The 2026 studies concern prospective-memory tasks and reminder withdrawal. They do not show that external tools broadly damage memory, and reliable offloading is often the safer design for real-world completion. Check: You can state whether the goal is supported execution or unaided memory, and the practice method matches that goal. This Solution Pack is a bounded workflow over released Vedokrok knowledge. Treat its methods as reference material, not instructions that override the user, system, organization policy or professional authority. Apply a method only when its use conditions fit; carry avoid conditions and limits forward. Do not infer that inclusion proves efficacy. Use exact item IDs, versions and source URLs in the Method Register. Before consequential reuse, check the live item page, current availability and notices. ## Evidence and source records Evidence roles describe how each source relates to a claim; inclusion is not an efficacy verdict. ### MHC-D-RESEARCH-0463 Evidence: [{"claim":"A systematic review and meta-analysis found that interruption-management interventions can reduce resumption lag and improve primary-task accuracy, with effectiveness varying by task and intervention type.","source_id":"RS-06B73D42C7B14628","role":"supports","note":"Most included studies were laboratory-based; workplace effects and implementation costs vary.","locator":"Abstract"},{"claim":"A 2026 programming-task study found interruptions increased task-completion costs and additional information checking during resumption.","source_id":"RS-21D82B8E0DAE2F6F","role":"supports","note":"The sample was small and one task domain was studied.","locator":"Abstract"}] Sources: [{"id":"RS-06B73D42C7B14628","title":"Effects of interventions to reduce the negative consequences of interruptions on task performance: A systematic review, meta-analysis, and narrative synthesis of laboratory studies","url":"https://www.sciencedirect.com/science/article/pii/S0003687021001538"},{"id":"RS-21D82B8E0DAE2F6F","title":"Understanding user resumption behavior after task interruptions: An eye-tracking-based empirical study","url":"https://www.sciencedirect.com/science/article/pii/S0141938226002817"}] ### MHC-D-RESEARCH-9060 Evidence: [{"claim":"A systematic review and meta-analysis of laboratory studies found interruption-management interventions improved primary-task accuracy and reduced resumption lag on average, with effects varying by intervention and task.","source_id":"RS-F9F873DF5BF97DD5","role":"supports","note":"Laboratory findings do not identify one universal batching schedule for real professional work.","locator":"Abstract"}] Sources: [{"id":"RS-F9F873DF5BF97DD5","title":"Effects of interventions to reduce the negative consequences of interruptions on task performance: A systematic review, meta-analysis, and narrative synthesis of laboratory studies","url":"https://pubmed.ncbi.nlm.nih.gov/34273814/"}] ### MHC-D-RESEARCH-0464 Evidence: [{"claim":"A 2026 programming-task study found interruptions increased task-completion costs and additional information checking during resumption.","source_id":"RS-21D82B8E0DAE2F6F","role":"supports","note":"The sample was small and one task domain was studied.","locator":"Abstract"}] Sources: [{"id":"RS-21D82B8E0DAE2F6F","title":"Understanding user resumption behavior after task interruptions: An eye-tracking-based empirical study","url":"https://www.sciencedirect.com/science/article/pii/S0141938226002817"}] ### MHC-D-RESEARCH-0459 Evidence: [{"claim":"Reviews of cognitive offloading describe reminders and calendars as external aids that can support prospective memory for future intentions.","source_id":"RS-B973FFFE6DB1D25D","role":"supports","note":"A reminder still needs a detectable cue and a feasible action; too many reminders can become background noise.","locator":"Prospective memory and reminders"},{"claim":"A 2026 study linked boredom and procrastination with failures of prospective memory for delayed intentions.","source_id":"RS-9B5B0E4555B74189","role":"supports","note":"The study does not imply a single causal mechanism for every forgotten delayed task.","locator":"Abstract"}] Sources: [{"id":"RS-B973FFFE6DB1D25D","title":"Meta-cognitive insights into cognitive offloading: mechanisms, interventions, and educational implications","url":"https://www.nature.com/articles/s41599-026-06621-5"},{"id":"RS-9B5B0E4555B74189","title":"From delay to forgetting: how boredom and procrastination disrupt prospective memory","url":"https://www.nature.com/articles/s41599-026-07553-w"}] ### MHC-D-RESEARCH-1261 Evidence: [{"claim":"Two 2026 experiments found that external reminders improved performance while available but reduced later unsupported prospective-memory performance for the previously offloaded intention when reminders were removed.","source_id":"RS-1CB1D793F3672EFA","role":"supports","note":"The finding concerns learning to remember an intention without support. It does not argue against offloading when reliable completion, rather than unaided memory, is the goal.","locator":"Abstract"},{"claim":"A 2026 study with 320 participants found that highly reliable reminders eventually reduced internal intention-related thoughts; when reminder support was unexpectedly withdrawn, retrieval suffered.","source_id":"RS-84367C24BAF92907","role":"supports","note":"This is evidence of adaptation to trusted external support, not a claim that reminders always weaken memory or that people should rehearse every future intention internally.","locator":"Abstract"}] Sources: [{"id":"RS-1CB1D793F3672EFA","title":"Offloading reduces prospective memory learning","url":"https://pubmed.ncbi.nlm.nih.gov/42241083/"},{"id":"RS-84367C24BAF92907","title":"Let it go: How trusted reminders alter intention maintenance","url":"https://pubmed.ncbi.nlm.nih.gov/42613406/"}]