From memstack
Maintains project state in .claude/STATE.md: updates with tasks, decisions, blockers, next steps, git status, modified files; reads on session start or 'where was I'.
npx claudepluginhub cwinvestments/memstack --plugin memstackThis skill uses the workspace's default tool permissions.
*Maintain a living document of where you are right now in a project.*
Saves and restores project state between Claude Code sessions: captures accomplishments, progress, git status, next steps, issues; stores in SQLite and markdown; generates handoff prompts. Use for 'save project', handoff, or low context.
Writes CONTINUE_HERE.md capturing session state with objective, completed, in-progress, next-steps, and context sections for handoff to new Claude Code sessions. Use for unfinished work or preserving git-insufficient context.
Manages coding session state: saves/restores git-based checkpoints, indexes project structure, loads components into context, checks git/tasks status.
Share bugs, ideas, or general feedback.
Maintain a living document of where you are right now in a project.
When this skill activates, output:
๐ State โ Updating project state...
Then execute the protocol below.
| Context | Status | Priority |
|---|---|---|
| User says "update state", "save state", "project state" | ACTIVE โ update STATE.md | P1 |
| User says "where was I", "where did I leave off" | ACTIVE โ read and present STATE.md | P1 |
| User starts a session and STATE.md exists | ACTIVE โ read silently, use as context | P2 |
| User says "save diary" or "log session" | DORMANT โ Diary handles full session logs | โ |
| User says "save project" or "handoff" | DORMANT โ Project skill handles lifecycle | โ |
| User asks to recall past sessions | DORMANT โ Echo handles historical recall | โ |
.claude/ directory:
{project_dir}/.claude/STATE.md
Gather current state:
Check git status for uncommitted work:
git status --short
Write STATE.md to the project's .claude/ directory:
# Project State
*Last updated: {YYYY-MM-DD HH:MM}*
## Currently Working On
{Active task or phase โ be specific}
## Decisions Made
- {Decision}: {Rationale}
## Blockers
- [ ] {Blocker description}
## Next Steps
1. {Immediate next action โ specific enough to start cold}
2. {Following action}
## Recently Modified Files
- {file path} โ {what changed}
## Uncommitted Changes
{List any unstaged/uncommitted work, or "None โ clean working tree"}
Confirm with a brief summary of what was saved.
| Skill | What it tracks | When |
|---|---|---|
| State | Current snapshot โ where you are right now | During session, living document |
| Diary | Historical log โ what you did in a session | End of session, append-only |
| Project | Project lifecycle โ handoff between sessions | Session boundaries |
| Work | Task list โ what needs to be done | When planning/tracking todos |
State is the present tense complement to Diary's past tense. State tells you where to resume; Diary tells you what happened.
{project_dir}/.claude/STATE.md โ updated living documentUser: "update state"
๐ State โ Updating project state...
Saved: C:\Projects\AdminStack\.claude\STATE.md
Currently: Building CC Monitor notification system
Blockers: None
Next: Wire up WebSocket events to notification dropdown
This will auto-load next session for seamless pickup.