session-lifecycle-automation

Automate session lifecycle hooks by configuring bookend scripts that capture decisions and open questions when sessions close. This skill modifies workspace settings to prevent the 44% zero-artifact session leak, preserving knowledge without manual intervention for solo operators.

Session lifecycle hooks are automated triggers that run at session start and end to preserve artifacts like decisions and open questions. You need them when sessions frequently close without saving context, causing knowledge loss and re-learning in solo operator development workspaces.

Set up background maintenance agents and commission directories by running this skill against your workspace path. It schedules automated maintenance tasks and creates a fire-and-forget delegation directory, enabling solo operators to queue background work without interrupting active development sessions.

Yes, session automation hooks integrate by modifying your existing ~/.claude/settings.json file. The skill requires filesystem access to read current automation state, update settings, schedule cron tasks, and create commission directories within the workspace.

Audit existing workspace automation by running this skill's audit function, which detects current hooks, scheduled tasks, and commission directories. This identifies what automation loops already exist before configuring new session bookend hooks, preventing duplicate or conflicting configurations.

Sessions lose context because without lifecycle hooks, decisions and open questions are not automatically preserved when sessions close. This creates a 44% zero-artifact session leak rate, forcing solo operators to re-learn project state and reducing overall productivity.