session-end

End the current rpm session and write a consolidated handoff.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

End-of-session wrap-ups are error-prone and can leave drift, unrecorded learnings, and backlog misalignment. This skill delivers a reliable, auditable handoff by ending the current rpm session, consolidating findings, and updating trackers for a clean transition.

Core Features & Use Cases

  • End-session orchestration: fast-path clean end for straightforward wrap-ups or full four-phase flow (Collecting Findings, Housekeeping, Reviewing Tasks, Handing Off) for complex sessions, with automated tracker updates and archival.
  • Drift and learning capture: auto-synthesizes learnings, updates past/present/future artifacts, and surfaces top next actions.
  • Handoff and repeatability: writes last-session data, clears session artifacts, and prints a handoff to resume in the next session.

Quick Start

Trigger the /session-end command to wrap up the current rpm session and generate a clean handoff.

Frequently Asked Questions about session-end

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

FAQPage Schema
How do I wrap up an rpm session with a clean handoff?

To wrap up an rpm session with a clean handoff, trigger the session-end command to consolidate findings, update trackers, and archive completed tasks. It applies a fast-path for straightforward wrap-ups or a four-phase workflow for complex sessions.

What is the best way to document session drift and learnings before handing off a backlog?

Documenting session drift and learnings is handled automatically during the four-phase session-end workflow. It auto-synthesizes learnings, updates past, present, and future artifacts, and surfaces top next actions for the backlog.

Do I need jq installed to automate rpm session end and handoff tasks?

Yes, you need jq installed as a dependency to run the session-end scripts. The Skill relies on jq to parse and process JSON data during the housekeeping and handoff phases.

What are the limitations of using a fast-path session end for complex backlog updates?

The fast-path session end is limited to straightforward wrap-ups without drift. Complex sessions require the full four-phase workflow—Collecting Findings, Housekeeping, Reviewing Tasks, and Handing Off—to properly capture learnings and update the backlog.

When do I need a full four-phase workflow to end a development session?

You need the full four-phase workflow to end a development session when there is drift, unrecorded learnings, or backlog misalignment. This structured process enforces phase transitions and seeks user confirmation for non-fast-path actions.

How does a session-end handoff update documentation and clear session artifacts?

A session-end handoff updates documentation by writing last-session data and clearing active session artifacts. It archives completed tasks, updates docs and rpm state, and prints a final handoff to resume work in the next session.