context-lifecycle

Orchestrate context checkpoints across session boundaries and compaction events.

1|Updated May 18, 2026

Search Tags:#context management #checkpointing #handoff #session continuity #compaction #git push

Ready to run

npx skills add https://github.com/linenoize/topia --skill context-lifecycle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: context-lifecycle
Source: https://github.com/linenoize/topia/tree/main/skills/context-lifecycle
Command: npx skills add https://github.com/linenoize/topia --skill context-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents long coding sessions from losing state, context, and next steps when work crosses phase boundaries, compaction events, or git pushes.

Core Features & Use Cases

Boundary orchestration: Decides when to save state, recommend compaction, and resume safely after a session transition.
Checkpoint recovery: Reads checkpoint and progress files before re-exploring work, so the agent resumes from the correct point.
Cross-session continuity: Coordinates handoffs, memory flushes, and compacted-session restoration for extended implementation work.
Use case: A developer finishes a risky refactor, pushes code, compacts the session, and then continues from the saved checkpoint without redoing research.

Quick Start

Ask the assistant to resume after compaction by reading the latest checkpoint and continuing from the next explicit action.

Frequently Asked Questions about context-lifecycle

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

FAQPage Schema

How do I maintain session continuity after context compaction in a long coding project?▼

Context checkpointing saves your working state before compaction events or git pushes. It reads existing progress files and coordinates memory flushes to ensure no implementation context is lost during session transitions.

What is the best way to resume work after a context compaction event?▼

The best way to resume work after compaction is to read the latest checkpoint file and execute the next explicit action. This validates the resume boundary and restores the full session state before continuing the coding task.

How do I save agent state before a risky refactor and git push?▼

You save agent state by triggering a checkpoint before phase endings and git push events. This orchestrates a session handoff by flushing memory and writing a progress file, ensuring safe recovery after the transition.

How does cross-session handoff work for extended implementation tasks?▼

Cross-session handoff coordinates context packing and neural memory workflows to transfer state across boundaries. It compacts the previous session and restores it in the new one, allowing extended implementation work to proceed without context loss.

When should I trigger a context checkpoint during a long-running coding session?▼

You should trigger a context checkpoint at phase endings, pre-compact and post-compact transitions, and git push events. This ensures state and next steps are saved before any session boundary or context window compression occurs.