longrunning-session

Coordinate long-running ADR workflows with phase planning, validation, and archival.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/pelchers/SessionSaver --skill longrunning-session
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: longrunning-session
Source: https://github.com/pelchers/SessionSaver/tree/main/.codex/skills/longrunning-session
Command: npx skills add https://github.com/pelchers/SessionSaver --skill longrunning-session

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps teams manage long-running sessions by enforcing phase-based planning, validation, and archival to keep work aligned and auditable.

Core Features & Use Cases

  • Phase planning and orchestration: create and manage phase plans in current/history.
  • Phase validation and review: enforce validations and generate phase_review files.
  • Handoff and queue: queue next phase via .codex/orchestration/queue/next_phase.json.
  • Documentation templates: produce primary_task_list.md, prd.md, technical_requirements.md, notes.md, plus phase_<N>.md and phase_<N>_review.md as work products.
  • Real-world use case: coordinate a multi-phase ADR for a product upgrade across teams, with history tracking.

Quick Start

Create the initial phase plan in current/ and generate the first phase file, primary_task_list.md, prd.md, technical_requirements.md, notes.md, and the initial history entry according to the templates.

Frequently Asked Questions about longrunning-session

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

FAQPage Schema
How do I manage phase planning for long-running ADR workflows across multiple teams?▼

Phase planning for long-running ADR workflows is managed by creating phase plans, enforcing validations, and generating phase_review files to keep multi-team work aligned and auditable across the project lifecycle.

What documentation templates do I need for multi-phase project orchestration?▼

Multi-phase project orchestration requires primary_task_list.md, prd.md, technical_requirements.md, and notes.md templates, plus phase_<N>.md and phase_<N>_review.md files to structure work products and phase validations.

How do I queue the next phase in a long-running session?▼

To queue the next phase in a long-running session, you generate a next_phase.json file within the .codex/orchestration/queue/ directory, triggering the handoff and continuation of the ADR workflow.

When should I use phase validation and archival reviews for product upgrades?▼

Phase validation and archival reviews should be used for product upgrades spanning multiple phases and teams, ensuring completed work passes validation checks, generates phase_review artifacts, and achieves auditable history tracking before handoff.

Does longrunning-session orchestration work without external dependencies?▼

Longrunning-session orchestration works without external dependencies, using internal references to coordinate phase creation, task lists, validations, and archival reviews entirely through generated markdown and JSON artifacts.