agentsclimarketplace

Resume from

Skill tranhieutt/software_development_department/.claude/skills/resume-from

Restores cognitive state from an atomic checkpoint in .tasks/checkpoints/[task_id].md, enabling instant recovery at the exact point of failure without re-running the full task.From its SKILL.md

Install
npx -y skills add tranhieutt/software_development_department --skill resume-from

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

3.6 KB, 791 tokens by cl100k_base, as published. Nobody here has run it

Resume From Checkpoint

Restore the working context of a specific task from its atomic checkpoint at .tasks/checkpoints/[task_id].md, then continue execution from the exact next step β€” without re-running completed work.

Steps

1. Validate argument

$ARGUMENTS must contain a task_id. If missing or empty:

❌ Usage: /resume-from <task_id>
   Example: /resume-from 042
   Example: /resume-from auth-api

Available checkpoints:
[Run: ls .tasks/checkpoints/ and list files excluding .gitkeep]

Stop here if no task_id is provided.

2. Load checkpoint

Read .tasks/checkpoints/[task_id].md.

If the file does not exist:

❌ No checkpoint found for task: [task_id]
   Expected: .tasks/checkpoints/[task_id].md

Available checkpoints:
[List files in .tasks/checkpoints/ excluding .gitkeep]

Tip: Run /save-state [task_id] first to create a checkpoint.

Stop here if file is missing.

3. Parse and surface checkpoint

Extract the following fields from the checkpoint and display them clearly:

πŸ” Resuming task: [task_id]
   Agent:         [agent_id]
   Saved at:      [saved_at]
   Retry count:   [retry_count]

πŸ“„ Output Snapshot (last known state):
   [output_snapshot content]

βœ… Completed Steps:
   [completed steps list]

⏭️  Next Step:
   [next_step content]

❓ Open Questions:
   [open_questions content β€” or "None" if empty]

πŸ“ Files Modified So Far:
   [files_modified list]

4. Apply exponential backoff if retrying

Check retry_count in the checkpoint frontmatter:

  • retry_count = 0 β†’ proceed immediately, no wait
  • retry_count = 1 β†’ wait 2s before continuing
  • retry_count = 2 β†’ wait 4s before continuing
  • retry_count = 3 β†’ wait 8s before continuing
  • retry_count >= 4 β†’ surface a warning:
⚠️  This task has failed [retry_count] times.
    Continuing, but consider escalating to a senior agent or the user
    if the same error recurs.

Then increment retry_count and update backoff_next_s (double the previous value, max 64s) in the checkpoint file before proceeding.

5. Resume execution

Hand off context to the appropriate agent (agent_id from checkpoint) with the following instruction:

"You are resuming task [task_id]. The completed steps and output snapshot above are already done β€” do NOT repeat them. Your only job is to execute the Next Step listed above and continue from there."

6. Update checkpoint on success

When the task completes successfully, update .tasks/checkpoints/[task_id].md:

  • Set status: completed
  • Set completed_at: [ISO timestamp]
  • Append to ## Completed Steps

Print:

βœ… Task [task_id] completed successfully.
   Checkpoint updated β†’ .tasks/checkpoints/[task_id].md (status: completed)

Checkpoint lifecycle

/save-state [task_id]   β†’ creates  .tasks/checkpoints/[task_id].md (status: in_progress)
/resume-from [task_id]  β†’ reads checkpoint, increments retry_count, resumes
                        β†’ on success: sets status: completed

Completed checkpoints are kept for audit β€” they are never auto-deleted. To list all checkpoints: ls .tasks/checkpoints/

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.