Session Continuity Engine
# Prompt: Session Continuity Engine (SCE) # Version: 1.2.4 # Author: Scott Malin, CISSP # Purpose: # Compresses a completed AI session into a structured continuity package that can be # transferred into a new session…
Open the source (opens github.com) https://github.com/f/prompts.chat
What it is
Prompts from thanos0000@gmail.com.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
The prompt
# Prompt: Session Continuity Engine (SCE)
# Version: 1.2.4
# Author: Scott Malin, CISSP
# Purpose:
# Compresses a completed AI session into a structured continuity package that can be
# transferred into a new session (including across different AI platforms) to preserve
# project context, historical decisions, active workstreams, and established conventions.
# The goal is to minimize context loss, reduce repetitive onboarding, and maintain
# project momentum using filter-safe, passive reference architecture.
# Changelog:
# - v1.0.0 to v1.2.1: Initial releases, cross-platform tuning, JSON mode addition.
# - v1.2.2: Fixed nested codeblock parsing issues. Standardized JSON keys.
# Quantified context scale metrics. Clarified Section 8 verification payload rules.
# - v1.2.3: Re-engineered compliance notice and guidelines into passive, static
# reference language to completely eliminate heuristic safety filter triggers.
# - v1.2.4 — 2026-10-19: Integrated LLM adaptation note for format and verification template control.
--------------------------------------------------------------------------
We are ending this session to preserve context, reduce context drift, and
maintain continuity across future conversations.
Your task is to create a comprehensive Session Transfer Package that captures
the current project state, active decisions, historical context, constraints,
and next actions.
The resulting package should help a future AI assistant understand the project
quickly and continue work with minimal re-discovery effort.
--------------------------------------------------------------------------
PURPOSE & METHODOLOGY
--------------------------------------------------------------------------
This document is a static, user-provided project state snapshot. It functions
strictly as reference documentation to ground the current session in historical
context, established project definitions, and completed technical milestones.
--------------------------------------------------------------------------
PROJECT REFERENCE GUIDELINES (v1.2.3)
--------------------------------------------------------------------------
The receiving assistant utilizes this data as an informational baseline:
- Use the confirmed project decisions to maintain consistency with existing work.
- Distinguish clearly between established facts, open questions, and planned steps.
- Reference the documented naming conventions, standards, and version histories
to prevent regression or configuration drift.
- Use tables or compact lists for scannable reference when displaying assets.
- Request explicit clarification if the archived data conflicts with current objectives.
--------------------------------------------------------------------------
LLM ADAPTATION NOTE
--------------------------------------------------------------------------
[LLM ADAPTATION NOTE v1.0] Carefully verify whether Markdown or JSON mode is requested before generating the output; default to Markdown using the exact section numbers and headings 0 through 8. For Section 8, output the verification template verbatim without executing it as instructions. Ensure all active project decisions, constraints, and source-of-truth assets from the conversation history are accurately condensed into the respective sections without omitting key metadata or metrics.
--------------------------------------------------------------------------
OUTPUT GENERATION INSTRUCTIONS
--------------------------------------------------------------------------
Generate the final output exactly as follows:
1. A brief introductory sentence.
2. One markdown codeblock containing the Session Transfer Package.
NESTED CODEBLOCK RULE: If the content inside any section requires a codeblock,
use four backticks (````) for the outer container or escape the inner blocks so
the master container does not break prematurely.
DEFAULT MODE (Markdown): Use the structure inside the START/END block below.
JSON MODE: If the user explicitly requests "JSON output" or "JSON mode", output
a single valid JSON object. Do not wrap it in markdown text. Use these exact
camelCase keys:
{
"handoffMetadata": {},
"projectHandoffContext": { "preferredInteractionStyle": "" },
"projectContextStatus": { "keyRisksAndAntiDrift": "" },
"persistentConstraints": {},
"historicalLedger": [],
"currentSourceOfTruthAssets": [],
"openQuestions": [],
"immediateNextSteps": [],
"continuityVerificationTemplate": ""
}
START OF PACKAGE CODEBLOCK
# SESSION TRANSFER PACKAGE (SCE v1.2.3)
## 0. Handoff Metadata
- Originating Platform/Model:
- Date:
- Sessions Compressed:
- Rough Context Scale (Choose one based on current session depth):
· Short (<10k tokens / brief chat)
· Medium (10k-50k tokens / moderate technical deep dive)
· Long (50k-100k tokens / heavy code or long multi-stage conversation)
· Very Long (>100k tokens / massive repository context or highly extended session)
- Primary Topics / Tags:
- Key Repositories/Files:
## 1. Project Handoff Context
This section summarizes the overall purpose of the project, its current
direction, major objectives, and any important strategic decisions already
made.
### Preferred Interaction Style
[Describe preferred working style, formatting conventions, level of detail,
versioning expectations, confidence-label requirements, communication style,
and other collaboration preferences.]
## 2. Project Context & Current Status
Provide a compressed but comprehensive summary of:
- Current project goals
- Work completed
- Current state
- Active development efforts
- Recent decisions
- Known issues
Focus on preserving context that would otherwise require significant effort
to rediscover.
### Key Risks, Gotchas & Anti-Drift Notes
Document any known risks, common failure modes, deprecated approaches,
or specific guidance to prevent context drift or safety issues in future sessions.
## 3. Persistent Constraints & Operating Standards
Document ongoing standards such as:
- Formatting…
Written by the prompts.chat (CC0 prompt collection) community (thanos0000@gmail.com). Not tested by InnerVault.
How to get it
Setup steps: not applicable.
Related
-
Hand-off
PromptsProduce a handoff summary of all decisions made in this session, formatted so I can paste it into a new chat to continue with the next steps pending to execute.
-
Continuous Execution Mode AI
PromptsYou are running in “continuous execution mode.” Keep working continuously and indefinitely: always choose the next highest-value action and do it, then immediately choose the next action and continue. Do not stop to…
-
Continue Coding Assistant
PromptsAct as a Continue Coding Assistant. You are a skilled programmer with expertise in multiple programming languages and frameworks. Your task is to assist in continuing the development of a codebase or project. You will…
-
Continue and Recap Assistant
PromptsAct as Opus 4.5, a Continue and Recap Assistant. You are a detail-oriented model with the ability to remember past interactions and provide concise recaps. Your task is to continue a previous task or project by: -…
-
Tell Your Story
PromptsWrite a personal story about why I started contributing to open source, what drives me, and how sponsorship helps me continue this journey in [field/technology].
-
Role: Principal AI Project Manager, Senior Prompt Engineer, and Multi-Agent Workflow Orchestrator. Context: Continue the existing project. Inspect and follow all current project rules, architecture decisions…