From memstack
Maintains a living STATE.md document tracking current project context, active tasks, blockers, and next steps. Auto-loads at session start or on explicit commands like 'update state' or 'where was I'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/memstack:stateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
*Maintain a living document of where you are right now in a project.*
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.
npx claudepluginhub cwinvestments/memstack --plugin memstackSaves and restores project state between Claude Code sessions. Captures session accomplishments, pending work, and next steps, then stores context in SQLite and markdown handoff files for seamless continuation.
Persists task state across sessions via state.md for cross-session continuity and generates project-map.md. Use for long/noisy sessions, explicit save/compress requests, project mapping, or stale context.
Displays project status, roadmap progress, blockers, and next-action suggestions based on workflow state. Use for progress checks and orientation.