session-continuity-harness

Preserve PROGRESS.md, DECISIONS.md, and handoff protocols across Codex sessions.

3|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/pax-k/pax-fullstack-harness --skill session-continuity-harness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-continuity-harness
Source: https://github.com/pax-k/pax-fullstack-harness/tree/main/skills/session-continuity-harness
Command: npx skills add https://github.com/pax-k/pax-fullstack-harness --skill session-continuity-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The session-continuity-harness skill resolves the issue of agent state being lost or corrupted when sessions end or fail, ensuring projects can be resumed seamlessly.

Core Features & Use Cases

  • State Preservation: Safely preserves PROGRESS.md, DECISIONS.md, and handoff protocols to maintain project state.
  • Session Routines: Defines and enforces start and exit routines to maintain integrity and completeness.
  • Validation & Advice: Includes a script for advisory validation and coordinates with other skills for handoff and cleaning.

Quick Start

Implement the session-continuity-harness in your Codex projects by ensuring to update and document handoff points during active sessions.

Frequently Asked Questions about session-continuity-harness

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

FAQPage Schema
How do I preserve Codex project state across session boundaries?

To preserve Codex project state across session boundaries, you can use a session continuity harness that saves `PROGRESS.md` and `DECISIONS.md` files, defining start and exit routines to maintain long-running task integrity.

What is a handoff protocol for long-running agent tasks?

A handoff protocol for long-running agent tasks is a defined routine that documents transition points and validates state preservation, enabling consistent project state restoration when sessions end or fail.

How do I resume a failed Codex session without losing project information?

You resume a failed Codex session without losing project information by restoring previously saved `PROGRESS.md` and `DECISIONS.md` files through an enforced exit routine that ensures seamless state recovery.

Can I enforce start and exit routines for state preservation in my workflow?

Yes, you can enforce start and exit routines for state preservation by implementing a session continuity harness that coordinates advisory validation and cleaning scripts to maintain project completeness during active sessions.

Does the session continuity harness require any external dependencies to run?

No, the session continuity harness requires no external dependencies, relying solely on its internal scripts to coordinate handoff protocols, advisory validation, and state preservation across your Codex projects.