session-continuity

Organizes session notes, handoffs, and project profiles in a notes home outside project repos.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/t-step/bindle-archive --skill session-continuity-t-step
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-continuity
Source: https://github.com/t-step/bindle-archive/tree/main/skills/session-continuity
Command: npx skills add https://github.com/t-step/bindle-archive --skill session-continuity-t-step

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding sessions end and their context dies with them, and notes saved inside a project repo are one git add -A away from being published. This Skill defines a durable, private notes home outside every repo, plus the conventions for session notes, handoffs, and project profiles that keep cross-session context intact. ## Core Features & Use Cases - Notes home conventions: Defines a ~/.bindle/projects/<project>/ layout with per-session notes, handoffs, a curated profile, a per-fact store, and a profile-proposals queue, all in plain Markdown. - Privacy-gated repo exports: Enforces a dual-artifact recipe where the full private note always stays in the notes home and only a scanner-checked, sanitized summary may enter the repo on explicit request. - Read-only session boundaries: Keeps session orientation and wrap-up from modifying the working repo, and requires handoffs to state what is done, out of scope, and untouchable. - Use Case: At the end of a debugging session, run /session-end to write a structured note (decisions, risks, next prompt) to the notes home, queue a profile-worthy fact for an Add/Defer/Reject decision, and leave the repo untouched. ## Quick Start Ask the agent to end the current session and save session notes plus a handoff for the next session using the session-continuity conventions.

Frequently Asked Questions about session-continuity

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

FAQPage Schema
How do I save session notes so a future session can catch up?▼

Run the /session-end command, which writes a structured Markdown note to the notes home at projects/<project>/sessions/YYYY-MM-DD-<slug>.md. The note records decisions, risks, deferred work, and the single best next prompt, and the repo is never modified.

Where should AI session notes and project profiles live?▼

They live in a notes home outside every project repo, defaulting to ~/.bindle or the BINDLE_NOTES_DIR environment variable. Project repos hold code and project-owned config; everything about your personal work on them stays in the notes home.

Can I put a session summary in the repo for a teammate?▼

Yes, but only on explicit request and only as a sanitized summary. The full private note is always written to the notes home first, then a separate repo copy must pass the check-private-info.sh scanner and is left unstaged.

Does session-continuity work with Obsidian?▼

Yes. Pointing BINDLE_NOTES_DIR at an Obsidian vault directory makes every note appear in the vault, since all artifacts are plain Markdown. Nothing in the conventions requires Obsidian plugins or sync assumptions.

What happens to a profile suggestion I defer?▼

A deferred proposal persists in profile-proposals.md and resurfaces unchanged at the next interactive /session-end run. Rejected proposals are removed permanently, and accepted ones move into profile.md; unattended runs only queue proposals without deciding.

Why shouldn't a handoff just say what to do next?▼

A handoff without scope boundaries invites the next session to redo or bulldoze finished work. The conventions require every handoff to state what is done, what is out of scope, and what must not be touched.