Menú
Use when the user asks for a standup, daily update, progress summary, or cross-project report built from Goldfish briefs and checkpoints
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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
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 | standup |
| description | Use when the user asks for a standup, daily update, progress summary, or cross-project report built from Goldfish briefs and checkpoints |
Default to yesterday (days: 1). If the user gives a timeframe — as an argument (/standup 7d, /standup 1w, /standup 3d) or in words ("last week", "since Friday") — pass it through as since (accepts m/h/d/w units) or days. A Monday standup after a weekend usually wants 3d; a weekly catch-up wants 1w.
recall({ workspace: "all", days: 1 }) // default: daily standup
recall({ workspace: "all", since: "1w" }) // e.g. /standup 1w
recall({ limit: 0 }) or the brief tool to understand current direction.For multiple projects, group by project.
For one project, use:
DoneNextBlockedKeep it short enough to read in one pass.