session-summary

Generate structured session handoff summaries with TL;DR and next steps.

1|Updated Jun 8, 2024
One-click install
npx skills add https://github.com/michaelmechenko/dotfiles --skill session-summary-michaelmechenko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-summary
Source: https://github.com/michaelmechenko/dotfiles/tree/main/opencode/skill/session-summary
Command: npx skills add https://github.com/michaelmechenko/dotfiles --skill session-summary-michaelmechenko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Session handoffs often lose critical context between transitions. This Skill generates concise, structured summaries that preserve decisions, actions, and environmental state.

Core Features & Use Cases

  • Structured Handovers: TL;DR, Completed Work, In Progress, Pending Decisions, and Critical Context are captured in a consistent format.
  • Context Preservation: Documents environment-specific details, files, and preferences to aid new agents or teammates.
  • On-Demand Handoff: Triggered at session end, pre-breaks, or when transferring context to another session or agent.

Quick Start

Provide a concise, context-rich session handoff summary at the end of a work session to enable smooth continuation by others.

Frequently Asked Questions about session-summary

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

FAQPage Schema
How do I generate a session summary for agent handoffs?

Generate a session summary by triggering the Skill at the end of a work session to output a structured handoff document. It captures the TL;DR, completed work, in-progress items, and next steps to ensure critical context is preserved for new agents.

What is the best way to preserve context during task transitions?

The best way to preserve context during task transitions is to create a structured handoff summary that documents environmental details, files, and user preferences. This ensures new agents or teammates have the critical state needed to continue work seamlessly.

What format should a session handoff summary include?

A session handoff summary should include a structured format covering a TL;DR, completed work, in-progress items, pending decisions, user preferences, next steps, and critical context. This format guarantees decisions and state are consistently captured.

When do I need to generate a handoff summary?

You need to generate a handoff summary at the end of a work session, before breaks, or when transferring context to another agent or team. This prevents context loss and ensures smooth continuation of in-progress tasks.

Can I use this for transferring context to a new agent?

Yes, you can use this to transfer context to a new agent by generating a concise, context-rich session wrap-up. It captures pending decisions and environmental state, allowing the new agent to resume work without losing critical information.

Does this work for end-of-session wrap-ups and task transitions?

Yes, this works for end-of-session wrap-ups and task transitions by applying a consistent note-taking format. It documents user preferences and critical context, solving the problem of losing decisions and actions between session transfers.