goal-handoff-persistencelisted

# Goal + Handoff Persistence External memory for rotating agents. Use this skill when the task may outgrow the current context window, span multiple phases, require restart or resume, or involve enough state that losing context would cause repeated work, direction drift, unsafe actions, or forgotten decisions. This is a lightweight persistence protocol. Do not create a large project structure by default. Start with a durable task working directory and two files: - `goal.md`: why the task exists, what success means, constraints, current direction, and acceptance criteria. - `handoff.md`: current state, completed actions, evidence, risks, backups, failures, next steps, and resume instructions. These files are the external memory for context compacting, restarts, session changes, model changes, and handoffs. Assume another agent with no reliable memory may take over at any time. Write `goal.md` and `handoff.md` so that agent can continue without relying on chat history, compressed summaries, or guesswork. ## Mandatory State-Update Contract These rules override any looser wording elsewhere in this skill: 1. **Goal write gate**: Update `goal.md` if and only if the user explicitly changes the task objective, deliverable, scope, core acceptance criteria, or core constraints, or explicitly asks to update `goal.md`. Never change it for routine progress, research, diagnostics, implementation, failures, fixes, validation, or completion status. 2. **Bounded file guard**: Before