Continuity Package — End-of-Session Skill

Package session artifacts into a validated continuity ZIP for handoff.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Vincri126/MCO-Template --skill continuity-package-end-of-session-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Continuity Package — End-of-Session Skill
Source: https://github.com/Vincri126/MCO-Template/tree/main/.orchestrator/skills/continuity-package
Command: npx skills add https://github.com/Vincri126/MCO-Template --skill continuity-package-end-of-session-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents knowledge loss and misaligned handoffs by ensuring every end-of-session artifact is updated and packaged before closing a session.

Core Features & Use Cases

  • Structured continuity checklist keeps project status, schema notes, roadmap updates, and CLAUDE governance files synched with precise action logs, metrics, and blocker changes.
  • Zip-based handoff bundles the canonical continuity documents plus every .orchestrator/skills entry so the next session loads a complete state snapshot.
  • Use Case: After finishing a sprint checkpoint, run the checklist to capture the action log, schema edits, roadmap progress, and CLAUDE updates, then build the ZIP for the next collaborator.

Quick Start

Use the continuity package skill to run the session wrap-up checklist and build the continuity ZIP for handoff.

Frequently Asked Questions about Continuity Package — End-of-Session Skill

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

FAQPage Schema
How do I package project status files and action logs for session continuity?

You package project status files by running an end-of-session checklist that appends action logs, reconciles schema and roadmap updates, and bundles everything into a validated continuity ZIP for handoff.

What is included in a session continuity package for project handoff?

A session continuity package includes canonical continuity documents, schema notes, roadmap updates, CLAUDE governance files, and every .orchestrator/skills entry bundled into a validated ZIP.

How do I prevent knowledge loss during end-of-session workflow transitions?

To prevent knowledge loss during end-of-session transitions, update project status files, databases, and session summaries, then package all artifacts into a continuity ZIP before closing.

Do I need any external dependencies to build a continuity ZIP for handoff?

No external dependencies are required to build a continuity ZIP; the skill operates independently to validate and package your session artifacts for project handoff.

Can I use this session continuity checklist for sprint checkpoints and blocker tracking?

Yes, you can use the session continuity checklist for sprint checkpoints to capture action logs, metrics, schema edits, roadmap progress, and blocker changes before building the handoff ZIP.