Workspace resume

Workspace Resume

Use this skill when the main risk is starting from the wrong folder, stale context, or an old plan instead of the actual current workspace.

Success Criteria

• The real workspace or repo is identified.
• Pointer folders, handoff files, and current ledgers are separated from source-of-truth files.
• Dirty worktree state and likely user changes are preserved.
• The next actionable slice is recovered without re-planning the whole project.
• Verification run or remaining verification gap is named.

Workflow

1. Pin the requested context

   • Identify the folder, repo, thread, task name, or date the user referenced.
   • Do not assume the current folder is the real repo.

2. Read pointer and state files first

   • Check AGENTS.md, README*, CURRENT_WORK*, HANDOFF*, KEY_DECISIONS*, task ledgers, package indexes, and transfer artifacts.
   • Note which files are coordination notes and which are source-of-truth project files.

3. Locate the real workspace

   • Inspect the repo root, branch, recent commits, and git status.
   • If the folder is a pointer or export package, follow the pointer before editing.
   • Never revert unrelated changes.

4. Recover the current task state

   • Use recent session names, memory, rollout summaries, and local ledgers only as much as needed.
   • Prefer exact local evidence over broad memory.
   • Extract the latest accepted decision, current blocker, and next smallest slice.

5. Verify cheaply when useful

   • Run existing focused tests, build checks, linters, or smoke checks when they are safe and relevant.
   • If verification is too expensive or blocked, say exactly what remains unverified.

6. Report before changing code

   • Name the real repo, authoritative files, dirty-state warning, recovered next slice, and verification status.
   • Then proceed with edits only if the user's request calls for action.

Output Template

**Recovered State**
- Real workspace:
- Source-of-truth files:
- Current branch/state:
- Latest accepted decision:
- Next slice:
- Verified:
- Unverified:

Common Traps

• Treating a projectless agent folder as the source repo.
• Restarting discovery from scratch when a ledger already names the next slice.
• Using memory as current fact without checking cheap local evidence.
• Reverting or cleaning up user changes while trying to get a clean state.
• Producing a long handoff when the user needs the next action.