AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Resume Handoff

skill-danaidev-agent-skills-resume-handoff · by DanAIDev

Resume work from a handoff stored under .ai/shared/handoffs. Use when a user asks to resume a handoff, provides a handoff path, or provides a ticket ID like ENG-1234.

↗ Repository
— No reviews yet
0 installs
4 views
0.0% view→install

Install

$ agentstack add skill-danaidev-agent-skills-resume-handoff

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Resume Handoff? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Resume Handoff

Overview

Read a handoff document, validate its context against the current repo state, and propose a concrete next-step plan before changing code.

Entry Handling

A) Path provided

  • Read the handoff file fully.
  • Read any referenced artifacts (plans, research, specs) the handoff calls out.
  • Validate file references from “Recent Changes” and “Learnings”.
  • Summarize findings and propose next actions; ask for confirmation.

B) Ticket provided (e.g., ENG-1234)

  • Look for handoffs in .ai/shared/handoffs/ENG-1234/.
  • List files in the directory and select the most recent by the filename timestamp YYYY-MM-DD_HH-mm-ss.
  • If no files exist, ask the user for the path.
  • Then follow the same flow as “Path provided.”

C) No parameter provided

Respond with a short prompt asking for either a path or a ticket ID, and offer an example.

Analysis Flow

1) Ingest handoff content

  • Extract tasks and statuses, recent changes, learnings, artifacts, and action items.

2) Read referenced artifacts

  • Read any linked documents, especially under:
  • .ai/shared/plans/
  • .ai/shared/research/
  • other explicit paths mentioned in the handoff

3) Validate against repo state

  • Confirm file references still exist.
  • Check for divergences (missing files, moved code, changed behavior).

4) Report and confirm Present a structured summary and ask for confirmation before making changes.

Use this response pattern:

I've analyzed the handoff from [date] by [author].

Original tasks:
- [Task] — [Status in handoff] → [Current verification]

Key learnings (validated):
- [Learning] — [Still valid / changed]

Recent changes (verified):
- [path/to/file.ext:line] — [Present / missing / modified]

Artifacts reviewed:
- [doc] — [key takeaway]

Recommended next actions:
1. [Action]
2. [Action]

Shall I proceed with action 1, or do you want to adjust the approach?

Guidelines

  • Be thorough but concise; focus on what enables the next agent to act.
  • Do not assume the handoff state is still valid; verify.
  • Avoid big code blocks; use file references.
  • Ask for confirmation before making code changes.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills