gsd-thread

Name: gsd-thread
Availability: InStock
Author: dobrinz123

Create, list, or resume persistent context threads in .planning/threads.

Updated Apr 9, 2026

Search Tags:#workflow #planning #context #threads #cross-session #thread #gsd

Ready to run

npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-thread-dobrinz123

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-thread
Source: https://github.com/dobrinz123/claude-skills-share/tree/main/skills/gsd-thread
Command: npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-thread-dobrinz123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams and individuals often lose track of context across sessions. gsd-thread solves this by creating lightweight, persistent context threads that live independently of any single planning phase.

Core Features & Use Cases

Create, list, and resume threads to capture goals, context, and next steps.
Persist thread data in a dedicated location (.planning/threads) to survive session restarts.
Use threads to bridge conversations across multiple sessions and phases without tying them to a single plan.

Quick Start

Create a new thread by providing a short description and let the system generate a slug, store it under .planning/threads, and mark it OPEN.

Frequently Asked Questions about gsd-thread

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

FAQPage Schema

How do I keep context persistent across multiple sessions for ongoing projects?▼

To keep context persistent across multiple sessions, you can create lightweight threads that store goals and next steps in a dedicated directory. This approach ensures your project data survives session restarts without being tied to a single plan.

What is the best way to manage cross-session threads for long-running workflows?▼

Managing cross-session threads involves creating, listing, and resuming context records stored in a local planning directory. This method bridges conversations across project phases by maintaining a persistent status and file structure independent of individual sessions.

How do I create and store a planning thread for ongoing work?▼

You create a planning thread by providing a short description of your task. The system then generates a slug, stores the thread file under a local planning directory, and marks its status as open for future reference.

Do I need any external dependencies to set up persistent context threads?▼

No external dependencies are required to set up persistent context threads. The system operates independently by parsing arguments, generating slugs, and managing thread files directly within your local environment.

When should I use cross-session threads instead of a single planning phase?▼

Use cross-session threads when you have long-running context that must survive multiple sessions and span across different project phases. They are ideal for ongoing projects where tying context to a single plan would cause you to lose track of broader goals.

Can I list and resume previously created context threads?▼

Yes, you can list and resume previously created context threads. The system manages thread status and retrieves stored files from the local planning directory, allowing you to pick up ongoing work exactly where you left off.