session-pack

Automate memory capture and handoff planning for collaborative sessions.

106|23|Updated Mar 1, 2026

Search Tags:#automation #multi-agent #memory #handoff #traceability #session-management

Ready to run

npx skills add https://github.com/ten-builder/ten-builder --skill session-pack-ten-builder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-pack
Source: https://github.com/ten-builder/ten-builder/tree/main/skills/session-pack
Command: npx skills add https://github.com/ten-builder/ten-builder --skill session-pack-ten-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Session participants often lose memory of decisions and struggle with continuity across handoffs. Session Pack automates memory extraction and handoff planning across multiple agents to keep context consistent.

Core Features & Use Cases

Memory extraction and context updates from session summaries.
Parallel analysis by three agents to generate memory changes, handoff drafts, and duplicate checks.
Handoff creation, updating, and archiving for completed sessions.
Git-change aware traceability and reproducibility.

Use cases: teams running long sessions, multi-agent workflows, audit trails, and seamless continuity between sessions.

Quick Start

Run /pack to automatically summarize the session and update memory and handoff across agents.

Frequently Asked Questions about session-pack

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

FAQPage Schema

How do I automate session memory and handoff for multi-agent workflows?▼

Automate session memory and handoff by running /pack to extract context, draft handoffs, and validate changes with git history. Three specialized agents coordinate deterministic updates to MEMORY.md and HANDOFF documents for traceable continuity.

What is the best way to maintain context continuity across long-running team sessions?▼

Maintain context continuity by automating memory extraction and handoff planning across multiple agents. This workflow updates MEMORY.md and context files, ensuring decisions are captured and sessions resume seamlessly without losing historical context.

How does multi-agent memory extraction work with git change history?▼

Multi-agent memory extraction works by running parallel agents to generate memory changes, draft handoffs, and check duplicates. It validates changes using git and context history to ensure reproducible and traceable updates to session documentation.

Can I use automated handoff generation for audit trails in multi-agent collaboration?▼

Use automated handoff generation for audit trails in multi-agent collaboration. The workflow creates, updates, and archives HANDOFF documents while tracking git changes, providing reproducible session continuity and traceable decision records.

Do I need a git repository to track session memory and handoff documents?▼

Git is used to provide git-change aware traceability and reproducibility for session memory updates. It validates the extracted memory and drafted handoffs against context history to ensure deterministic and accurate session continuity.