Workdocs Handoff Update

This workflow updates workdocs so a new session (or a different agent/human) can resume with minimal rediscovery.

Purpose & Scope

Use this workflow when:

• •You are ending a session or expect a context reset.
• •Work is mid-flight and you need durable state for resumption.
• •You need to hand off to a reviewer or another agent.

Out of scope:

• •Writing new implementation code (this workflow is documentation maintenance only).

Inputs & Preconditions

Inputs:

• •The active workdocs folder path (recommended: workdocs/active/T-YYYYMMDD-slug/)
• •What changed since the last update (files, decisions, known issues)
• •Next executable steps and validation commands

Preconditions:

• •The workdocs folder exists and contains (at minimum): plan.md, context.md, tasks.md

Steps

1. •

   Update context.md (state + decisions)

   • •Record:
     • •What is completed vs in progress vs blocked
     • •Key decisions and why they were made
     • •The exact files touched and what each change achieved
     • •Any required human approvals/inputs and why
     • •The next 1鈥? concrete steps to resume work
   • •Keep it factual; avoid speculative 鈥渕aybe鈥?notes.
2. •

   Update tasks.md (verifiable checklist)

   • •Check off completed items.
   • •Add newly discovered tasks (with acceptance criteria).
   • •Mark the single current in-progress item (if applicable).
   • •Reorder to reflect the next executable sequence.
3. •

   Update plan.md (machine-readable + narrative)

   • •In the YAML todos header:
     • •Ensure status reflects reality (exactly one in_progress if work is active).
     • •Ensure each todo has explicit outputs and checks.
     • •Add/adjust dependencies and gates to match current constraints.
   • •In the narrative:
     • •Update Validation (what must be run/checked next)
     • •Update Definition of Done (what 鈥渄one鈥?means now)
     • •Update Risks & Gates (new risks discovered; stop-the-line conditions)
4. •

   *Capture the 鈥渞esume command set鈥?

   • •Add a short list of commands that the next session should run first (lint/check scripts, targeted tests, regeneration steps).
   • •If any command output matters, note what 鈥淥K鈥?looks like.
5. •

   Final sanity check

   • •Confirm the workdocs contain:
     • •Current status, next steps, and blockers
     • •File pointers and validation commands
     • •Any approval gates clearly stated

Outputs

• •Updated workdocs in workdocs/active/T-YYYYMMDD-slug/:
  • •context.md reflects current state and decisions
  • •tasks.md reflects progress and next executable items
  • •plan.md reflects current todos, outputs/checks, and gates

Safety Notes

• •Do not include secrets, tokens, or real credentials.
• •Do not edit tool-owned marker blocks (routing/ability indexes) as part of this workflow.

Related