gsd-thread

Name: gsd-thread
Availability: InStock
Author: duyseu

Create, list, and resume persistent context threads in Markdown files.

1|Updated Aug 17, 2025

Search Tags:#workflow #planning #context #threads #cross-session #manage

Ready to run

npx skills add https://github.com/DuySeu/StockMind --skill gsd-thread-duyseu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-thread
Source: https://github.com/DuySeu/StockMind/tree/main/.agent/skills/gsd-thread
Command: npx skills add https://github.com/DuySeu/StockMind --skill gsd-thread-duyseu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage persistent context threads to keep lightweight, cross-session knowledge stores for work that spans multiple sessions.

Core Features & Use Cases

Create, list, and resume lightweight context threads stored as Markdown files under .planning/threads/{slug}.md.
Track thread status with OPEN, IN PROGRESS, and RESOLVED, enabling smooth handoffs across sessions.
Reuse and reference prior thread content to maintain continuity of work without losing context.

Quick Start

Create a new thread with a concise description, then resume it in future sessions to continue work.

Frequently Asked Questions about gsd-thread

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

FAQPage Schema

How do I manage persistent context across multiple work sessions?▼

You can manage persistent context across multiple work sessions by creating lightweight threads stored as Markdown files. These threads track status states like OPEN, IN PROGRESS, and RESOLVED to ensure smooth handoffs without losing continuity.

What is the best way to store cross-session knowledge for ongoing planning?▼

The best way to store cross-session knowledge is using persistent context threads saved under a local planning directory. This approach keeps lightweight Markdown records of prior work, enabling you to resume tasks seamlessly in future sessions.

How do I create and resume a workflow thread?▼

To create and resume a workflow thread, you use specific modes to generate a slug and format a Markdown template. When resuming, the system retrieves the existing thread file and updates its status to IN PROGRESS to continue work.

Can I track the status of my cross-session threads?▼

Yes, you can track the status of cross-session threads using three designated states: OPEN, IN PROGRESS, and RESOLVED. The system automatically updates the thread status within the Markdown file when you resume or complete work.

Do I need any external dependencies to organize cross-session work with threads?▼

No external dependencies are required to organize cross-session work with threads. The system operates independently using a small internal DSL to manage thread modes and stores all data locally as Markdown files.

When should I avoid using persistent context threads for workflow planning?▼

You should avoid using persistent context threads for isolated, single-session tasks that do not require cross-session knowledge. Since it creates Markdown files to track status handoffs, it is unnecessary for ephemeral work that concludes immediately without future resumption.