Menu
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
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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 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
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.
| name | brief |
| description | 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 |
Goldfish brief = durable direction.
docs/plans/ owns implementation specs and task breakdowns.Do not copy a harness task list or docs/plans/ checklist into the brief. Link to execution artifacts instead.
Keep the brief compact and stable:
docs/plans/... or other design docsExitPlanMode plan blobbrief({
action: "save",
title: "Brief API surface around strategic context",
content: "## Goal\n\nRename the forward-looking artifact to brief.\n\n## Why Now\n\nHarnesses now own execution planning.\n\n## Constraints\n\nKeep one-release compatibility for plan callers.\n\n## Success Criteria\n\nRecall, skills, hooks, and docs all present brief as canonical.\n\n## References\n\n- docs/plans/2026-04-16-brief-repositioning-design.md",
tags: ["memory", "migration"],
activate: true
})
Only one brief should be active per workspace.
brief({ action: "get" }) gets the active brief.brief({ action: "list" }) shows saved briefs.recall({ limit: 0 }) shows the active brief without loading checkpoints.docs/plans/ for execution detail.plan, translate it to brief semantics unless the user is asking about a legacy artifact on purpose.