Agent Skills: Standup

Generate a standup report from Goldfish memory across all projects — use when the user asks for a standup, daily update, progress summary, what they've been working on, or needs a report for a team sync

UncategorizedID: anortham/goldfish/standup

Install this agent skill to your local

pnpm dlx add-skill https://github.com/anortham/goldfish/tree/HEAD/.agents/skills/standup

Skill Files

Browse the full folder contents for standup.

Download Skill

Loading file tree…

.agents/skills/standup/SKILL.md

Skill Metadata

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

Standup

Core Split

  • Goldfish brief explains the direction
  • Checkpoints show what happened
  • Standup ties the two together across projects

Timeframe

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.

Workflow

  1. Recall cross-project activity over the requested timeframe:
recall({ workspace: "all", days: 1 })      // default: daily standup
recall({ workspace: "all", since: "1w" })  // e.g. /standup 1w
  1. For active projects, use recall({ limit: 0 }) or the brief tool to understand current direction.
  2. Group checkpoint clusters into the few accomplishments that mattered.
  3. Synthesize a short report with done, next, and blocked.

Reporting Rules

  • Lead with impact, not motion.
  • Group noisy checkpoint clusters into one accomplishment.
  • Call out blockers plainly.
  • Mention drift when work does not line up with the brief.
  • If no brief exists, say so and rely on checkpoints.

Format

For multiple projects, group by project.

For one project, use:

  • Done
  • Next
  • Blocked

Keep it short enough to read in one pass.