gsd-thread

Create, list, or resume persistent context threads with slug-based storage.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/onelee85/my-skills --skill gsd-thread
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-thread
Source: https://github.com/onelee85/my-skills/tree/main/gsd-thread
Command: npx skills add https://github.com/onelee85/my-skills --skill gsd-thread

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistent context threads help you store lightweight cross-session knowledge for work that spans multiple interactions without tying to a specific project phase.

Core Features & Use Cases

  • Create new threads from descriptions, list existing threads with status, and resume a thread to load its context.
  • Manage thread statuses (OPEN, IN PROGRESS, RESOLVED) and switch between sessions seamlessly.
  • Use cases include research threads, debugging investigations, and multi-session planning.

Quick Start

Create a new thread describing the task you want to track and I will set it up as an OPEN thread.

Frequently Asked Questions about gsd-thread

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

FAQPage Schema
How do I manage cross-session context for long-running research tasks?

You can manage cross-session context by creating persistent threads that store knowledge under .planning/threads. This enables you to resume ongoing investigations and load previous context seamlessly across multiple chats.

What is the best way to track multi-session planning workflows without losing previous context?

Tracking multi-session planning workflows is done by resuming persistent context threads that load stored knowledge. You can switch between sessions seamlessly while maintaining statuses like OPEN, IN PROGRESS, and RESOLVED.

Can I use persistent threads for debugging investigations that span multiple chats?

Yes, persistent threads support debugging investigations across multiple chats by storing lightweight cross-session knowledge. You can create a thread from a description, track its status, and resume it later to load the context.

How do I organize and update task statuses for cross-session context management?

You organize cross-session context management by assigning statuses such as OPEN, IN PROGRESS, or RESOLVED to your threads. This allows you to list existing threads and track the lifecycle of multi-session projects effectively.

Does session persistence require a specific project phase to save context?

No, session persistence stores lightweight cross-session knowledge independently of any specific project phase. Threads are implemented using slug-based storage, allowing you to manage ongoing research or planning tasks freely.