skills/resume-task/SKILL.md
Resume work on a task after a session crash or timeout
npx skillsauth add gioe/tusk resume-taskInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Recovers context after a session crash/timeout and continues the implementation workflow.
tusk branch-parse
{"task_id": N} → use that ID and proceed to Step 2/resume-task 42)tusk task-start <TASK_ID> --force --force-session
The --force flag ensures the workflow proceeds even if the task has no acceptance criteria (emits a warning rather than hard-failing). The --force-session flag explicitly reuses an active session when resuming from outside the recorded task workspace.
Returns JSON with four keys:
task — full task row (summary, description, priority, domain, assignee, complexity)
progress — checkpoints (most recent first); first entry's next_steps = resume point
criteria — acceptance criteria (id, criterion, source, is_completed)
session_id — reuses open session if one exists
Hold onto session_id for later use.
git log --oneline $(git merge-base HEAD main)..HEAD
Task: [TASK-<id>] <summary> (priority, complexity, domain)
Description: <description>
Progress Checkpoints: (most recent first)
- <next_steps> | <commit_hash> | <files_changed>
(or "No prior checkpoints found.")
Acceptance Criteria:
- [x] completed criterion
- [ ] pending criterion ← defines remaining work
Recent Commits: (git log output from Step 3)
Next Steps: <most recent checkpoint's next_steps, or incomplete criteria if none>
Continue from /tusk step 4 onward (subagents → explore → implement → commit → criteria → finalize). Steps 1-3 are already done.
tusk criteria done <cid>tusk progress <TASK_ID> --next-steps "<what remains>"
tusk lint before pushing (advisory only)Read file: <base_directory>/../tusk/SKILL.md
Where <base_directory> is the resume-task skill's base directory.data-ai
Autonomously work through the backlog — dispatches /chain for chain heads, /tusk for standalone tasks, repeating until empty
tools
Investigate the scope of a problem and form an honest assessment — task creation is optional
data-ai
Groom the backlog by closing completed tickets, removing redundant/stale tickets, reprioritizing, and assigning agents
tools
File a GitHub issue against the tusk repo itself — tusk bugs, CLI limitations, skill improvements, or missing features. Use anytime the user identifies a gap in tusk (not in their own project's code).