Workspace Continuation
Use this skill for continuity tasks that depend on current workspace state and prior progress.
Inputs
current workspace state - The branch, worktree, changed files, command results, TODOs, tests, and relevant conversation notes.active plan or objective - The requested outcome, current plan, completed work, remaining steps, and known constraints.
Outputs
validated continuation - Focused implementation progress with verification evidence or a precise blocker.handoff - A compact continuation record that lets a fresh session resume without rediscovery.
Continue Work
- Resume from the actual workspace state rather than restarting from scratch.
- Inspect changed files, command output, TODOs, tests, and relevant conversation notes to determine what remains.
- Preserve unrelated user changes and do not redo finished work unless current evidence proves it is wrong.
- Continue with the next concrete action until the task is complete or a real blocker remains.
- Verify the requested outcome with changed files, passing commands, reproduced behavior, or a clear blocker explanation.
Implement A Plan
Use current workspace state and active plan or objective to produce a validated continuation.
- Read the plan and inspect the files, data paths, and tests it affects.
- Confirm the plan still matches the current code. If stale, adapt it conservatively and explain the adjustment.
- Check the worktree before editing and preserve unrelated user changes.
- Make focused changes that follow existing project patterns.
- Run relevant formatter, lint, typecheck, tests, or equivalent validation for touched areas.
Write A Handoff
Use current workspace state and active plan or objective to produce a handoff. Include the objective, current status, working directory, dirty files, files changed or inspected, decisions made, remaining work in priority order, blockers, risks, and assumptions. Keep it specific enough for a fresh session to resume.
Reporting
Finish with what changed or what remains, why it matches the plan or current objective, and the verification evidence.
1---2name: workspace-continuation3description: Generates compact handoffs and continues active plans from workspace state. Use when resuming work, carrying a plan through implementation and validation, or summarizing work for a fresh session without rediscovery.4---56# Workspace Continuation78Use this skill for continuity tasks that depend on current workspace state and prior progress.910## Inputs1112- `current workspace state` - The branch, worktree, changed files, command results, TODOs, tests, and relevant conversation notes.13- `active plan or objective` - The requested outcome, current plan, completed work, remaining steps, and known constraints.1415## Outputs1617- `validated continuation` - Focused implementation progress with verification evidence or a precise blocker.18- `handoff` - A compact continuation record that lets a fresh session resume without rediscovery.1920## Continue Work21221. Resume from the actual workspace state rather than restarting from scratch.232. Inspect changed files, command output, TODOs, tests, and relevant conversation notes to determine what remains.243. Preserve unrelated user changes and do not redo finished work unless current evidence proves it is wrong.254. Continue with the next concrete action until the task is complete or a real blocker remains.265. Verify the requested outcome with changed files, passing commands, reproduced behavior, or a clear blocker explanation.2728## Implement A Plan2930Use `current workspace state` and `active plan or objective` to produce a `validated continuation`.31321. Read the plan and inspect the files, data paths, and tests it affects.332. Confirm the plan still matches the current code. If stale, adapt it conservatively and explain the adjustment.343. Check the worktree before editing and preserve unrelated user changes.354. Make focused changes that follow existing project patterns.365. Run relevant formatter, lint, typecheck, tests, or equivalent validation for touched areas.3738## Write A Handoff3940Use `current workspace state` and `active plan or objective` to produce a `handoff`. Include the objective, current status, working directory, dirty files, files changed or inspected, decisions made, remaining work in priority order, blockers, risks, and assumptions. Keep it specific enough for a fresh session to resume.4142## Reporting4344Finish with what changed or what remains, why it matches the plan or current objective, and the verification evidence.
Nick2bad4u