Session Continuity
- Updated July 20, 2026
- snjnlsn/snjnlsn-marketplace
session-continuity is an agent skill that maintains per-session and per-branch handoffs, callouts, retrospects, and branch finalization.
About
session-continuity is a marketplace plugin skill for developers who run long agent sessions across branches and need memory outside the model context window. It structures per-session and per-branch documentation: handoffs that explain what was done and what is next, callouts for important constraints, retrospects when a chunk of work ends, and branch finalization so merges do not orphan intent. Developers benefit most when multiple features move in parallel or when they stop mid-task and return days later—the skill favors procedural discipline over ad-hoc chat summaries. It complements implementation skills rather than replacing them; you still write code in Build, but you reduce repeated discovery in Ship review and Operate iteration because the narrative lives in repo-adjacent docs. Complexity is intermediate because you must adopt naming and update habits; confidence is moderate given sparse public SKILL.md detail beyond the lifecycle list.
- Per-session documentation lifecycle (handoffs and continuity notes)
- Per-branch lifecycle including branch finalization
- Callouts for decisions and risks across agent sessions
- Retrospects to close loops before merging or switching work
Session Continuity by the numbers
- Data as of Jul 21, 2026 (Skillselion catalog sync)
/plugin marketplace add snjnlsn/snjnlsn-marketplace/plugin install session-continuity@snjnlsn-marketplaceAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Last updated | July 20, 2026 |
|---|---|
| Repository | snjnlsn/snjnlsn-marketplace ↗ |
What it does
Keep per-session and per-branch continuity docs—handoffs, callouts, retrospects, and branch wrap-up—so agent work survives context limits and branch switches.
Who is it for?
Best when you're running multi-day agent sessions, parallel git branches, or frequent context-window resets and want repo-local continuity.
Skip if: One-shot tasks finished in a single short session with no branch churn, or teams that already enforce rigid PM tooling with no agent handoffs.
When should I use this skill?
Starting or ending an agent session, switching branches, or closing a body of work that needs handoffs, callouts, retrospects, or branch finalization.
What you get
You get structured session and branch documentation—handoffs, callouts, and retrospects—so the next session or reviewer can resume without replaying the whole chat.
- Session handoff documents
- Branch callouts and retrospects
- Branch finalization notes ready for merge or archive
Files
Per-session and per-branch documentation lifecycle: handoffs, callouts, retrospects, branch finalization.
session-continuity
Source: ./plugins/session-continuity
{ "name": "session-continuity", "source": "./plugins/session-continuity", "description": "Per-session and per-branch documentation lifecycle: handoffs, callouts, retrospects, branch finalization." }
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.488k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.401k16.1kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.397k16.1k
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.318k202k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k71Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k71How it compares
Use instead of pasting chat logs—this is a documentation lifecycle plugin, not a generic brainstorming or planning generator.
FAQ
Who is session-continuity for?
Developers using agent marketplaces who need repeatable session handoffs and branch-level wrap-up documentation.
When should I use session-continuity?
Use it in Build when starting or ending an agent session; in Ship when preparing a branch for review with a retrospect; and in Operate when iterating on production fixes across sessions.
Is session-continuity safe to install?
Check the Security Audits panel on this Prism page and review what files the plugin writes in your repo; avoid storing secrets in handoff docs.