Agent skill · ma08
continue-task
Take over an interrupted tracked task from a previous Codex or Claude session by resolving the existing task home from a tracker ref, task slug, status file, or zellij session, then syncing the status file to the current session and reading the status plus transcript tail before continuing.
What it needs
About 2k tokens when loaded.
What this skill does
Continue Task Use this when the current session needs to resume work that already has a tracked task folder, especially after a provider failure, a dead session, or a clean human handoff. Prefer this over start-new-task when a matching tracked task already exists. Prefer this over save-task-status when the current session first needs to adopt a task that was last owned by another session. Invocation Lower-level overrides: Commands Resolve and inspect the task home first: Explicit overrides when needed: Adopt the resolved task into the current session: If the workflow expects the remote live-session block to move to this session, repeat with --sync-github-issue. Process 1. Resolve the existing task home first. Target by tracker ref or task slug before using low-level overrides. 2. If resolution is ambiguous, stop and surface the candidates. Do not guess. 3. Read the resolved status.md first. Treat task metadata and the local status recap as the source of truth. 4. Use only a short transcript tail as fallback for the final pre-interruption context or when the status file is stale. Do not read the full transcript by default. 5. Adopt the task into the current session by running synctaskmetadata.py against the resolved status file. This should make later get-task-details and save-task-status calls point at the resumed task. 6. When running inside Codex Desktop and codexapp.setthreadtitle is available, rename the calling thread after adoption; omit threadId. Use <Tracker Human ID>: <Tracker Title>, or [no ticker]: <clear natural-language title> when no tracker exists. Do not edit Codex SQLite/JSONL state or ask for a UI refresh. Outside Codex Desktop, or when the native tool is unavailable, skip the rename instead of emulating it. 7. If the resolved task home lives in another repo, treat that workspace path as canonical before making code changes. Do not create a duplicate task folder unless the user explicitly wants a forked task history. 8. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills ma08/continue-task--4e6344