Continue Work Skill

Description

This skill enables seamless session continuity by reading local state artifacts — uncommitted git changes, todo files, autonomous state, and recent git history — to reconstruct context and resume work without the user needing to re-explain anything.

Instructions

When the user says "continue", "pick up where I left off", or invokes this skill, follow this workflow:

Step 1: Gather Session Artifacts

Check these sources in order:

Copy
# 1. Check for autonomous state file
cat .claude/autonomous-state.json 2>/dev/null

# 2. Check for todo/task files
cat TODO.md 2>/dev/null
cat .claude/todos.json 2>/dev/null

# 3. Check git state for uncommitted work
git status --short
git stash list

# 4. Check recent commits for context
git log --oneline -10

# 5. Check for work-in-progress branches
git branch --list '*wip*' '*draft*' '*fix/*' '*feat/*'

# 6. Check for recent file modifications
git diff --stat
git diff --cached --stat

Step 2: Reconstruct Context

Build a status report:

Copy
## Session Recovery Report

### Autonomous Task (if found)
- Task: "Migrate to ESM modules"
- Progress: 7/12 steps complete
- Last step: "Convert src/middleware/"
- Next step: "Update test imports"

### Uncommitted Changes
- Modified: src/utils/format.ts (added ESM exports)
- Modified: src/services/auth.ts (converted imports)
- Staged: 2 files ready to commit

### Recent Context (last 5 commits)
- abc123 — feat: convert utils to ESM
- def456 — feat: convert services to ESM
- ...

### Open TODOs
- [ ] Fix circular dependency in auth module
- [ ] Update jest config for ESM
- [ ] Run full test suite

Step 3: Propose Next Action

Based on the recovered context, suggest the logical next step:

Copy
## Recommended Next Action

Based on your session state, you were migrating to ESM modules.
Step 7/12 is next: "Update test imports".

Shall I:
1. Continue the ESM migration from step 7?
2. Commit the 2 staged files first?
3. Something else?

Rules

• NEVER make assumptions about what the user was doing — always check artifacts first
• If no artifacts are found, check git log and recent file modifications as fallback
• If still nothing found, honestly say "I don't see any previous session state" and ask what they want to do
• Present findings as a summary — don't dump raw git output
• Ask for confirmation before resuming any multi-step operation
• If there are uncommitted changes, mention them prominently (risk of data loss)
• Check for stashed changes — users often forget about these
• If multiple work streams are detected, ask which one to continue

Examples

User: Continue Action: Check all artifact sources, build recovery report, suggest next action

User: What was I working on? Action: Same recovery workflow, but present as informational report without action suggestion

User: Resume the migration Action: Find migration-related state, confirm progress, continue from last incomplete step