tticom Durable handoff
Create durable project state. Do not use this skill merely to compact a conversation: a temporary session bridge belongs in the session, not in a repository.
This skill has no prerequisite skills.
Choose the destination
Prefer the repository and path declared by the project profile. Never write durable operational state into a product repository when a separate governance or operations repository owns it. If no durable destination is configured, ask before creating one.
Verify state
Read live state rather than copying an agent summary:
- repository, branch, base SHA, local HEAD, and remote HEAD;
- worktree status and changed paths;
- PR URL, state, checks, reviews, and unresolved threads;
- exact validation commands and results;
- active task, authority source, and required next gate.
If local and remote heads differ, label the work unpublished and do not claim the PR represents it.
For review state, record the latest non-dismissed formal review on the exact live head, including review ID, reviewer, state, commit ID, and server timestamp. Keep author handbacks separate from formal verdicts. Do not let an older approval override a later changes-requested review on the same head.
Write a compact record
Include purpose and outcome, exact repository revisions (including the revision of the installed AgentOps skills when the installation records one), verified versus reported evidence, changed and frozen paths, unresolved risks and comments, and the exact next authorised action.
Reference existing specs, decisions, reports, PRs, and commits by path or URL. Do not paste their contents. Redact credentials, private paths, personal data, and private input details.
Use template.md as the minimum shape.
Verify the handoff
Reread it as a fresh agent. Confirm every next action is executable or explicitly blocked, no candidate is presented as authority, and every SHA is full and matches live remote state.