skills.rest
flonat
flonatCOMMUNITY
Explore all skills by this author →
𝕏@fburnatGitHub

handoff

Manage project state handoffs between AI sessions using a .context/ai-handoff.md file.

127|22|Updated Feb 20, 2026
Search Tags:#handoff#research workflow#AI session continuity#project state tracking#cross-client coordination
One-click install
npx skills add https://github.com/flonat/flonat-research --skill handoff-flonat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/flonat/flonat-research/tree/main/skills/handoff
Command: npx skills add https://github.com/flonat/flonat-research --skill handoff-flonat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the challenge of passing a project between AI sessions, ensuring continuity and consistency in work flow.

Core Features & Use Cases

  • Cross-Client Handoff: Supports handoff between Claude and Codex, as well as between sessions of the same client.
  • Persistent Handoff Protocol: Utilizes a .context/ai-handoff.md file for recording and tracking the handoff state.
  • State Tracking: Tracks and updates the status of the handoff from 'ready' to 'in_progress' and 'complete'.

Quick Start

Create a handoff to continue work from a previous AI session by running the 'handoff' command.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I maintain AI session continuity when switching between Claude and Codex?▼

AI session continuity is maintained by recording the project state in a `.context/ai-handoff.md` file, allowing the next session to seamlessly resume the workflow. This cross-client coordination tracks task status from ready to complete.

What is the best way to hand off a project state between different AI sessions?▼

The best way to hand off a project state is using a persistent handoff protocol that writes the current context to a `.context/ai-handoff.md` file. This ensures seamless continuation and consistency across different AI systems.

Does the project handoff process support cross-client coordination between Claude and Codex?▼

Yes, cross-client coordination supports project handoff between Claude and Codex clients. It tracks the handoff state and updates the status from ready to in_progress and complete to maintain workflow consistency.

How do I track the status of an AI session handoff?▼

You can track the status of an AI session handoff by checking the `.context/ai-handoff.md` file, which updates the project state from ready to in_progress and finally to complete as the task progresses.

When do I need a persistent handoff protocol for my research workflow?▼

You need a persistent handoff protocol for your research workflow when you must pass complex project states between AI sessions to ensure task continuation. It prevents context loss when transitioning work across different AI clients.

Are there any limitations to using a markdown file for project state tracking across AI systems?▼

Using a markdown file for project state tracking relies on the `.context/ai-handoff.md` protocol to maintain consistency. It currently supports cross-client coordination specifically between Claude and Codex sessions.

Related Skills

Explore More Software Engineering Skills→
HermeticOrmusHermeticOrmus

pickup

Restore session context from a HANDOFF.md file with project details and git history.

Community
Intermediate
HermeticOrmusHermeticOrmus

handoff

Capture development session state into a HANDOFF.md file.

Community
Intermediate
nnexainnexai
1

gsd-check-todos

List and filter pending development tasks with roadmap correlation.

Community
Intermediate
maxwell2732maxwell2732
39

session-memory

Persist cross-session learnings to .claude/memory with decisions.md, patterns.md, and context.json.

Community
Intermediate