continue-task

Resume interrupted tracked coding agent tasks by syncing metadata and status files.

28|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/ma08/botfiles --skill continue-task-ma08
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continue-task
Source: https://github.com/ma08/botfiles/tree/main/claude/skills/continue-task
Command: npx skills add https://github.com/ma08/botfiles --skill continue-task-ma08

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When coding agent sessions are interrupted by provider failures, dead sessions, or human handoffs, you lose all context of your in-progress tracked tasks and have to manually reconstruct where you left off. This Skill eliminates that tedious manual work by automatically adopting and resuming existing tracked tasks.

Core Features & Use Cases

  • Multi-Method Task Resolution: Locate existing tracked task homes using tracker references, task slugs, status files, or zellij session names, with safeguards against ambiguous matches.
  • Context Sync & Adoption: Automatically sync task metadata to the current session and pull the latest status plus recent transcript tail to get up to speed on prior progress.
  • Use Case: If your Claude Code session crashed mid-way through a tracked GitHub issue task, use this Skill to resume the existing task folder instead of starting over and losing all prior work.

Quick Start

Use the continue-task skill to resume the tracked task associated with the GitHub issue #124 that was interrupted in your last coding agent session.

Frequently Asked Questions about continue-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume interrupted coding agent tasks without losing context?

You can resume interrupted coding agent tasks by resolving the existing task home, syncing metadata to the current session, and pulling the latest status file and transcript tail to recover prior progress.

How does cross-session task tracking work with zellij?

Cross-session task tracking with zellij locates existing task homes using tracker references, task slugs, status files, or zellij session names to adopt and sync metadata into a new session for uninterrupted work.

Can I adopt an existing tracked task folder into a new coding agent session?

Yes, you can adopt an existing tracked task folder into a new session by resolving the task home through its slug or status file, then syncing metadata and surfacing the latest task state.

What is the best way to recover from a crashed coding agent session?

The best way to recover from a crashed coding agent session is to use multi-method task resolution to locate the interrupted tracked task, sync its metadata, and review the recent transcript tail to resume work.

Does this task resumption method work with tracked GitHub issue folders?

Yes, this task resumption method works with tracked GitHub issue folders by resolving the associated task home, syncing the latest status file, and pulling recent progress to continue the work.

What happens if multiple task slugs match during cross-session status sync?

Multi-method task resolution includes safeguards against ambiguous matches during cross-session status sync, ensuring the correct tracked task home is identified before adopting and syncing metadata.