plan
Plan — Persistent Strategic Plans
The Core Idea
Plans capture strategic direction that must survive across sessions. When you start multi-session work or make architectural decisions, save a plan immediately — the reasoning is fresh now and won't be available later. When work is done, mark the plan complete so future sessions don't waste effort on finished goals. A stale plan actively misleads; it's worse than having no plan at all.
When to Create a Plan
Plans matter most when context needs to survive session boundaries. Without a plan, the next session starts from scratch.
- Starting multi-session work — save a plan with goals and approach so the next session knows where to pick up
- After architectural decisions — capture the direction immediately so future sessions don't re-derive or contradict it
- After brainstorming/design sessions — the approved design should outlive the conversation that produced it
- New features spanning multiple sessions — a plan keeps the thread when context compacts or sessions end
- User describes project direction or roadmap — that strategic context is exactly what plans are for
How to Create a Plan
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-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.
2progress-tracking
Proactively checkpoint work progress at key moments without asking permission. Use when completing tasks, fixing bugs, making discoveries, or reaching milestones. Builds persistent memory across sessions.
2