run-session

Read and write session state in WORK.md and FLOW.md with git checkpoints.

11|2|Updated Apr 7, 2022
One-click install
npx skills add https://github.com/nullhack/temple8 --skill run-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-session
Source: https://github.com/nullhack/temple8/tree/main/.opencode/skills/run-session
Command: npx skills add https://github.com/nullhack/temple8 --skill run-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the lifecycle of multi-step sessions by ensuring state is consistently read at the start and written at the end, enabling agents to resume where they left off.

Core Features & Use Cases

  • Read policy and state management for FLOW.md and WORK.md
  • Auto-detects session state from filesystem and git
  • Checkpoints and resume across steps for uninterrupted workflows
  • Use Case: A team can pause a feature in progress and resume later without losing context or decisions.

Quick Start

Start a session by initializing from existing WORK.md and FLOW.md, detecting the current state, and loading the active feature to resume progress.

Frequently Asked Questions about run-session

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

FAQPage Schema
How do I automate session state management and resume capability across multi-step AI workflows?

Automate session state management by reading WORK.md and FLOW.md at the start of a session and writing updated checkpoints at the finish. This detects the current filesystem and git state, enabling AI agents to resume multi-step workflows exactly where they left off.

What is the best way to checkpoint an AI-assisted workflow so I can pause and resume it later?

The best way to checkpoint an AI-assisted workflow is to use automated session detection from your filesystem and git history. This approach reads your active feature state and updates checkpoints with a traceable commit history, ensuring no context or decisions are lost when pausing.

How does git-based state detection work for resuming interrupted feature development?

Git-based state detection works by reading your existing WORK.md and FLOW.md files to auto-detect the actual session state from the filesystem and repository. It then updates checkpoints with traceable commit history, allowing controlled transitions and accurate resume points.

Do I need specific dependencies or external components to enable session checkpointing with this approach?

No specific dependencies or external components are required to enable session checkpointing. The approach relies entirely on reading and writing to your existing WORK.md and FLOW.md files, using git and filesystem state detection to manage transitions and resume capabilities.

Can I use this session automation approach for team-based feature development without losing context?

Yes, you can use this session automation approach for team-based feature development. It ensures state is consistently read at the start and written at the end of a session, allowing teams to pause a feature in progress and resume later without losing context or decisions.

Why does my multi-step AI agent workflow lose context between different execution steps?

Multi-step AI agent workflows lose context between steps when session state is not consistently read at the start and written at the end. Automating this lifecycle with checkpointing and state detection prevents context loss and ensures controlled transitions across steps.