wrap-session

Automate end-of-session documentation and handoff artifacts across project files.

527|69|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/product-on-purpose/pm-skills --skill wrap-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap-session
Source: https://github.com/product-on-purpose/pm-skills/tree/main/.claude/skills/wrap-session
Command: npx skills add https://github.com/product-on-purpose/pm-skills --skill wrap-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-session documentation is error-prone and often scattered across multiple files. This skill automates the generation and updating of handoff artifacts to maintain project continuity.

Core Features & Use Cases

  • Update README.md: refresh project description and status to reflect current state.
  • Update CHANGELOG.md: append Unreleased changes using Keep a Changelog format (Added/Changed/Fixed).
  • Refresh Agent Context: update AGENTS/<model>/CONTEXT.md with the latest project state.
  • Create Session Logs: generate and save SESSION-LOG entries under AGENTS/<model>/SESSION-LOG/.
  • Handoff & Documentation: prepare documentation for stakeholders when wrapping up or handing off work.

Quick Start

Invoke the wrap-session workflow at the end of a working session to generate a session log, update README.md and CHANGELOG.md, and refresh agent context files.

Frequently Asked Questions about wrap-session

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

FAQPage Schema
How do I automate end-of-session documentation and handoffs for my project?

You can automate end-of-session documentation by invoking a workflow that updates README.md, appends Keep a Changelog formatted entries to CHANGELOG.md, refreshes agent context files, and generates session logs to prepare handoff materials for stakeholders.

How does automated project handoff update CHANGELOG and README files?

Automated project handoff appends Unreleased changes to CHANGELOG.md using Keep a Changelog format like Added, Changed, or Fixed, and updates README.md to reflect the current project status and description.

What is the best way to maintain agent context when wrapping up a working session?

Maintain agent context by updating AGENTS/<model>/CONTEXT.md with the latest project state and saving detailed SESSION-LOG entries under AGENTS/<model>/SESSION-LOG/ during your end-of-session documentation workflow.

Do I need any specific dependencies to generate session logs and project documentation?

No specific dependencies are required to generate session logs and project documentation, as the workflow operates without external dependencies to format and update your project files directly.

Can I use this workflow to prepare documentation for stakeholders during a project handoff?

Yes, you can use this workflow to prepare documentation for stakeholders by generating handoff artifacts that update project docs and refresh agent context files for continuity.

What format does the automated session wrapper use for CHANGELOG entries?

The automated session wrapper uses the Keep a Changelog format for CHANGELOG entries, enforcing specific categorization like Added, Changed, and Fixed under an Unreleased section.