skills.rest
mark-torres10
mark-torres10COMMUNITY
Explore all skills by this author →
GitHub

handoff

Generates a structured end-of-session handoff.md summarizing completed work, remaining to-dos, and PR status.

3|Updated Feb 15, 2025
Search Tags:#documentation#markdown#pull request#agent workflow#handoff#session summary#to-do tracking
One-click install
npx skills add https://github.com/mark-torres10/ai_tools --skill handoff-mark-torres10
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/mark-torres10/ai_tools/tree/main/skills/handoff
Command: npx skills add https://github.com/mark-torres10/ai_tools --skill handoff-mark-torres10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a work session ends or an agent switches, context about what was done, what remains, and where the plan lives is easily lost. This Skill produces a concise handoff.md file so the next agent or human can resume work quickly without re-reading the entire session. ## Core Features & Use Cases - Structured handoff file: Creates a handoff.md at the repo root with exactly three sections (Context, What's done, Next), each limited to one paragraph. - Plan and PR discovery: Searches .cursor/plans/ then docs/plans/ for plan sources, and resolves the PR URL via gh or records the branch and commit if no PR exists. - Explicit resume point: Enumerates remaining to-dos and marks the last in-progress task with a "Last left off" marker. - Use Case: At the end of a coding session on a feature branch, run this Skill to produce a handoff file so a teammate or another agent can pick up the PR, read the key files, and continue the remaining to-dos. ## Quick Start Ask the agent to generate an end-of-session handoff summarizing what was done, the remaining to-dos, and the PR link into handoff.md.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I create a handoff document at the end of a coding session?▼

Run the handoff Skill at the end of your session. It writes a handoff.md file at the repo root with three sections covering context, completed work, and next steps, including the PR link and remaining to-dos.

What should an agent handoff summary include?▼

A good handoff includes the PR URL or branch state, the plan files used, a brief summary of completed work, key files to read next, remaining to-dos, and an explicit marker naming the last in-progress task.

Where does the handoff Skill look for plan files?▼

It searches .cursor/plans/ first, preferring the most recently modified files, then falls back to docs/plans/. If no clear plan source exists, it stops and asks which markdown files define the intended work.

What happens if there is no PR for the current branch?▼

The Skill attempts to resolve the PR using gh. If no PR exists, it records "no PR yet" in handoff.md along with the branch name and latest commit SHA instead of inventing a link.

When should I not use a session handoff file?▼

Do not use it mid-session as a running log; it is designed strictly for end-of-session summaries. Also avoid it when no plan or PR context exists, since the Skill will stop and ask rather than fabricate details.

Related Skills

Explore More Software Engineering Skills→
f4irlinef4irline
5

progress-doc

Create and update standardized markdown progress documents for feature branches.

Community
Basic
sburlsburl
26

handoff

Generate a structured handoff document capturing branch, commits, open PRs, failing tests, and next steps.

Community
Intermediate
Archive228Archive228
746

pr-from-diff

Generate structured pull request descriptions from commit messages and changes.

Community
Basic
Vincri126Vincri126

Continuity Package — End-of-Session Skill

Package session artifacts into a validated continuity ZIP for handoff.

Community
Advanced