skills.rest
MartinoPolo
MartinoPoloCOMMUNITY
Explore all skills by this author →
GitHub

mp-handoff

Create and update HANDOFF.md with session progress and continuity context.

1|Updated Feb 7, 2026
Search Tags:#continuity#project context#decision log#session handoff#task list#handover notes
One-click install
npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-handoff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mp-handoff
Source: https://github.com/MartinoPolo/mpx-claude-code/tree/main/skills/mp-handoff
Command: npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

mp-handoff prevents valuable context from being lost between Claude Code sessions by creating or updating a single, developer-readable session summary that a new agent can immediately use.

Core Features & Use Cases

  • Session progress recap: Captures what was accomplished, with enough detail (including file paths and specific changes) to avoid re-discovery.
  • Decision and rationale preservation: Records key decisions, alternatives considered, and why the chosen approach was taken.
  • Continuity for future work: Merges new progress into an existing HANDOFF.md when present, includes task status, and highlights next steps, critical files, and working memory/constraints.

Quick Start

Use the mp-handoff skill when you are ready to end a session and want to persist progress into HANDOFF.md for the next developer to continue.

Frequently Asked Questions about mp-handoff

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

FAQPage Schema
How do I preserve project context and decision logs for a session handoff?▼

To preserve project context for a session handoff, generate a HANDOFF.md file in your project root that summarizes accumulated decisions, task status, and next steps for the next agent to read.

What is the best way to maintain continuity across multi-session development?▼

Maintaining multi-session development continuity requires merging current task status into an existing HANDOFF.md file, optionally enriching it with context from .mpx/CONTEXT.md and .mpx/DECISIONS.md files.

How does a session handoff briefing transfer working memory to a new agent?▼

A session handoff briefing transfers working memory by writing an updated 20 to 200 line summary detailing accomplished tasks, critical file paths, dead ends encountered, and project constraints for the new agent.

What should be included in handover notes when switching tasks?▼

Handover notes for task switching should include a recap of specific changes, decision rationale, alternatives considered, task list status, and highlighted next steps to prevent context re-discovery.

Can I use existing project context files to enrich my session handoff summary?▼

Yes, you can enrich your session handoff summary by reading existing HANDOFF.md files and optionally pulling accumulated project history from .mpx/CONTEXT.md and .mpx/DECISIONS.md before merging updates.

Why does my session progress get lost between development agents?▼

Session progress gets lost between agents when end-of-session handoffs fail to persist working memory, decision rationale, and task status into a developer-readable project root summary file.

Related Skills

Explore More Product & Management Skills→
MartinoPoloMartinoPolo
1

mp-grill

Clarify plans and requirements by interrogating assumptions until decisions are settled.

Community
Intermediate
jlawsjlaws
2

session-handoff

Generate structured HANDOFF.md documents with session decisions, file paths, and next steps.

Community
Intermediate
carson-sweetcarson-sweet
6

Session Export

Generate a portable markdown record of an AI session with transcripts and decision logs.

Community
Intermediate
VKirillVKirill
112

project-memory

Standardize project documentation with PROGRESS.md, LESSONS.md, and ADRs.

Community
Intermediate