session-end

Persist active plans and generate session handoff and summary documentation.

3|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/fluxforgeai/ARTEMIS --skill session-end-fluxforgeai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-end
Source: https://github.com/fluxforgeai/ARTEMIS/tree/main/.claude/skills/session-end
Command: npx skills add https://github.com/fluxforgeai/ARTEMIS --skill session-end-fluxforgeai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that ephemeral session work is persisted, summarized, and handed off safely so important implementation plans, decisions, and trackers are not lost between sessions.

Core Features & Use Cases

  • Persist active plans: Locate recent plan files and copy them into a timestamped docs/plans archive for continuity.
  • Generate handoff and summary artifacts: Create NEXT_SESSION_PROMPT and SESSION_SUMMARY files with status, priorities, and references to saved plans.
  • Repository bookkeeping: Update CLAUDE.md to point to the new handoff, archive previous handoffs, and reconcile findings trackers and changelogs when relevant.
  • Use Case: At the end of a development or AI-assisted session, run the workflow to capture work-in-progress, produce a clear next-session prompt, and keep project trackers and documentation synchronized.

Quick Start

Create a new NEXT_SESSION_PROMPT and SESSION_SUMMARY, save any recent plan from ~/.claude/plans to docs/plans with a timestamped filename, update CLAUDE.md line 24 to reference the new handoff, and move the old handoff to docs/archive/sessions/.

Frequently Asked Questions about session-end

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

FAQPage Schema
How do I automate session handoff and summary documentation at the end of a development cycle?

Automating session handoff involves saving active plan files into a timestamped archive, generating NEXT_SESSION_PROMPT and SESSION_SUMMARY artifacts, and updating CLAUDE.md references to persist work-in-progress safely between sessions.

What is the best way to archive previous handoffs and reconcile findings trackers?

Archiving previous handoffs requires moving old session files to a dedicated docs/archive/sessions/ directory and conditionally updating findings trackers and changelogs to ensure repository bookkeeping remains synchronized.

How does saving active plan files work with timestamped filenames for session continuity?

Saving active plan files works by locating recent plans from local directories and copying them into a timestamped docs/plans archive using file I/O operations, ensuring ephemeral implementation plans are not lost.

Can I update CLAUDE.md references to point to a new handoff without exposing credentials?

Updating CLAUDE.md references to point to a new handoff is supported through safe archival workflows that persist plans and documentation via file I/O without exposing credentials during the session end maintenance process.

Do I need specific file directories to persist plans and generate session summaries?

You need file I/O access across user and repo directories, specifically a local plans directory and a docs path, to copy plan files, create summary artifacts, and move previous handoffs to an archive.

Why does session end maintenance require conditional tracker updates and changelog reconciliation?

Session end maintenance requires conditional tracker updates and changelog reconciliation because repository bookkeeping must adapt to relevant findings, ensuring project trackers and documentation stay synchronized with the latest active plans.