Menü
Use when returning to a project after time away, switching harnesses, or handing work off to another agent, to produce a structured session-resumption summary from the active brief, recent checkpoints, and git delta.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Use when the user asks for a standup, daily update, progress summary, or cross-project report built from Goldfish briefs and checkpoints
Use when starting a new session, after context loss, searching for prior work, or when the user asks what happened previously and needs Goldfish memory restored
Use when starting multi-session work, capturing approved project direction, updating goals or constraints, or when the user asks for durable strategic context that should persist across sessions
Use when the user asks for progress against current project direction, wants a status check on the active brief, or needs evidence-backed assessment across briefs, checkpoints, and docs/plans
Save developer context to Goldfish memory — checkpoint at meaningful milestones, not after every action
Basierend auf der SOC-Berufsklassifikation
| name | handoff |
| description | Use when returning to a project after time away, switching harnesses, or handing work off to another agent, to produce a structured session-resumption summary from the active brief, recent checkpoints, and git delta. |
Three triggers:
/handoff differs from neighbors/standup aggregates across projects for a daily-update audience (you, looking at what you did everywhere)./recall returns raw checkpoints for an in-session agent that needs memory restored./handoff synthesizes within one project into a single resumption document for a different agent or a returning you, picking up cold.Pick by audience and scope.
Four steps. Run them in order, then compose the document.
recall({ limit: 0 })
This returns the active brief without pulling checkpoints. If no brief is active, note that in the output and keep going.
recall({ days: 3, limit: 10, full: true })
Default window is 3 days. If the user passed a time argument (for example --since 2d or --since 4h), honour it:
recall({ since: "2d", limit: 10, full: true })
full: true is required so you see next, unknowns, and git context.
git rev-parse --abbrev-ref HEAD
git status -s
git log -1 --oneline
Three short commands, three short outputs. No fancy flags.
Compose one markdown document using the sections in Output Format below. Do not dump tool output verbatim; distill it.
One markdown document, sections in this order:
## Direction3-5 lines summarizing the active brief: goal, key constraints, current status. If no brief is active, write "No active brief" and lean on the checkpoint trail for direction.
## State at handoffgit rev-parse --abbrev-ref HEAD)git log -1 --oneline)git status -s), or "clean working tree"Keep this compact. Three bullets maximum.
## Recent activityLast 5-10 checkpoints, dense format. Group adjacent checkpoints into logical milestones when they tell a continuous story; otherwise list chronologically. For each checkpoint include:
summary field)When clustering, lead the cluster with a one-line milestone header, then nest the supporting checkpoints beneath it.
## Next stepsPull from the most recent checkpoint's next field. Add any success criteria from the active brief that do not yet have checkpoint evidence. Short bullets; concrete actions.
## Open questionsPull from recent checkpoints' unknowns fields and from any open items in the active brief. If there are no open questions, say so plainly.
## Source pointersFile paths the receiving agent can read deeper from:
.memories/briefs/<id>.md).memories/<date>/<time>_<hash>.md)docs/plans/ documents referenced by the brief or a recent checkpointThe skill takes one optional argument: a time window (--since 2d, --since 4h).
Default behaviour:
Users who want a fixed window should pass --since.
Native harness memory does not survive harness switches. Goldfish's evidence ledger (briefs plus checkpoints) does, and /handoff turns that ledger into a portable resumption document. It is the explicit answer to "how does work resume on a different harness or a different agent?"