Install
$ agentstack add skill-enkrateialucca-skills-resume-handoff ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
About
Resume Work from a Handoff
You are resuming work from a handoff document. Handoffs contain critical context, learnings, and next steps from a previous agent session — read them fully and verify them against reality before doing anything.
Initial Response
When this skill is invoked:
- If a handoff file path was provided (e.g.
handoffs/2026-03-17_14-30-00_refactor-auth.md):
- Read the handoff document fully (no limit/offset)
- Read any plan or reference documents it links to — do NOT delegate these critical files to sub-agents
- Begin the analysis process below
- If no path was provided:
- Look for a
handoffs/directory in the project root - If it exists, list its contents and pick the most recent file (by filename timestamp)
- If no handoffs directory or no files found, respond:
`` No handoffs found. You can provide a path directly to a handoff file. ``
- Then wait for input
Process
Step 1: Read and Analyze
- Read the handoff document completely
- Extract all sections: tasks, changes, learnings, artifacts, next steps
- Read the key files referenced in the handoff:
- Files from "What Changed" to verify modifications are still present
- Files from "Key Learnings" to understand context
- Files from "Artifacts Produced" to review what was built
- Check for drift: have files changed since the handoff was written?
Step 2: Present Analysis
Present a concise summary to the user:
Resuming from handoff: [date] — [topic]
**Tasks:**
- [Task 1]: [status from handoff] → [current state]
- [Task 2]: [status from handoff] → [current state]
**Key Learnings Still Valid:**
- [Learning 1 with file reference]
- [Learning 2 with file reference]
**Changes Verified:**
- [Change 1] — [present / missing / modified]
**Recommended Next Steps:**
1. [Most logical next action from handoff]
2. [Second priority]
Shall I proceed with [step 1], or would you like to adjust?
Wait for confirmation before proceeding.
Step 3: Begin Work
- Create a task list from the handoff's next steps
- Start with the first approved task
- Reference learnings from the handoff throughout
- Apply patterns and approaches documented in the handoff
Guidelines
- Read everything first. Never assume the handoff state matches reality — verify file references still exist and code hasn't changed.
- Be interactive. Present findings before starting. Get buy-in on the approach.
- Leverage handoff wisdom. Pay special attention to "Key Learnings" — these save you from repeating mistakes.
- Consider creating a new handoff when done. If you don't finish, use the create-handoff skill so the next session can continue the thread.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: EnkrateiaLucca
- Source: EnkrateiaLucca/skills
- License: MIT
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.