rpm

Automate session-continuity and drift detection for Claude Code workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

rpm solves the problem of losing session context and drifting requirements by providing a persistent context, session resumption, and drift auditing so developers can pick up where they left off without re-explaining.

Core Features & Use Cases

  • Session resumption: Every session starts with full context including git state, tasks, and drift history.
  • Drift auditing: Scans docs and memory to surface inconsistencies and outdated instructions.
  • Backlog and handoff: Maintains a backlog and generates handoffs for the next session.

Quick Start

Run /init-rpm to scaffold rpm infrastructure for a new project, then start working as rpm auto-loads context at session start.

Frequently Asked Questions about rpm

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

FAQPage Schema
How do I keep Claude Code context and git state across sessions?

To keep Claude Code context across sessions, you can use a session-continuity tool that preserves git state, tasks, and drift history. It auto-loads context at the start of every session so you can resume work without re-explaining.

What is drift detection in project tracking and when do I need it?

Drift detection scans project docs and memory to surface inconsistencies and outdated instructions. You need it when managing long-running Claude Code workflows where requirements and documentation easily become misaligned over time.

How do I set up automated session management for a new project?

To set up automated session management, run the initialization command once per project to scaffold the infrastructure. This sets up project tracking, backlog, and handoff generation under project docs.

Does Claude Code session management require any external dependencies?

No, this Claude Code session management approach requires no external dependencies. It operates by reading and writing project docs and using hooks to update trackers and generate handoffs natively.

What's the best way to generate session handoffs for Claude Code workflows?

The best way to generate session handoffs is using an automated tracking tool that maintains a backlog and logs git context via hooks. It creates detailed handoff documents for the next session.

Why does my project context drift when using Claude Code across multiple sessions?

Project context drifts because standard sessions do not preserve git state, tasks, and instructions. An automated drift auditing tool fixes this by scanning docs to surface inconsistencies and auto-loading context.