progress-tracking
Progress Tracking Skill
Purpose
Build persistent memory by proactively checkpointing important moments in development. This creates a detailed history that survives crashes, context resets, and time away from the project.
When to Activate
Checkpoint automatically at these key moments:
🎯 Task Completion
- Feature implemented and tested
- Bug fixed and verified
- Refactoring completed
- Tests written and passing
🔍 Important Discoveries
- Found root cause of a bug
- Identified architecture pattern
- Discovered unexpected behavior
- Located critical code sections
More from anortham/goldfish
recall
Restore context from Goldfish developer memory — use when starting a new session, after context loss, searching for past work, or when the user asks what happened previously, wants to find old decisions, or needs cross-project context
13plan
Create and manage persistent plans in Goldfish memory — use when starting multi-session work, making architectural decisions, or when the user discusses project direction, roadmaps, or design decisions that need to persist across sessions
13plan-status
Assess progress against the active Goldfish plan using checkpoints and plan data — use when the user asks about project progress, how things are going, what's been accomplished, or wants a status check against their plan
12checkpoint
Save developer context to Goldfish memory — checkpoint at meaningful milestones, not after every action
12standup
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
11session-memory
Automatically restore session context from persistent memory at the start of every coding session. Use this skill IMMEDIATELY when starting work to recall previous checkpoints, active plans, and git context. MANDATORY for context restoration.
2