pause

Save session state and write a .continue-here.md handoff file.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/SienkLogic/towline --skill pause
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pause
Source: https://github.com/SienkLogic/towline/tree/main/plugins/dev/skills/pause
Command: npx skills add https://github.com/SienkLogic/towline --skill pause

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Saves the current session state so you can resume exactly where you left off in a future conversation.

Core Features & Use Cases

  • Capture the minimal handoff data needed to resume work, including current phase/plan, completed work, remaining tasks, and key decisions.
  • Generate a .continue-here.md handoff file and optionally update the global STATE.md to reflect the pause point.
  • Optional git-based WIP commit to record the pause when configured by repo settings.

Quick Start

Run the pause skill to create a .continue-here.md handoff and capture the current session state for resumption.

Frequently Asked Questions about pause

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

FAQPage Schema
How do I save session state to resume interrupted workflow phases later?

To save session state, the pause skill collects your current plan position, completed work, remaining tasks, decisions, and blockers, then writes a .continue-here.md handoff file for exact resumption later.

What is a .continue-here.md handoff file and how does it capture session state?

A .continue-here.md handoff file is a generated document that captures the minimal session state data needed to resume work, including current phase, completed work, remaining tasks, and key decisions.

Can I create a git WIP commit to record a workflow pause point?

Yes, you can optionally create a git WIP commit to record the pause point when configured by your repository settings, preserving the session state alongside the generated handoff file.

Does the pause skill update STATE.md to reflect the current pause position?

Yes, the pause skill optionally updates the global STATE.md file to reflect the current pause position, ensuring the broader workflow state stays synchronized with the saved handoff data.

What's the best way to handle session handoff across interrupted workflow conversations?

The best way to handle session handoff is to collect position, completed work, remaining work, decisions, blockers, and next steps into a structured handoff file, enabling a clean resumption across future conversations.

When do I need to save workflow session state for cross-session resumption?

You need to save workflow session state when an interrupted Towline workflow spans multiple phases and plans, requiring a clean handoff to resume exactly where you left off in a future conversation.