session-end

Automate end-of-session cleanup, documentation, and commit to memory.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/paulyokota/FeedForward --skill session-end-paulyokota
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-end
Source: https://github.com/paulyokota/FeedForward/tree/main/.claude/skills/session-end
Command: npx skills add https://github.com/paulyokota/FeedForward --skill session-end-paulyokota

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-session cleanup, documentation, and commit are performed automatically to ensure consistent post-session records and reproducible history.

Core Features & Use Cases

  • Automatically summarize the session and surface keystone learnings.
  • Write end-of-session notes to box/sessions with a standardized file name pattern and structured content.
  • Update the investigation log and routing references to keep knowledge bases in sync.

Quick Start

Summarize the session, write end-of-session notes to box/sessions, and commit the changes to memory and routing.

Frequently Asked Questions about session-end

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

FAQPage Schema
How do I automate end-of-session documentation and cleanup?

An end-of-session wrap-up automatically summarizes the session, writes structured notes to box/sessions, updates the investigation log and routing references, and commits changes to memory.

What is included in automated session notes for issue tracking?

Automated session notes include a session summary, keystone learnings, and structured content written to box/sessions using a standardized file name pattern.

How do I keep my investigation log and routing updated after a session?

Updating an investigation log and routing is handled automatically by the workflow, which ensures knowledge bases and issue trackers stay in sync when changes are committed to memory.

Does this session-end workflow require any external dependencies?

No external dependencies are required to run the session-end workflow, as it operates independently to summarize sessions, write notes to box/sessions, and commit routing updates.

When should I use an automated workflow for session wrap-up?

Using an automated workflow for session wrap-up is necessary when your sessions require reflective notes, investigation logs, and routing updates across knowledge bases to ensure consistent post-session records and reproducible history.