ftm-pause

Serialize the active ftm session state into a portable STATE.md file.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Saves the current ftm skill session state so conversations can resume later without losing context, across brainstorm, executor, debug, council, and audit workflows.

Core Features & Use Cases

  • Session capture: serialize the active session context, including phase, decisions, and goals, to a portable state file.
  • Cross-conversation resume: restore full context in a new chat and continue where you left off.
  • Multi-skill compatibility: supports pausing any active ftm skill and rehydrating it later.

Quick Start

Invoke /ftm-pause during an active session to capture and save the current ftm state for seamless resumption in a future conversation.

Frequently Asked Questions about ftm-pause

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

FAQPage Schema
How do I pause and save a development session state without losing context?

To pause and save a development session state, invoke the pause command to serialize the active context, phase, and goals into a portable markdown file, enabling seamless restoration later.

Can I resume a paused conversation state across multiple new chat sessions?

Yes, you can resume a paused conversation state across new chats by restoring the serialized session file, which rehydrates the full context so you can continue exactly where you left off.

Does session state serialization work with brainstorm, debug, and audit workflows?

Session state serialization supports pausing and resuming progress across brainstorm, executor, debug, council, and audit workflows by capturing phase-specific data from the active skill.

Where is the serialized session state file stored for cross-conversation restoration?

The serialized session state file is written and validated to a specific state directory in your local environment, ensuring the captured session context remains accessible for future restoration.

What is the best way to manage session state when switching between different skills?

The best way to manage session state across skill boundaries is to serialize the active session data into a portable file attached to your project, capturing decisions and phase-specific data for rehydration.

Do I need an active session running to capture and save my current progress state?

Yes, you must have an active session running because the pause mechanism detects the active skill and captures its current phase, decisions, and goals to validate and write the state file.