handoff

Generate structured cold-start prompts for cross-session handoffs.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/n0rvyn/indie-toolkit --skill handoff-n0rvyn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/n0rvyn/indie-toolkit/tree/main/dev-workflow/skills/handoff
Command: npx skills add https://github.com/n0rvyn/indie-toolkit --skill handoff-n0rvyn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates cross-session handoffs by generating a cold-start prompt that preserves project context and current task state.

Core Features & Use Cases

  • Generates structured cold-start prompts for session transfer that include context recovery, current task, and plan references.
  • Supports multi-user handoffs across days or different sessions, ensuring continuity and traceability.
  • Exposes a predictable output format that enables quick resumption without losing critical context.

Quick Start

Generate a concise cold-start prompt to transfer context to a new session.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I preserve project context when transferring work across sessions?

Preserving project context across sessions requires generating a structured cold-start prompt that captures context recovery, current task state, and plan references. This ensures continuity and traceability without losing critical information during the transfer.

What is a cold-start prompt for cross-session handoffs?

A cold-start prompt for cross-session handoffs is a structured markdown output that encapsulates project context, plan references, and status. It enables quick resumption of ongoing work by guiding context recovery and next actions for a new session or team member.

How do I generate a handoff prompt for a different team member?

Generating a handoff prompt for a team member involves creating a structured markdown document with sections for context, plan references, and status. This predictable output format supports multi-user handoffs across different days and sessions, ensuring quick resumption.

Can I configure model selection and disable model invocation for session handoffs?

Yes, session handoffs support configuration-driven behavior including disabling model invocation, context forking, and model selection. These settings control how the structured markdown prompt is generated and how context recovery is applied during the transfer.

What's the best way to automate context recovery for ongoing software engineering work?

Automating context recovery for ongoing work is best handled by generating a structured cold-start prompt that preserves project context and current task state. This approach applies to work spanning multiple sessions or team members, ensuring continuity and traceability.

What sections are included in a structured session handoff prompt?

A structured session handoff prompt includes sections for context, plan references, and status. This predictable markdown format guides context recovery, current task identification, and next actions, enabling quick resumption without losing critical project context.