gsd-thread

Manage persistent context threads for cross-session workflows.

Updated May 21, 2026
One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-thread-jedmamosto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-thread
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-thread
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-thread-jedmamosto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gsd-thread prevents you from losing important context between AI sessions by managing persistent threads that can be resumed later.

Core Features & Use Cases

  • Create and manage persistent context threads: Start new lightweight cross-session knowledge stores for work that does not map to a single phase.
  • List and inspect thread state: Retrieve available threads and their status (including open vs resolved) to pick up the right item.
  • Close or resume thread work: Stop tracking completed context or continue an in-progress thread by slug.

Quick Start

Use the gsd-thread skill to show your current threads by running status demo-thread.

Frequently Asked Questions about gsd-thread

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

FAQPage Schema
How do I keep AI work context ready across sessions without losing state?▼

Persistent context threads let you keep work context ready across sessions by storing cross-session workflow state in a local markdown file. This lightweight knowledge store allows ongoing projects and research notes to be resumed later without losing state.

How do I resume an in-progress workflow thread by slug?▼

You resume an in-progress workflow thread by running the resume command with the specific thread slug. This retrieves the saved cross-session context and loads the workflow state for immediate continuation.

Can I list and check the status of persistent threads?▼

You can list available persistent threads and inspect their status to check open versus resolved items. This helps you pick up the right workflow context when returning to cross-session work.

Do I need a specific file path to manage cross-session knowledge stores?▼

Cross-session knowledge stores require read and write access to a workflow thread store located at $HOME/.claude/get-shit-done/workflows/thread.md. This file acts as the persistent memory for your context threads.

When should I close a persistent context thread?▼

Close a persistent context thread when a multi-session workflow or project is completed. Closing stops tracking the resolved context, keeping your active thread list focused on in-progress work.

What is the best way to manage multi-session workflows that do not map to a single phase?▼

Creating lightweight persistent threads is the best way to manage multi-session workflows that do not map to a single phase. This provides a cross-session knowledge store not tied to specific project milestones.