session-close

Automate end-of-session cleanup and generate a Brady OS handoff.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/thingperson/pileofshame --skill session-close-thingperson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-close
Source: https://github.com/thingperson/pileofshame/tree/main/.claude/skills/session-close
Command: npx skills add https://github.com/thingperson/pileofshame --skill session-close-thingperson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-session ritualization streamlines project wrap-up by automating documentation hygiene, logging decisions, updating the session-resume artifact, and generating a Brady OS handoff to coordinate cross-project signals.

Core Features & Use Cases

  • End-of-session cleanup: tidy docs, update session-resume, surface DECISIONS for Brady review, and prepare the operator handoff.
  • Handoff generation: create Brady OS handoff notes to signal cross-project state changes and next steps.
  • Guardrails and transparency: ensure no modifications to in-progress work and clearly separate code vs operator-level signals.

Quick Start

Perform a session close by triggering the session-close skill to run the pre-flight sweep and generate the Brady OS handoff.

Frequently Asked Questions about session-close

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

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

Session-close automates end-of-session cleanup by tidying project docs, logging decisions, updating the session-resume artifact, and generating a Brady OS handoff to coordinate cross-project signals.

What is a Brady OS handoff and how does it manage cross-project state?▼

A Brady OS handoff is a generated note that signals cross-project state changes and next steps. It surfaces operator-level decisions for Brady's review while enforcing guardrails against modifying in-progress work.

How do I scan ROADMAP and AGENTS.md for drift when closing a session?▼

Scanning for drift during session closure checks ROADMAP and AGENTS.md files to identify misalignments. The pre-flight sweep surfaces these discrepancies in the generated handoff to keep project documentation accurate.

Can I push documentation updates and issue the handoff to the hub automatically?▼

Yes, the session close process optionally pushes documentation updates and issues the generated Brady OS handoff to the hub. This automates the end-of-session workflow while maintaining transparency between code and operator-level signals.

What guardrails prevent modifying in-progress work during session wrap-up?▼

Session close enforces guardrails that strictly avoid changing in-progress work and only surface non-sensitive, operator-level signals. This clearly separates code modifications from operator-level state updates during the handoff.