5 Save Progress — Development skill for Claude Code
You are tasked with creating a comprehensive progress checkpoint when the user needs to pause work on a feature.
How to install 5 Save Progress
Installs to ~/.claude/commands/teambrilliant-claude-research-plan-implement-5_save_progress.md
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/teambrilliant/claude-research-plan-implement/HEAD/.claude/commands/5_save_progress.md -o ~/.claude/commands/teambrilliant-claude-research-plan-implement-5_save_progress.md Restart Claude Code, or start a new session, for it to be picked up.
What 5 Save Progress does
Save Progress
You are tasked with creating a comprehensive progress checkpoint when the user needs to pause work on a feature.
When to Use This Command
Invoke this when:
- User needs to stop mid-implementation
- Switching to another task/feature
- End of work session
- Before a break or context switch
Process
Step 1: Assess Current State
- Review conversation history to understand what was being worked on
- Check git status for uncommitted changes
- **Identify the ac
Alternatives in Development
- Quick Plan — Create a detailed implementation plan based on the user's requirements provided through the USER_PROMPT variab 3.4k ★
- /remember — Save a finding or successful pattern to persistent hunt memory 1.2k ★
- Frontend Slides Editable — Editable HTML presentation skill for Codex/Claude Code with drag-resize editing, slide reordering, local save/ 466 ★
Full documentation available on GitHub
View Source RepositoryRelated Skills
Save State
Capture discoveries, decisions, and progress for seamless resumption
Plan With Team
Create a detailed implementation plan based on the user's requirements provided through the USER_PROMPT variab
Arsave
AgentRecall full save — journal + palace + awareness + insights in one shot.
Mem Save
Save a curated session-level summary to history. Use this at meaningful milestones — end of session, before a
02 Revision History
Give Inkwell a revision history: snapshot a post's prior state on every meaningful save, let the
Memo
Memo MCP -- save and restore conversation across agents
Related Agents
Neo Shadow
Memory keeper. MUST BE USED to save session context into the second brain (.neo/brain/) — at task boundaries,
Commit
Stage and commit changes, or open a pull request. Trigger when the user asks to commit, make a commit, save ch
Context Engine
Context window management — tracks tool call count, auto-detects when context fills up, triggers state save +